HPC Docs - User contributions [en]

HPC Cluster ELSA3 Host Key Change

2026-04-30T15:17:51Z

Admin: /* SSH on MacOS X/MS-Windows/Linux */

= Remote Host Key/Identification Changed Error =

When trying to connect to '''elsa.hpc.tcnj.edu''' using SSH after the ELSA3 upgrade, you will probably get an error about the host key or host identification changed.

Below are instructions on how to resolve this error when using the command-line SSH program on Mac OS X, but the commands are identical if you are using Linux or the Microsoft Windows built-in SSH client. Near the bottom of this page are instructions if you are on Microsoft Windows and using PuTTY or MobaXterm SSH client software. If you are using a different SSH client, you will need to consult its documentation for instructions on how to resolve host key issues.

== SSH on MacOS X/MS-Windows/Linux ==
When attempting to use the terminal SSH client, you will see a message similar to the screenshot below stating '''WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!''', followed by some additional "scary" text and finally the message that the '''Host key verification has failed'''. Note that the text may vary slightly based on the operating system (Mac/Windows/Linux) you are using. These screenshots were captured on a Mac.

[[File:MacOSX-host-key-change.png]]

To resolve the issue, you need to remove the old host key for '''elsa.hpc.tcnj.edu''' so that you can accept the new one. To do so, run the command <code>ssh-keygen -R elsa.hpc.tcnj.edu</code> in the terminal. Your output should be similar to the screenshot below. Again, it may vary based on your operating system, but you want to see that it found '''elsa.hpc.tcnj.edu''' and updated the file.

[[File:MacOSX-remove-host-key.png]]

After the existing host key has been removed, you can run the <code>ssh</code> command in your terminal again. This time it will ask you to accept the new host key. If you accepted it, you won't be asked again. You need to type the full word <code>yes</code> and press the ENTER/RETURN key.

[[File:MacOSX-accept-host-key.png]]

That's it. You can now continue to use the ELSA3 HPC cluster.

== PuTTY on Microsoft Windows ==
Resolving the host key/identification change when using PuTTY is pretty straightforward. Simply click the '''Accept''' button to replace the old host key with the new one.

[[File:Putty-host-key-change.png]]

== MobaXterm on Microsoft Windows ==
Resolving the host key/identification change when using MobaXterm is straightforward. Simply click the '''OK''' button to replace the old host key with the new one.

[[File:MobaXterm-host-key-change.png]]

ELSA3 Upgrade FAQ

2026-04-30T15:17:01Z

Admin:

== 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 =====

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.

<code>module add matlab/R2021a</code>

and replace it with one of these

<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/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, and /courses and are available and are currently shared between the two clusters. Because of how the global /scratch system works, it won't be available until after the upgrade.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.hpc.tcnj.edu

Via Web: https://ondemand-test3.hpc.tcnj.edu/

When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the second "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Sunday, May 3rd. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks before the final cut-over on May 21st & 22nd.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
* WebMO website
* ELSA VDI Desktop under Interactive Applications in Open OnDemand
* ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
* Access to /scratch

These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 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 login node
* 1 Open OnDemand node

===== 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.

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

HPC Cluster ELSA3 Host Key Change

2026-04-30T15:10:35Z

Admin: /* Remote Host Key/Identification Changed Error */

= Remote Host Key/Identification Changed Error =

When trying to connect to '''elsa.hpc.tcnj.edu''' using SSH after the ELSA3 upgrade, you will probably get an error about the host key or host identification changed.

Below are instructions on how to resolve this error when using the command-line SSH program on Mac OS X, but the commands are identical if you are using Linux or the Microsoft Windows built-in SSH client. Near the bottom of this page are instructions if you are on Microsoft Windows and using PuTTY or MobaXterm SSH client software. If you are using a different SSH client, you will need to consult its documentation for instructions on how to resolve host key issues.

== SSH on MacOS X/MS-Windows/Linux ==
When attempting to use the terminal SSH client, you will see a message similar to the screenshot below stating '''WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!''', followed by some additional "scary" text and finally the message that the '''Host key verification has failed'''. Note that the text may vary slightly based on the operating system (Mac/Windows/Linux) you are using. This was captured on a Mac.

[[File:MacOSX-host-key-change.png]]

To resolve the issue, you need to remove the old host key for '''elsa.hpc.tcnj.edu''' so that you can accept the new one. To do so, run the command <code>ssh-keygen -R elsa.hpc.tcnj.edu</code> in the terminal. Your output should be similar to the screenshot below. Again, it may vary based on your operating system, but you want to see that it found '''elsa.hpc.tcnj.edu''' and updated the file.

[[File:MacOSX-remove-host-key.png]]

After the existing host key has been removed, you can run the <code>ssh</code> command in your terminal again. This time it will ask you to accept the new host key. If you accepted it, you won't be asked again. You need to type the full word <code>yes</code> and press the ENTER/RETURN key.

[[File:MacOSX-accept-host-key.png]]

That's it. You can now continue to use the ELSA3 HPC cluster.

== PuTTY on Microsoft Windows ==
Resolving the host key/identification change when using PuTTY is pretty straightforward. Simply click the '''Accept''' button to replace the old host key with the new one.

[[File:Putty-host-key-change.png]]

== MobaXterm on Microsoft Windows ==
Resolving the host key/identification change when using MobaXterm is straightforward. Simply click the '''OK''' button to replace the old host key with the new one.

[[File:MobaXterm-host-key-change.png]]

HPC Cluster ELSA3 Host Key Change

2026-04-30T15:09:10Z

Admin:

= Remote Host Key/Identification Changed Error =

When trying to connect to '''elsa.hpc.tcnj.edu''' using SSH after the ELSA3 upgrade, you will probably get an error about the host key or host identification changed.

Below are instructions on how to resolve this error when using the command-line SSH program on Mac OS X, but the commands are identical if you are using Linux or the Microsoft Windows built-in SSH client. Near the bottom of this page are instructions if you are on Microsoft Windows and using PuTTY or MobaXterm SSH client software. If you are using a different SSH client, you will need to consult its documentation for instructions on how to resolve host key issues.

== SSH on MacOS X/MS-Windows/Linux ==
When attempting to use the terminal SSH client, you will see a message similar to the screenshot below stating '''WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!''', followed by some additional "scary" text and finally the message that the '''Host key verification has failed'''. Note that the text may vary slightly based on the operating system (Mac/Windows/Linux) you are using. This was captured on a Mac.

[[File:MacOSX-host-key-change.png]]

To resolve the issue, you need to remove the old host key for '''elsa.hpc.tcnj.edu''' so that you can accept the new one. To do so, run the command <code>ssh-keygen -R elsa.hpc.tcnj.edu</code> in the terminal. Your output should be similar to the screenshot below. Again, it may vary based on your operating system, but you want to see that it found '''elsa.hpc.tcnj.edu''' and updated the file.

[[File:MacOSX-remove-host-key.png]]

After the existing host key has been removed, you can run the <code>ssh</code> command in your terminal again. This time it will ask you to accept the new host key. If accepted, it won't ask you again the next time. You need to type the full word <code>yes</code> and press the ENTER/RETURN key.

[[File:MacOSX-accept-host-key.png]]

That's it. You can now continue to use the ELSA3 HPC cluster.

== PuTTY on Microsoft Windows ==
Resolving the host key/identification change when using PuTTY is pretty straightforward. Simply click the '''Accept''' button to replace the old host key with the new one.

[[File:Putty-host-key-change.png]]

== MobaXterm on Microsoft Windows ==
Resolving the host key/identification change when using MobaXterm is straightforward. Simply click the '''OK''' button to replace the old host key with the new one.

[[File:MobaXterm-host-key-change.png]]

HPC Cluster ELSA3 Host Key Change

2026-04-30T15:07:48Z

Admin:

=== Remote Host Key/Identification Changed Error ===

When trying to connect to '''elsa.hpc.tcnj.edu''' using SSH after the ELSA3 upgrade, you will probably get an error about the host key or host identification changed.

Below are instructions on how to resolve this error when using the command-line SSH program on Mac OS X, but the commands are identical if you are using Linux or the Microsoft Windows built-in SSH client. Near the bottom of this page are instructions if you are on Microsoft Windows and using PuTTY or MobaXterm SSH client software. If you are using a different SSH client, you will need to consult its documentation for instructions on how to resolve host key issues.

== SSH on MacOS X/MS-Windows/Linux ==
When attempting to use the terminal SSH client, you will see a message similar to the screenshot below stating '''WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!''', followed by some additional "scary" text and finally the message that the '''Host key verification has failed'''. Note that the text may vary slightly based on the operating system (Mac/Windows/Linux) you are using. This was captured on a Mac.

[[File:MacOSX-host-key-change.png]]

To resolve the issue, you need to remove the old host key for '''elsa.hpc.tcnj.edu''' so that you can accept the new one. To do so, run the command <code>ssh-keygen -R elsa.hpc.tcnj.edu</code> in the terminal. Your output should be similar to the screenshot below. Again, it may vary based on your operating system, but you want to see that it found '''elsa.hpc.tcnj.edu''' and updated the file.

[[File:MacOSX-remove-host-key.png]]

After the existing host key has been removed, you can run the <code>ssh</code> command in your terminal again. This time it will ask you to accept the new host key. If accepted, it won't ask you again the next time. You need to type the full word <code>yes</code> and press the ENTER/RETURN key.

[[File:MacOSX-accept-host-key.png]]

That's it. You can now continue to use the ELSA3 HPC cluster.

== PuTTY on Microsoft Windows ==
Resolving the host key/identification change when using PuTTY is pretty straightforward. Simply click the '''Accept''' button to replace the old host key with the new one.

[[File:Putty-host-key-change.png]]

== MobaXterm on Microsoft Windows ==
Resolving the host key/identification change when using MobaXterm is straightforward. Simply click the '''OK''' button to replace the old host key with the new one.

[[File:MobaXterm-host-key-change.png]]

HPC Cluster ELSA3 Host Key Change

2026-04-30T15:06:06Z

Admin: /* MobaXterm on Microsoft Windows */

=== Remote Host Key/Identification Changed Error ===

When trying to connect to '''elsa.hpc.tcnj.edu''' using SSH after the ELSA3 upgrade, you will probably get an error about the host key or host identification changed.

Below are instructions on how to resolve this error when using the command-line SSH program on Mac OS X, but the commands are identical if you are using Linux or the Microsoft Windows built-in SSH client. Near the bottom of this page are instructions if you are on Microsoft Windows and using PuTTY or MobaXterm SSH client software.

== SSH on MacOS X/MS-Windows/Linux ==
When attempting to use the terminal SSH client, you will see a message similar to the screenshot below stating '''WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!''', followed by some additional "scary" text and finally the message that the '''Host key verification has failed'''. Note that the text may vary slightly based on the operating system (Mac/Windows/Linux) you are using. This was captured on a Mac.

[[File:MacOSX-host-key-change.png]]

To resolve the issue, you need to remove the old host key for '''elsa.hpc.tcnj.edu''' so that you can accept the new one. To do so, run the command <code>ssh-keygen -R elsa.hpc.tcnj.edu</code> in the terminal. Your output should be similar to the screenshot below. Again, it may vary based on your operating system, but you want to see that it found '''elsa.hpc.tcnj.edu''' and updated the file.

[[File:MacOSX-remove-host-key.png]]

After the existing host key has been removed, you can run the <code>ssh</code> command in your terminal again. This time it will ask you to accept the new host key. If accepted, it won't ask you again the next time. You need to type the full word <code>yes</code> and press the ENTER/RETURN key.

[[File:MacOSX-accept-host-key.png]]

That's it. You can now continue to use the ELSA3 HPC cluster.

== PuTTY on Microsoft Windows ==
Resolving the host key/identification change when using PuTTY is pretty straightforward. Simply click the '''Accept''' button to replace the old host key with the new one.

[[File:Putty-host-key-change.png]]

== MobaXterm on Microsoft Windows ==
Resolving the host key/identification change when using MobaXterm is straightforward. Simply click the '''OK''' button to replace the old host key with the new one.

[[File:MobaXterm-host-key-change.png]]

HPC Cluster ELSA3 Host Key Change

2026-04-30T15:05:07Z

Admin: /* SSH on MacOS X/MS-Windows/Linux */

=== Remote Host Key/Identification Changed Error ===

When trying to connect to '''elsa.hpc.tcnj.edu''' using SSH after the ELSA3 upgrade, you will probably get an error about the host key or host identification changed.

Below are instructions on how to resolve this error when using the command-line SSH program on Mac OS X, but the commands are identical if you are using Linux or the Microsoft Windows built-in SSH client. Near the bottom of this page are instructions if you are on Microsoft Windows and using PuTTY or MobaXterm SSH client software.

== SSH on MacOS X/MS-Windows/Linux ==
When attempting to use the terminal SSH client, you will see a message similar to the screenshot below stating '''WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!''', followed by some additional "scary" text and finally the message that the '''Host key verification has failed'''. Note that the text may vary slightly based on the operating system (Mac/Windows/Linux) you are using. This was captured on a Mac.

[[File:MacOSX-host-key-change.png]]

To resolve the issue, you need to remove the old host key for '''elsa.hpc.tcnj.edu''' so that you can accept the new one. To do so, run the command <code>ssh-keygen -R elsa.hpc.tcnj.edu</code> in the terminal. Your output should be similar to the screenshot below. Again, it may vary based on your operating system, but you want to see that it found '''elsa.hpc.tcnj.edu''' and updated the file.

[[File:MacOSX-remove-host-key.png]]

After the existing host key has been removed, you can run the <code>ssh</code> command in your terminal again. This time it will ask you to accept the new host key. If accepted, it won't ask you again the next time. You need to type the full word <code>yes</code> and press the ENTER/RETURN key.

[[File:MacOSX-accept-host-key.png]]

That's it. You can now continue to use the ELSA3 HPC cluster.

== PuTTY on Microsoft Windows ==
Resolving the host key/identification change when using PuTTY is pretty straightforward. Simply click the '''Accept''' button to replace the old host key with the new one.

[[File:Putty-host-key-change.png]]

== MobaXterm on Microsoft Windows ==
Resolving the host key/identification change when using MobaXterm is pretty straightforward. Simply click the '''OK''' button to replace the old host key with the new one.

[[File:MobaXterm-host-key-change.png]]

HPC Cluster ELSA3 Host Key Change

2026-04-30T15:04:24Z

Admin: /* SSH on MacOS X/MS-Windows/Linux */

=== Remote Host Key/Identification Changed Error ===

When trying to connect to '''elsa.hpc.tcnj.edu''' using SSH after the ELSA3 upgrade, you will probably get an error about the host key or host identification changed.

Below are instructions on how to resolve this error when using the command-line SSH program on Mac OS X, but the commands are identical if you are using Linux or the Microsoft Windows built-in SSH client. Near the bottom of this page are instructions if you are on Microsoft Windows and using PuTTY or MobaXterm SSH client software.

== SSH on MacOS X/MS-Windows/Linux ==
When attempting to use the terminal SSH client, you will see a message similar to the screenshot below stating '''WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!''', followed by some additional "scary" text and finally the message that the '''Host key verification has failed'''. Note that the text may vary slightly based on the operating system (Mac/Windows/Linux) you are using. This was captured on a Mac.

[[File:MacOSX-host-key-change.png]]

To resolve the issue, you need to remove the old host key for '''elsa.hpc.tcnj.edu''' so that you can accept the new one. To do so, run the command <code>ssh-keygen -R elsa.hpc.tcnj.edu</code> in the terminal. Your output should be similar to the screenshot below. Again, it may vary based on your operating system, but you want to see that it found '''elsa.hpc.tcnj.edu''' and updated the file.

[[File:MacOSX-remove-host-key.png]]

After the existing host key has been removed, you can run the <code>ssh</code> command in your terminal again. This time it will ask you to accept the new host key. You will only be asked this once. If accepted, it won't ask you again the next time. You need to type the full word <code>yes</code> and press the ENTER/RETURN key.

[[File:MacOSX-accept-host-key.png]]

That's it. You can now continue to use the ELSA3 HPC cluster.

== PuTTY on Microsoft Windows ==
Resolving the host key/identification change when using PuTTY is pretty straightforward. Simply click the '''Accept''' button to replace the old host key with the new one.

[[File:Putty-host-key-change.png]]

== MobaXterm on Microsoft Windows ==
Resolving the host key/identification change when using MobaXterm is pretty straightforward. Simply click the '''OK''' button to replace the old host key with the new one.

[[File:MobaXterm-host-key-change.png]]

HPC Cluster ELSA3 Host Key Change

2026-04-30T15:03:44Z

Admin: /* SSH on MacOS X/MS-Windows/Linux */

=== Remote Host Key/Identification Changed Error ===

When trying to connect to '''elsa.hpc.tcnj.edu''' using SSH after the ELSA3 upgrade, you will probably get an error about the host key or host identification changed.

Below are instructions on how to resolve this error when using the command-line SSH program on Mac OS X, but the commands are identical if you are using Linux or the Microsoft Windows built-in SSH client. Near the bottom of this page are instructions if you are on Microsoft Windows and using PuTTY or MobaXterm SSH client software.

== SSH on MacOS X/MS-Windows/Linux ==
When attempting to use the terminal SSH client, you will see a message similar to the screenshot below stating '''WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!''', followed by some additional "scary" text and finally the message that the '''Host key verification has failed'''. Note that the text may vary slightly based on the operating system (Mac/Windows/Linux) you are using. This was captured on a Mac.

[[File:MacOSX-host-key-change.png]]

To resolve the issue, you need to remove the old host key for '''elsa.hpc.tcnj.edu''' so that you can accept the new one. To do so, run the command <code>ssh-keygen -R elsa.hpc.tcnj.edu</code> in the terminal. Your output should be similar to the screenshot below. Again, it may vary based on your operating system, but you want to see that it found '''elsa.hpc.tcnj.edu''' and updated the file.

[[File:MacOSX-remove-host-key.png]]

After the existing host key has been removed, you can run the ssh command in your terminal again. This time it will ask you to accept the new host key. You will only be asked this once. If accepted, it won't ask you again the next time. You need to type the full word <code>yes</code> and press the ENTER/RETURN key.

[[File:MacOSX-accept-host-key.png]]

That's it. You can now continue to use the ELSA3 HPC cluster.

== PuTTY on Microsoft Windows ==
Resolving the host key/identification change when using PuTTY is pretty straightforward. Simply click the '''Accept''' button to replace the old host key with the new one.

[[File:Putty-host-key-change.png]]

== MobaXterm on Microsoft Windows ==
Resolving the host key/identification change when using MobaXterm is pretty straightforward. Simply click the '''OK''' button to replace the old host key with the new one.

[[File:MobaXterm-host-key-change.png]]

HPC Cluster ELSA3 Host Key Change

2026-04-30T15:03:13Z

Admin:

=== Remote Host Key/Identification Changed Error ===

When trying to connect to '''elsa.hpc.tcnj.edu''' using SSH after the ELSA3 upgrade, you will probably get an error about the host key or host identification changed.

Below are instructions on how to resolve this error when using the command-line SSH program on Mac OS X, but the commands are identical if you are using Linux or the Microsoft Windows built-in SSH client. Near the bottom of this page are instructions if you are on Microsoft Windows and using PuTTY or MobaXterm SSH client software.

== SSH on MacOS X/MS-Windows/Linux ==
When attempting to use the terminal SSH client, you will see a message similar to the screenshot below stating '''WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!''', followed by some additional "scary" text and finally the message that the '''Host key verification has failed'''. Note that the text may vary slightly based on the operating system (Mac/Windows/Linux) you are using. This was captured on a Mac.

[[File:MacOSX-host-key-change.png]]

To resolve the issue, you need to remove the old host key for elsa.hpc.tcnj.edu so that you can accept the new one. To do so, run the command <code>ssh-keygen -R elsa.hpc.tcnj.edu</code> in the terminal. Your output should be similar to the screenshot below. Again, it may vary based on your operating system, but you want to see that it found '''elsa.hpc.tcnj.edu''' and updated the file.

[[File:MacOSX-remove-host-key.png]]

After the existing host key has been removed, you can run the ssh command in your terminal again. This time it will ask you to accept the new host key. You will only be asked this once. If accepted, it won't ask you again the next time. You need to type the full word <code>yes</code> and press the ENTER/RETURN key.

[[File:MacOSX-accept-host-key.png]]

That's it. You can now continue to use the ELSA3 HPC cluster.

== PuTTY on Microsoft Windows ==
Resolving the host key/identification change when using PuTTY is pretty straightforward. Simply click the '''Accept''' button to replace the old host key with the new one.

[[File:Putty-host-key-change.png]]

== MobaXterm on Microsoft Windows ==
Resolving the host key/identification change when using MobaXterm is pretty straightforward. Simply click the '''OK''' button to replace the old host key with the new one.

[[File:MobaXterm-host-key-change.png]]

HPC Cluster ELSA3 Host Key Change

2026-04-30T14:39:34Z

Admin: Created page with "File:MacOSX-host-key-change.png File:MacOSX-remove-host-key.png File:MacOSX-accept-host-key.png File:Putty-host-key-change.png File:MobaXterm-host-key-change.png"

[[File:MacOSX-host-key-change.png]]

[[File:MacOSX-remove-host-key.png]]

[[File:MacOSX-accept-host-key.png]]

[[File:Putty-host-key-change.png]]

[[File:MobaXterm-host-key-change.png]]

File:MacOSX-post-quantum-warning.png

2026-04-30T14:35:07Z

Admin: Screenshot of MacOS X show post-quantum warning message.

== Summary ==
Screenshot of MacOS X show post-quantum warning message.

File:MacOSX-accept-host-key.png

2026-04-30T14:34:37Z

Admin: Screenshot of MacOS X showing acceptance of new host key.

== Summary ==
Screenshot of MacOS X showing acceptance of new host key.

File:MacOSX-remove-host-key.png

2026-04-30T14:34:10Z

Admin: Screenshot of MacOS X showing removal of old host key.

== Summary ==
Screenshot of MacOS X showing removal of old host key.

File:MacOSX-host-key-change.png

2026-04-30T14:33:40Z

Admin: Screenshot of MacOS X terminal showing SSH host key changed error.

== Summary ==
Screenshot of MacOS X terminal showing SSH host key changed error.

File:Putty-host-key-change.png

2026-04-30T14:28:31Z

Admin: Screenshot of warning from Putty about SSH server key has changed.

== Summary ==
Screenshot of warning from Putty about SSH server key has changed.

File:MobaXterm-host-key-change.png

2026-04-30T14:28:12Z

Admin: Screenshot of warning from MobaXterm about SSH server key has changed.

== Summary ==
Screenshot of warning from MobaXterm about SSH server key has changed.

ELSA3 Upgrade FAQ

2026-04-09T19:10:38Z

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

== ELSA3 Upgrade Issues & Resolutions ==

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

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.

<code>module add matlab/R2021a</code>

and replace it with one of these

<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/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, and /courses and are available and are currently shared between the two clusters. Because of how the global /scratch system works, it won't be available until after the upgrade.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.hpc.tcnj.edu

Via Web: https://ondemand-test3.hpc.tcnj.edu/

When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the second "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Sunday, May 3rd. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks before the final cut-over on May 21st & 22nd.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
* WebMO website
* ELSA VDI Desktop under Interactive Applications in Open OnDemand
* ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
* Access to /scratch

These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 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 login node
* 1 Open OnDemand node

===== 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.

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

ELSA3 Upgrade FAQ

2026-04-09T19:09:41Z

Admin: /* Are my files also available on this new cluster? */

== ELSA3 Upgrade Issues & Resolutions ==

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

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.

<code>module add matlab/R2021a</code>

and replace it with one of these

<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/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, and /courses and are available and are currently shared between the two clusters. Because of how the global /scratch system works, it won't be available until after the upgrade.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.hpc.tcnj.edu

Via Web: https://ondemand-test3.hpc.tcnj.edu/

When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the second "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Sunday, May 3rd. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks before the final cut-over on May 21st & 22nd.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
* WebMO website
* ELSA VDI Desktop under Interactive Applications in Open OnDemand
* ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
* Access to /scratch

These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== 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.

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

ELSA3 Upgrade FAQ

2026-04-09T19:08:07Z

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

== ELSA3 Upgrade Issues & Resolutions ==

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

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.

<code>module add matlab/R2021a</code>

and replace it with one of these

<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/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.hpc.tcnj.edu

Via Web: https://ondemand-test3.hpc.tcnj.edu/

When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the second "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Sunday, May 3rd. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks before the final cut-over on May 21st & 22nd.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
* WebMO website
* ELSA VDI Desktop under Interactive Applications in Open OnDemand
* ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
* Access to /scratch

These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== 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.

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

ELSA3 Upgrade FAQ

2026-04-09T19:07:50Z

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

== ELSA3 Upgrade Issues & Resolutions ==

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

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.

<code>module add matlab/R2021a</code>

and replace it with one of these

<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/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.hpc.tcnj.edu

Via Web: https://ondemand-test3.hpc.tcnj.edu/

When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the second "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Sunday, May 3rd. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks before the final cut-over on May 21st & 22nd.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
* WebMO website
* ELSA VDI Desktop under Interactive Applications in Open OnDemand
* ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)

These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== 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.

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

ELSA3 Upgrade FAQ

2026-04-09T19:07:04Z

Admin: /* When will ELSA3 launch into production? */

== ELSA3 Upgrade Issues & Resolutions ==

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

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.

<code>module add matlab/R2021a</code>

and replace it with one of these

<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/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.hpc.tcnj.edu

Via Web: https://ondemand-test3.hpc.tcnj.edu/

When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the second "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Sunday, May 3rd. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks before the final cut-over on May 21st & 22nd.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== 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.

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

ELSA3 Upgrade FAQ

2026-04-09T19:04:00Z

Admin: /* How long is the testing period of the first "cluster crunch"? */

== ELSA3 Upgrade Issues & Resolutions ==

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

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.

<code>module add matlab/R2021a</code>

and replace it with one of these

<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/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.hpc.tcnj.edu

Via Web: https://ondemand-test3.hpc.tcnj.edu/

When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the second "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Sunday, May 3rd. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks before the final cut-over on May 21st & 22nd.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

HPC Cluster Projection Instructions

2026-03-12T18:38:17Z

Admin: /* Resources */

== Presentation Tips ==
When creating assets to display on the ELSA HPC cluster room glass, keep these things in mind:
* Use a black background if possible since black appears invisible when displayed on the glass
* Use bright, slightly oversaturated colors for images and text
* Provide text describing what the viewer is seeing, and remember to make it for a general audience
* Make sure your text is succinct and uses a font type and size that displays well when projected
* Use the templates below which take the window frame in the middle of the display into account

== Resources ==

[[File:PowerPoint_icon.png|alt=PowerPoint logo]] [[Media:ELSA template.pptx|Download PowerPoint presentation with sample slides for ELSA HPC cluster projection]]

<HR>

[[File:ELSA template.png|alt=Example image formatted for ELSA HPC cluster projection|200px|Example image formatted for ELSA HPC cluster projection]]

[[Media:ELSA template.png|Download image]] - Right-click link and choose '''Save Link As...''' in the pop-up.

<HR>

[[File:Example-ELSA-Projection.mp4|alt=Example video formatted for ELSA HPC cluster projectsion|Example video formatted for ELSA HPC cluster projection]]

[[Media:Example-ELSA-Projection.mp4|Download video of ELSA HPC cluster projection]] - Right-click link and choose '''Save Link As...''' in the pop-up.

''A special thanks to Nick Battista from TCNJ's Mathematics and Statistics department for contributing to the sample slides.''

CSC360-Computer-Networking-with-Li

2026-03-12T18:35:08Z

Admin: /* Accessing Your Kali Linux Virtual Machine */

== CSC360 - Computer Networking with Dr. Li ==

=== Accessing Your Kali Linux Virtual Machine ===

You will need to access to a computer with Firefox or Chrome. This can be a Windows, Mac or Linux machine. If you are off-campus, you will need to use the campus VPN first.
<br><br>
Point Firefox to this URL:

https://moose.hpc.tcnj.edu:8006/
<br><br>
You should get a login screen like the following:

[[File:Promox Login.png|alt=Proxmox login dialog box|none|Promox Login]]

Pull down the '''Realm''' option and choose '''TCNJ LDAP authentication server'''.

In the User name and Password fields to enter your regular TCNJ username and password.
Click '''Login'''.

After logging in you may need to expand the menus on the left side under hpc-moose1, hpc-moose2, hpc-moose3 or hpc-moose4 to see your server. It should match the one you were assigned.

Click on your server name to get additional info.

[[File:Proxmox Console.png|alt=Promox main console screen|800px|Proxmox Console]]

You can open a console window by using one of the following methods:

# Double-click on your server name.
# Right-click on your server name and choose '''>_ Console'''.
# While your server is selected, click on '''>_ Console''' in the upper right side of the page.
# While your server is selected, click on '''>_ Console''' in the menu toward the middle of the page.

The first three options will pop-out a separate console window. You may need to allow pop-ups in the browser (it will warn you). The last option will display the console in the page itself. It is recommended that you use one of the first three options.

'''Note:''' You will most likely need to resize the pop-out window to display the entire console screen.

If you have any issues opening a connection or encounter other “funkiness” with the console window, close it and try to open it again. If problems continue, try using a "private" or "incognito" window in your browser to access the server since there may be issues with the browser cache or other browser hiccups.

[[File:Kali Desktop.png|alt=Kali Linux desktop|800px|Kali Linux Desktop]]

Once the console is open, you can login using the credentials provided to you in class. You may experience some delays especially with quick keypresses but it should get more consistent as you use it. When done, simply close the pop-out console window (you may also want to logout of the Kali Linux GUI first) and click the '''Logout''' button in the upper-right corner of the Proxmox page.

You can also '''Stop''' and '''Start''' your VM (in case it goes unresponsive or crashes) by right-clicking on the VM name at the left side of the page and choosing the appropriate option from the pop-up menu. Alternately you can click the power button in title bar of the console window and choose an appropriate action. Don't use the '''Shutdown''' option if your VM is unresponsive.

=== Video Demonstration ===
<youtube>https://www.youtube.com/watch?v=vzt-K05Y4NI</youtube>

HPC Cluster About

2026-03-12T18:27:11Z

Admin: /* Acknowledgements */

== ELSA High Performance Computing Cluster ==

ELSA (Electronic Laboratory for Science and Analysis) is TCNJ's heterogeneous High Performance Computing (HPC) cluster named after the famous [[wikipedia:Born_Free|“Born Free”]] lioness and our mascot.

TCNJ’s High Performance Computing (HPC) Cluster is located in the new STEM Building. The Cluster consists of eight server racks of High-Performance Computing (HPC) equipment housed in a 400 square-foot facility equipped with centralized cooling, power, and backup power. The computing cluster contains 68 nodes, providing 4,000 CPU cores supporting compute, big data and virtualization workloads. A subset of nodes includes a total of 99 graphic processing units for accelerated computing. Approximately six petabytes of network-based storage provide long-term and “scratch” space for data intensive applications. There are six identical storage servers. Three servers are in the STEM cluster room and the others in a dedicated, climate-controlled space in the Green Hall datacenter. Data from the STEM storage server is replicated daily. Cluster node interconnects consist of both 10Gb and 25Gb Ethernet while storage has 100GbE networking. The cluster can support multiple types of workloads including HPC, GPU-based calculations, remote visualization, big data, and virtualization. The cluster is designed, with the aid of open-source orchestration software, to be easily reconfigured to meet the evolving research and pedagogical needs of the faculty and students.

TCNJ’s School of Science employs a full-time, dedicated HPC system administrator who reports directly to the Dean of the School of Science. This administrator oversees the design and implementation of the HPC center. He also works closely with TCNJ’s central IT Division and assists faculty and students on best practices when using available HPC resources. This level of support increases the availability of HPC capabilities to student researchers with limited HPC experience.

== Use Cases ==
Generally, the HPC cluster is used to run large simulations and process big data that is impractical to do on a desktop workstation or laptop computer. The HPC cluster provides large amounts of memory (RAM), CPU cores (processors), GPUs (specialized computational devices) and permanent storage (disk).

Example areas of faculty and undergraduate research and teaching using the ELSA cluster include:

* Applied Mathematics
* Astrophysics
* Big Data
* Biochemistry
* Biophysics
* Biostatistics
* Catalytic Chemistry
* Encryption
* Evolution & Phylogeny
* Fluid Dynamics
* Genetics & Bioinformatics
* Machine Learning
* Mathematical Biology
* Natural Language Processing
* Synthetic Biology

== Contact and Tour Information ==
To learn more about the ELSA cluster including how to gain access to this resource as well as scheduling class tours of the cluster, please contact Shawn Sivy in Physics 108A, ssivy@tcnj.edu, or 609-771-3475.

== Acknowledgements ==
{|
|-
| [[File:NJ State Seal.png|alt=State seal of NJ]]     || [[File:NSF Logo.png|alt=National Science Foundation logo]]
|}
The computing hardware comprising the ELSA cluster was provided in part by the State of New Jersey’s Building our Future bond, NJ ELF Bond, and grants from the National Science Foundation ([https://www.nsf.gov/awardsearch/showAward?AWD_ID=1826915&HistoricalAwards=false OAC-1826915] and [https://www.nsf.gov/awardsearch/showAward?AWD_ID=2320244 OAC-2320244]). The College of New Jersey and the School of Science gratefully acknowledge their support and partnership.

Main Page

2026-03-12T18:26:01Z

Admin:

= Welcome to the ELSA HPC Cluster Documentation Site =
[[File:ELSA HPC Cluster.jpg|alt=Student helping with ELSA cluster node|thumb|Computer Science student Victoria Green helping maintain the ELSA HPC Cluster.]]

# [[HPC Cluster About|About ELSA]]
# [[How to Acknowledge Use|How to Acknowledge Use of the ELSA HPC Cluster]]
# [[HPC Cluster Users Google Group|Stay Informed! Join the ELSA HPC Cluster Users Google Group]]
# [[HPC Cluster Getting Started|Getting Started with the ELSA HPC Cluster]]
# [[HPC Cluster Hardware Resources|Hardware Resources]]
# [[HPC Cluster Software Resources|Software Resources]]
# [[HPC Linux Tutorial|A Brief Linux Tutorial]]
# [[HPC Cluster Lmod|Using Lmod]]
# [[HPC Cluster Open OnDemand|Open OnDemand]]
# [[HPC Cluster Job Scheduler|The SLURM Job Scheduler]]

# [[HPC Cluster Course Specific|Course Specific Use of ELSA]]
# [[HPC Cluster Projection Instructions|ELSA Slideshow Tips and Resources]]

ELSA3 Upgrade FAQ

2026-03-05T19:52:26Z

Admin: /* How do I access the test cluster? */

== ELSA3 Upgrade Issues & Resolutions ==

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

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.

<code>module add matlab/R2021a</code>

and replace it with one of these

<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/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.hpc.tcnj.edu

Via Web: https://ondemand-test3.hpc.tcnj.edu/

When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

ELSA3 Upgrade FAQ

2026-03-05T19:52:01Z

Admin: /* How do I access the test cluster? */

== ELSA3 Upgrade Issues & Resolutions ==

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

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.

<code>module add matlab/R2021a</code>

and replace it with one of these

<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/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.hpc.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

ELSA3 Upgrade FAQ

2026-03-05T16:12:38Z

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

== ELSA3 Upgrade Issues & Resolutions ==

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

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.

<code>module add matlab/R2021a</code>

and replace it with one of these

<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/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

MediaWiki:Sidebar

2026-03-05T14:33:18Z

Admin:

MediaWiki:Sidebar

2026-03-05T14:32:47Z

Admin:

MediaWiki:Sidebar

2026-03-05T14:32:32Z

Admin:

ELSA3 Upgrade FAQ

2026-03-05T14:05:39Z

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

== ELSA3 Upgrade Issues & Resolutions ==

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

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.

<code>module add matlab/R2021a</code>

and replace it with one of these

<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/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

ELSA3 Upgrade FAQ

2026-03-05T14:05:10Z

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

== ELSA3 Upgrade Issues & Resolutions ==

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

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.

<code>module add matlab/R2021a</code>

and replace it with one of these

<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>

<code>module avail matlab</code>

== ELSA3 Upgrade/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

ELSA3 Upgrade FAQ

2026-03-05T14:04:46Z

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

== ELSA3 Upgrade Issues & Resolutions ==

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

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.

<code>module add matlab/R2021a</code>

and replace it with one of these

<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>

<code>module avail matlab</code>

== ELSA3 Upgrade/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

ELSA3 Upgrade FAQ

2026-03-05T14:04:10Z

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

== ELSA3 Upgrade Issues & Resolutions ==

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

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 this (<code>module add</code> and <code>module load</code> are synonymous).

<code>module add matlab/R2021a</code>

and replace it with one of these

<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>

<code>module avail matlab</code>

== ELSA3 Upgrade/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

ELSA3 Upgrade FAQ

2026-03-05T14:04:00Z

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

== ELSA3 Upgrade Issues & Resolutions ==

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

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 this (<code>module add</code> and <code>module load</code> are synonymous).

<code>module add matlab/R2021a</code>

and replace it with one of these

<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>

<code>module avail matlab</code>

== ELSA3 Upgrade/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

ELSA3 Upgrade FAQ

2026-03-05T14:02:54Z

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

== ELSA3 Upgrade Issues & Resolutions ==

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

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.

Look for a line in your submit script like this (<code>module add</code> and <code>module load</code> are synonymous).

<code>module add matlab/R2021a</code>

and replace it with one of these

<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>

<code>module avail matlab</code>

== ELSA3 Upgrade/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

ELSA3 Upgrade FAQ

2026-03-05T14:02:22Z

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

== ELSA3 Upgrade Issues & Resolutions ==

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

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 "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.

Look for a line in your submit script like this (<code>module add</code> and <code>module load</code> are synonymous).

<code>module add matlab/R2021a</code>

and replace it with one of these

<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>

<code>module avail matlab</code>

== ELSA3 Upgrade/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

ELSA3 Upgrade FAQ

2026-03-05T14:01:49Z

Admin: /* ELSA3 Upgrade Issues & Resolutions */

== ELSA3 Upgrade Issues & Resolutions ==

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

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 load 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 "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.

<code>Lmod has detected the following error: The following module(s) are unknown: "matlab/R2021a"</code>

Look for a line in your submit script like this (<code>module add</code> and <code>module load</code> are synonymous).

<code>module add matlab/R2021a</code>

and replace it with one of these

<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>

<code>module avail matlab</code>

== ELSA3 Upgrade/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

ELSA3 Upgrade FAQ

2026-03-05T14:00:46Z

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

== ELSA3 Upgrade Issues & Resolutions ==

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

If your job or <code>module add</code> command fails and you have an error like the one below in your '''job.''####''.out''' file, it means that the application or the version of the application you are trying to load 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 "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.

<code>Lmod has detected the following error: The following module(s) are unknown: "matlab/R2021a"</code>

Look for a line in your submit script like this (<code>module add</code> and <code>module load</code> are synonymous).

<code>module add matlab/R2021a</code>

and replace it with one of these

<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>

<code>module avail matlab</code>

== ELSA3 Upgrade/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

ELSA3 Upgrade FAQ

2026-03-05T14:00:07Z

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

== ELSA3 Upgrade Issues & Resolutions ==

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

If your job fails and you have an error like the one below in your '''job.''####''.out''' file, it means that the application or the version of the application you are trying to load 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 "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.

<code>Lmod has detected the following error: The following module(s) are unknown: "matlab/R2021a"</code>

Look for a line in your submit script like this (<code>module add</code> and <code>module load</code> are synonymous).

<code>module add matlab/R2021a</code>

and replace it with one of these

<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>

<code>module avail matlab</code>

== ELSA3 Upgrade/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

ELSA3 Upgrade FAQ

2026-03-05T13:59:15Z

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

== ELSA3 Upgrade Issues & Resolutions ==

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

If your job fails and you have an error like the one below in your '''job.''####''.out''' file, it means that the application or the version of the application you are trying to load 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 "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.

<code>Lmod has detected the following error: The following module(s) are unknown: "matlab/R2021a"</code>

Look for a line in your submit script like this (<code>module add</code> and <code>module load</code> are synonymous).

<code>module add matlab/R2021a</code>

and replace it with one of these

<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>

<code>module avail matlab</code>

== ELSA3 Upgrade/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

ELSA3 Upgrade FAQ

2026-03-05T13:58:59Z

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

== ELSA3 Upgrade Issues & Resolutions ==

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

If your job fails and you have an error like the one below in your '''job.''####''.out''' file, it means that the application or the version of the application you are trying to load 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 "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.

<code>Lmod has detected the following error: The following module(s) are unknown: "matlab/R2021a"</code>

Look for a line in your submit script like this (<code>module add</code> and <code>module load</code> are synonymous).

<code>module add matlab/R2021a</code>

and replace with one of these

<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>

<code>module avail matlab</code>

== ELSA3 Upgrade/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

ELSA3 Upgrade FAQ

2026-03-05T13:58:40Z

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

== ELSA3 Upgrade Issues & Resolutions ==

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

If your job fails and you have an error like the one below in your '''job.''####''.out''' file, it means that the application or the version of the application you are trying to load 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 "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.

<code>Lmod has detected the following error: The following module(s) are unknown: "matlab/R2021a"</code>

Look for a line in your submit script like this (<code>add</code> and <code>load</code> are synonymous).

<code>module add matlab/R2021a</code>

and replace with one of these

<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>

<code>module avail matlab</code>

== ELSA3 Upgrade/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

ELSA3 Upgrade FAQ

2026-03-05T13:58:10Z

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

== ELSA3 Upgrade Issues & Resolutions ==

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

If your job fails and you have an error like the one below in your '''job.''####''.out''' file, it means that the application or the version of the application you are trying to load 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 "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.

<code>Lmod has detected the following error: The following module(s) are unknown: "matlab/R2021a"</code>

Look for a line in your submit script like this (<code>add</code> and <code>load</code> are synonymous).

<code>module add matlab/R2021a</code>

and replace with one of these

<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>

<code>module avail matlab</code>

== ELSA3 Upgrade/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

ELSA3 Upgrade FAQ

2026-03-05T13:57:45Z

Admin: /* ELSA3 Upgrade Issues & Resolutions */

== ELSA3 Upgrade Issues & Resolutions ==

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

If your job fails and you have an error like the one below in your '''job.''####''.out''' file, it means that the application or the version of the application you are trying to load 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 "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.

<code>Lmod has detected the following error: The following module(s) are unknown: "matlab/R2021a"</code>

Look for a line in your submit script like this (<code>add</code> and <code>load</code> are synonymous).

<code>module add matlab/R2021a</code>

and replace with one of these

<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>

<code>module avail matlab</code>

== ELSA3 Upgrade/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

ELSA3 Upgrade FAQ

2026-03-05T13:41:30Z

Admin: /* What have you tested? */

== ELSA3 Upgrade Issues & Resolutions ==

Nothing yet

== ELSA3 Upgrade/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing this [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.

ELSA3 Upgrade FAQ

2026-03-05T13:41:14Z

Admin: /* What have you tested? */

== ELSA3 Upgrade Issues & Resolutions ==

Nothing yet

== ELSA3 Upgrade/Testing Frequently Asked Questions ==

===== So why is there a new cluster? =====
ELSA3 features an upgraded operating system, Rocky Linux 9, and the OpenHPC 3.x cluster tools. The current cluster is using Rocky Linux 8 and the OpenHPC 2.x cluster tools.

===== 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.

===== 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.

===== I don't have time to do the testing. Can I have my students access the ELSA3 test cluster to do the testing instead? =====
Absolutely. Feel free to share this email with them. Have them contact me if they run into any issues.

===== 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.

===== Are my files also available on this new cluster? =====
Yes. Your files in your home directory, /projects, /courses and global /scratch are available and are currently shared between the two clusters.

===== 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.

===== How do I access the test cluster? =====
For the test, you can use these names to access the ELSA3 cluster test:
Via SSH: Use elsa-test3.hpc.tcnj.edu, e.g. ssh ssivy@elsa-test3.tcnj.edu
Via Web: https://ondemand-test3.hpc.tcnj.edu/
When we move to production, these will be changed to the existing elsa.hpc.tcnj.edu and ondemand.hpc.tcnj.edu.

===== How long is the testing period of the first "cluster crunch"? =====
You can login to the new cluster now and continue to use it through Friday, March 27th. At that point, I'll take the new cluster down to make any necessary changes, updates or tweaks. Another test period will be available in April.

===== What have you tested? =====
I surveyed the main users of the cluster to determine which applications needed to be "ported" over to ELSA3. Some applications and some older versions of applications have been left behind. You can see all the applications that have been ported and tested by me by reviewing the [https://docs.google.com/spreadsheets/d/1s2FJ9vfOHikBThf4rE45Pmh45EgqU8nQwi0y9qPlK08/ Google Sheet].

In addition, all applications available under the Interactive Applications in Open OnDemand on the new cluster have been tested, and, at the very least, should start up.

===== Is there an entire new cluster running for this test? =====
Yes, sort of. The test cluster should be full-featured except for those items listed below. The applications below are disabled in this test because it could cause issues with their equivalent applications in the current cluster. The disabled apps are:
WebMO website
ELSA VDI Desktop under Interactive Applications in Open OnDemand
ARM nodes (these will be reimaged with Rocky Linux 9 over the summer)
These will be available in a future test session or with the launch of the ELSA3 cluster in production

There are limited resources available. Here are the nodes available for testing:
* 2 CPU-based nodes (1 AMD-based and 1 Intel-based)
* 1 GPU node with 4 x RTX 2080 GPUs
* 1 GPU node with 4 x RTX A5000 GPUs
* 1 GPU node with 4 x L40S GPUs
* 1 Visualization node with an L40 GPU (new!) for graphics rendering
* 1 login node
* 1 Open OnDemand node

===== When will ELSA3 launch into production? =====
I hope to switch over to the new ELSA3 version the week of May 25th (Memorial Day week). Exact dates/times will be announced in the future. There is currently a planned campus power outage on May 25th so I am thinking of starting up the new cluster after the power returns. The switch over may take up to 2 days depending on how smooth the process goes (I'm hoping for just one day).

===== What will happen to the current cluster? =====
All the nodes will be moved over to the new ELSA3 cluster when it goes into production. The old cluster software will remain for a while, but will no longer be accessible to end-users. If something needs to be moved over later, I will still be able to access the old cluster configurations and software. Remember, all files in your /home, /projects, /courses and /scratch will be available to you on the new cluster.

===== Any gotchas I should worry about when testing? =====
Mostly no. I've disabled the ELSA VDI Desktop because switching back and forth between the new cluster and the old cluster can cause issues. My only other suggestion is to be careful using Open OnDemand on both clusters at the same time. Since your /home directory is available, both will write info to it. Don't accidentally delete or cancel a job running on the wrong Open OnDemand. It won't work anyway and will confuse the other cluster's Open OnDemand. I would suggest using only one at a time and running them in a private/incognito browser window.