Faq t2b - Revision history

Admin: /* Debugging SSH connection to mX machines: */

2026-03-30T11:34:53Z

Debugging SSH connection to mX machines:

← Older revision		Revision as of 11:34, 30 March 2026
Line 25:		Line 25:
	<pre>		<pre>
	> ll $HOME/.ssh		> ll $HOME/.ssh
	> date && ssh -vvv MYUSERNAME@m3.iihe.ac.be <-- it needs to be on a specific machines (no mshort/mlong) so that we can read the logs!		> date && ssh -vvv MYUSERNAME@m10.iihe.ac.be <-- it needs to be on a specific machines (no mshort/mlong) so that we can read the logs!
	</pre>		</pre>

Admin: /* List of the UIs / mX machines: */

2026-03-30T11:34:28Z

List of the UIs / mX machines:

← Older revision		Revision as of 11:34, 30 March 2026
Line 1:		Line 1:
	<br><br>		<br><br>
	=== List of the UIs / mX machines: ===		=== List of the UIs / mX machines: ===
	- mshort: m2 , m3 => 20 minutes of CPU time per process <br>		- mshort: m10 , m11 => 20 minutes of CPU time per process <br>
	- mlong: ~~m0, m1~~ => ~~5 hour~~ of CPU time per process		- mlong: m4 to m9 => no limit of CPU time per process

	=== Keep ssh connection to UI open: ===		=== Keep ssh connection to UI open: ===

Admin: /* Debugging SSH connection to mX machines: */

2024-11-19T14:19:37Z

Debugging SSH connection to mX machines:

← Older revision		Revision as of 14:19, 19 November 2024
Line 29:		Line 29:

	: 2b. Also add your public IPv4 so that we can track your connection in the logs, via visiting for instance https://www.whatismyip.com/		: 2b. Also add your public IPv4 so that we can track your connection in the logs, via visiting for instance https://www.whatismyip.com/
			: 2c. Just in case something went wrong: send us your public ssh key (the one ending in .pub!à

	=== MadGraph taking all the cores of a workernode ===		=== MadGraph taking all the cores of a workernode ===

Admin: /* List of the UIs / mX machines: */

2024-04-02T11:15:28Z

List of the UIs / mX machines:

← Older revision		Revision as of 11:15, 2 April 2024
Line 1:		Line 1:
	<br><br>		<br><br>
	=== List of the UIs / mX machines: ===		=== List of the UIs / mX machines: ===
	- mshort: ~~m1,~~ m2 , m3 => 20 minutes of CPU time per process <br>		- mshort: m2 , m3 => 20 minutes of CPU time per process <br>
	- mlong: m4, ~~m5, m6 , m7~~ => 1 hour of CPU time per process		- mlong: m0, m1 => 5 hour of CPU time per process

	=== Keep ssh connection to UI open: ===		=== Keep ssh connection to UI open: ===

Admin: /* Debugging SSH connection to mX machines: */

2022-12-06T15:46:02Z

Debugging SSH connection to mX machines:

← Older revision		Revision as of 15:46, 6 December 2022
Line 28:		Line 28:
	</pre>		</pre>

	: 2b Also add your public IPv4 so that we can track your connection in the logs, via visiting for instance https://www.whatismyip.com/		: 2b. Also add your public IPv4 so that we can track your connection in the logs, via visiting for instance https://www.whatismyip.com/

	=== MadGraph taking all the cores of a workernode ===		=== MadGraph taking all the cores of a workernode ===

Admin: /* Debugging SSH connection to mX machines: */

2022-12-06T15:44:53Z

Debugging SSH connection to mX machines:

← Older revision		Revision as of 15:44, 6 December 2022
Line 9:		Line 9:

	=== Debugging SSH connection to mX machines: ===		=== Debugging SSH connection to mX machines: ===
	# Check permissions on ssh keys:		# Check permissions on ssh keys on your laptop:
	<pre>		<pre>
	> ll $HOME/.ssh		> ll $HOME/.ssh
Line 22:		Line 22:
	</pre>		</pre>

	: 2. If that does not fix it, send us the output of those commands via chat/email:		: 2a. If that does not fix it, send us the output of those commands via chat/email, as well as the content of your public key to crosscheck with what is in our system:
	<pre>		<pre>
	> ll $HOME/.ssh		> ll $HOME/.ssh
	> date && ssh -vvv MYUSERNAME@m2.iihe.ac.be <-- it needs to be on a specific machines (no mshort/mlong) so that we can read the logs!		> date && ssh -vvv MYUSERNAME@m3.iihe.ac.be <-- it needs to be on a specific machines (no mshort/mlong) so that we can read the logs!
	</pre>		</pre>

			: 2b Also add your public IPv4 so that we can track your connection in the logs, via visiting for instance https://www.whatismyip.com/

	=== MadGraph taking all the cores of a workernode ===		=== MadGraph taking all the cores of a workernode ===

Admin: /* MadGraph taking all the cores of a workernode */

2022-10-03T11:18:42Z

MadGraph taking all the cores of a workernode

← Older revision		Revision as of 11:18, 3 October 2022
Line 30:		Line 30:

	=== MadGraph taking all the cores of a workernode ===		=== MadGraph taking all the cores of a workernode ===
	The default settings for MadGraph is to take all the available cores. This kills the site.		The default settings for MadGraph is to take all the available cores. This kills the site.

			that is why you need to uncomment and set 2 variables in the '''md5_configuration.txt''' file (not the '''dat''' file), '''run_mode''' & '''nb_core'''.<br>
			The run mode should be set to 0, single machine, via:
			run_mode = 0

	If the number of cores used by MadGraph is higher than 1, this needs to be asked to the job scheduler with the following directive added to your HTCondor submit file:		If the number of cores used by MadGraph is higher than 1, this needs to be asked to the job scheduler with the following directive added to your HTCondor submit file:
	<pre> request_cpus = "2" </pre>		<pre> request_cpus = "2" </pre>
	~~Where ppn is the number of cores you request. <br>~~
	To tell MadGraph the number of cores he can take per job, use the following recipe:		To tell MadGraph the number of cores he can take per job, use the following recipe:
	<pre>		<pre>
Line 40:		Line 45:
	save options		save options
	</pre>		</pre>
			or in the '''md5_configuration.txt''':
			nb_core = 1
	Note 'nb_core' and 'request_cpus' must alway be the same value! <br>		Note 'nb_core' and 'request_cpus' must alway be the same value! <br>
	Note also that if you ask for more than one core your time in the queue will probably be longer as the scheduler needs to find the correct amount of free slots on one single machine. We advise against putting this number higher than one unless you really need it for parallel jobs.		Note also that if you ask for more than one core your time in the queue will probably be longer as the scheduler needs to find the correct amount of free slots on one single machine. <br>
			We advise against putting this number higher than one unless you really need it for parallel jobs.

Admin: /* List of the UIs / mX machines: */

2022-02-14T09:28:44Z

List of the UIs / mX machines:

← Older revision		Revision as of 09:28, 14 February 2022
Line 1:		Line 1:
	<br><br>		<br><br>
	=== List of the UIs / mX machines: ===		=== List of the UIs / mX machines: ===
	- m2 , m3 => 20 minutes of CPU time per process <br>		- mshort: m1, m2 , m3 => 20 minutes of CPU time per process <br>
	- m6 , m7 => 1 hour of CPU time per process		- mlong: m4, m5, m6 , m7 => 1 hour of CPU time per process


	=== Keep ssh connection to UI open: ===		=== Keep ssh connection to UI open: ===

Admin: /* MadGraph taking all the cores of a workernode */

2021-12-08T11:33:09Z

MadGraph taking all the cores of a workernode

← Older revision		Revision as of 11:33, 8 December 2021
Line 41:		Line 41:
	save options		save options
	</pre>		</pre>
	Note 'nb_core' and '~~ppn~~' must alway be the same value! <br>		Note 'nb_core' and 'request_cpus' must alway be the same value! <br>
	Note also that if you ask for more than one core your time in the queue will probably be longer as the scheduler needs to find the correct amount of free slots on one single machine. We advise against putting this number higher than one unless you really need it for parallel jobs.		Note also that if you ask for more than one core your time in the queue will probably be longer as the scheduler needs to find the correct amount of free slots on one single machine. We advise against putting this number higher than one unless you really need it for parallel jobs.

Admin: /* MadGraph taking all the cores of a workernode */

2021-12-08T11:06:33Z

MadGraph taking all the cores of a workernode

← Older revision		Revision as of 11:06, 8 December 2021
Line 32:		Line 32:
	=== MadGraph taking all the cores of a workernode ===		=== MadGraph taking all the cores of a workernode ===
	The default settings for MadGraph is to take all the available cores. This kills the site.		The default settings for MadGraph is to take all the available cores. This kills the site.
	If the number of cores used by MadGraph is higher than 1, this needs to be asked to the job scheduler with the following directive added to ~~qsub~~:		If the number of cores used by MadGraph is higher than 1, this needs to be asked to the job scheduler with the following directive added to your HTCondor submit file:
	<pre> ~~-lnodes=1:ppn~~=2 </pre>		<pre> request_cpus = "2" </pre>
	Where ppn is the number of cores you request. <br>		Where ppn is the number of cores you request. <br>
	To tell MadGraph the number of cores he can take per job, use the following recipe:		To tell MadGraph the number of cores he can take per job, use the following recipe: