ELSA3 Upgrade FAQ - Revision history

Admin: /* Large message when using Open OnDemand Terminal */

2026-05-27T12:27:47Z

Large message when using Open OnDemand Terminal

← Older revision		Revision as of 12:27, 27 May 2026
Line 41:		Line 41:
	</pre>		</pre>

	===== Large message when using Open OnDemand Terminal =====		===== Large message when using the Open OnDemand Terminal =====

	When you launch the '''>_ ELSA OpenHPC Cluster Shell Access''' to get to a command-line terminal or use the '''>_Open in Terminal''' option, you see a large error message similar to the one below.		When you launch the '''>_ ELSA OpenHPC Cluster Shell Access''' to get to a command-line terminal or use the '''>_Open in Terminal''' option, you see a large error message similar to the one below.

Admin at 12:27, 27 May 2026

2026-05-27T12:27:28Z

@@ Line 40: / Line 40: @@
 [ssivy@login001 ~]$
 </pre>
 == ELSA3 Upgrade Frequently Asked Questions ==

Admin: /* Job or module command failed with "The following module(s) are unknown" error */

2026-05-18T13:04:05Z

Job or module command failed with "The following module(s) are unknown" error

← Older revision		Revision as of 13:04, 18 May 2026
Line 10:		Line 10:

	If your job or <code>module add</code> command fails and you have an error like <code>Lmod has detected the following error: The following module(s) are unknown:</code> in your '''job.''####''.out''' file, it means that the application or the version of the application you are trying to use is not on the ELSA3 cluster. For an application like Matlab where there are multiple version, simply change your SLURM submit script to select a different version or remove the version entirely and let the system pick the best "default" version. If the application does not exist on the ELSA3 cluster, and you need it for your workflow, please contact Shawn Sivy (ssivy@tcnj.edu) to have it moved over from the old ELSA cluster.		If your job or <code>module add</code> command fails and you have an error like <code>Lmod has detected the following error: The following module(s) are unknown:</code> in your '''job.''####''.out''' file, it means that the application or the version of the application you are trying to use is not on the ELSA3 cluster. For an application like Matlab where there are multiple version, simply change your SLURM submit script to select a different version or remove the version entirely and let the system pick the best "default" version. If the application does not exist on the ELSA3 cluster, and you need it for your workflow, please contact Shawn Sivy (ssivy@tcnj.edu) to have it moved over from the old ELSA cluster.


	To fix the situation where the version is no longer available, look for a line in your submit script like the one below. Note: <code>module add</code> and <code>module load</code> are synonymous.		To fix the situation where the version is no longer available, look for a line in your submit script like the one below. Note: <code>module add</code> and <code>module load</code> are synonymous.

Admin: /* The module command gives me an "attempt to compare string with number" error */

2026-05-18T13:03:16Z

The module command gives me an "attempt to compare string with number" error

← Older revision		Revision as of 13:03, 18 May 2026
Line 26:		Line 26:
	===== The module command gives me an "attempt to compare string with number" error =====		===== The module command gives me an "attempt to compare string with number" error =====

	If you are using the <code>module</code> command such as <code>module avail</code> and get an error like the one below, you need to run the <code>lmod-clear-cache</code> command. ~~You can then re-run your~~ <code>module</code> command again. This error occurs because the caching format used by <code>module</code> differs from the prior version.		If you are using the <code>module</code> command such as <code>module avail</code> and get an error like the one below, you need to run the <code>lmod-clear-cache</code> command. The <code>module</code> command should now work again as expected. This error occurs because the caching format used by <code>module</code> differs from the prior version.

	<pre>		<pre>

Admin: /* ELSA3 Upgrade Issues & Resolutions */

2026-05-18T13:01:44Z

ELSA3 Upgrade Issues & Resolutions

@@ Line 19: / Line 19: @@
 <code>module add matlab/R2025a</code> ''or''  <code>module add matlab</code>
 To see what modules are available, use the <code>module avail</code> command.
 Example: <code>module avail</code> ''or''  <code>module avail matlab</code>
 == ELSA3 Upgrade Frequently Asked Questions ==

Admin: /* ELSA3 Upgrade Frequently Asked Questions */

2026-05-18T12:53:26Z

ELSA3 Upgrade Frequently Asked Questions

← Older revision		Revision as of 12:53, 18 May 2026
Line 51:		Line 51:
	===== Is there a new login for the ELSA3 test cluster? =====		===== Is there a new login for the ELSA3 test cluster? =====
	No. Just use your regular TCNJ username and password like you do on the current ELSA cluster.		No. Just use your regular TCNJ username and password like you do on the current ELSA cluster.

	<!--		<!--
	===== How do I access the test cluster? =====		===== How do I access the test cluster? =====

Admin: /* Is there a new login for the ELSA3 test cluster? */

2026-05-18T12:53:08Z

Is there a new login for the ELSA3 test cluster?

← Older revision		Revision as of 12:53, 18 May 2026
Line 50:		Line 50:

	===== Is there a new login for the ELSA3 test cluster? =====		===== Is there a new login for the ELSA3 test cluster? =====
	~~Nope~~. Just use your regular TCNJ username and password like you do on the current ELSA cluster.		No. Just use your regular TCNJ username and password like you do on the current ELSA cluster.

	<!--		<!--
Line 87:		Line 87:
	* 1 Open OnDemand node		* 1 Open OnDemand node
	-->		-->

	===== When will ELSA3 launch into production? =====		===== When will ELSA3 launch into production? =====
	ELSA will be upgraded on May 21 & 22nd (Commencement days). Because of the campus power outage on Sunday, May 24th and Memorial Day on Monday, May 25th, ELSA3 will be down until Tuesday, May 26th. I hope the have the system up and operational in the afternoon.		ELSA will be upgraded on May 21 & 22nd (Commencement days). Because of the campus power outage on Sunday, May 24th and Memorial Day on Monday, May 25th, ELSA3 will be down until Tuesday, May 26th. I hope the have the system up and operational in the afternoon.

Admin: /* ELSA3 Upgrade/Testing Frequently Asked Questions */

2026-05-18T12:52:25Z

ELSA3 Upgrade/Testing Frequently Asked Questions

Admin at 15:17, 30 April 2026

2026-04-30T15:17:01Z

← Older revision		Revision as of 15:17, 30 April 2026
Line 1:		Line 1:
	== ELSA3 Upgrade Issues & Resolutions ==		== ELSA3 Upgrade Issues & Resolutions ==

			===== SSH host key/identification errror when connecting to elsa.hpc.tcnj.edu =====

			If you can't connect to '''elsa.hpc.tcnj.edu''' using your SSH client because of a host key/identification error, see [[HPC_Cluster_ELSA3_Host_Key_Change\|these instructions]] to resolve the issue.

			This '''does not''' affect using the web interface and its built-in terminal in Open OnDemand.

	===== Job or module command failed with "The following module(s) are unknown" error =====		===== Job or module command failed with "The following module(s) are unknown" error =====

Admin: /* Is there an entire new cluster running for this test? */

2026-04-09T19:10:38Z

Is there an entire new cluster running for this test?

← Older revision		Revision as of 19:10, 9 April 2026
Line 74:		Line 74:
	* 1 GPU node with 4 x RTX 2080 GPUs		* 1 GPU node with 4 x RTX 2080 GPUs
	* 1 GPU node with 4 x RTX A5000 GPUs		* 1 GPU node with 4 x RTX A5000 GPUs
	* 1 GPU node with 4 x L40S GPUs		* 1 GPU node with 4 x L40S GPUs (may not always be available depending on L40S needs on the current cluster)
	* 1 Visualization node with an L40 GPU (new!) for graphics rendering		* 1 Visualization node with an L40 GPU (new!) for graphics rendering
	* 1 login node		* 1 login node

← Older revision		Revision as of 12:52, 18 May 2026
Line 25:		Line 25:
	Example: <code>module avail</code> ''or'' <code>module avail matlab</code>		Example: <code>module avail</code> ''or'' <code>module avail matlab</code>

	== ELSA3 Upgrade~~/Testing~~ Frequently Asked Questions ==		== ELSA3 Upgrade Frequently Asked Questions ==

	===== So why is there a new cluster? =====		===== So why is there a new cluster? =====
Line 32:		Line 32:
	===== Does this cluster upgrade affect the virtual machines (VMs) on the "MoOSE" virtual infrastructure? =====		===== Does this cluster upgrade affect the virtual machines (VMs) on the "MoOSE" virtual infrastructure? =====
	No. The virtualization system is a separate cluster with its own servers and software. However, I will look to upgrade the underlying virtualization software this summer, but that will (mostly) be transparent to the end-users of that system.		No. The virtualization system is a separate cluster with its own servers and software. However, I will look to upgrade the underlying virtualization software this summer, but that will (mostly) be transparent to the end-users of that system.
			<!--
	===== Why do I need to test anything? =====		===== Why do I need to test anything? =====
	Like moving from one version of Windows to another or one version of MacOS to another, there are some changes that may cause issues with the existing software applications. While I have done some basic testing to make sure there aren't obvious issues with the applications, I am inviting you to also try out some of your applications and double-check my testing.		Like moving from one version of Windows to another or one version of MacOS to another, there are some changes that may cause issues with the existing software applications. While I have done some basic testing to make sure there aren't obvious issues with the applications, I am inviting you to also try out some of your applications and double-check my testing.
Line 44:		Line 44:
	===== Both my students and I are too busy to do any testing. What will happen if we don't do any testing? =====		===== Both my students and I are too busy to do any testing. What will happen if we don't do any testing? =====
	That's not a problem. I just wanted to provide you with an opportunity to test drive the new cluster before it goes into production after the spring semester. If you don't any have time to test now, we can work together later on to resolve any issues you encounter.		That's not a problem. I just wanted to provide you with an opportunity to test drive the new cluster before it goes into production after the spring semester. If you don't any have time to test now, we can work together later on to resolve any issues you encounter.
			-->

	===== Are my files also available on this new cluster? =====		===== Are my files also available on this new cluster? =====
Line 51:		Line 52:
	Nope. Just use your regular TCNJ username and password like you do on the current ELSA cluster.		Nope. Just use your regular TCNJ username and password like you do on the current ELSA cluster.

			<!--
	===== How do I access the test cluster? =====		===== How do I access the test cluster? =====
	For the test, you can use these names to access the ELSA3 cluster test:		For the test, you can use these names to access the ELSA3 cluster test:
Line 84:		Line 86:
	* 1 login node		* 1 login node
	* 1 Open OnDemand node		* 1 Open OnDemand node
			-->
	===== When will ELSA3 launch into production? =====		===== When will ELSA3 launch into production? =====
	ELSA will be upgraded on May 21 & 22nd (Commencement days). Because of the campus power outage on Sunday, May 24th and Memorial Day on Monday, May 25th, ELSA3 will be down until Tuesday, May 26th. I hope the have the system up and operational in the afternoon.		ELSA will be upgraded on May 21 & 22nd (Commencement days). Because of the campus power outage on Sunday, May 24th and Memorial Day on Monday, May 25th, ELSA3 will be down until Tuesday, May 26th. I hope the have the system up and operational in the afternoon.