ELSA3 Upgrade FAQ: Difference between revisions
No edit summary |
|||
| Line 25: | Line 25: | ||
Example: <code>module avail</code> ''or'' <code>module avail matlab</code> | Example: <code>module avail</code> ''or'' <code>module avail matlab</code> | ||
== ELSA3 Upgrade | == ELSA3 Upgrade Frequently Asked Questions == | ||
===== So why is there a new cluster? ===== | ===== So why is there a new cluster? ===== | ||
| Line 32: | Line 32: | ||
===== Does this cluster upgrade affect the virtual machines (VMs) on the "MoOSE" virtual infrastructure? ===== | ===== Does this cluster upgrade affect the virtual machines (VMs) on the "MoOSE" virtual infrastructure? ===== | ||
No. The virtualization system is a separate cluster with its own servers and software. However, I will look to upgrade the underlying virtualization software this summer, but that will (mostly) be transparent to the end-users of that system. | No. The virtualization system is a separate cluster with its own servers and software. However, I will look to upgrade the underlying virtualization software this summer, but that will (mostly) be transparent to the end-users of that system. | ||
<!-- | |||
===== Why do I need to test anything? ===== | ===== Why do I need to test anything? ===== | ||
Like moving from one version of Windows to another or one version of MacOS to another, there are some changes that may cause issues with the existing software applications. While I have done some basic testing to make sure there aren't obvious issues with the applications, I am inviting you to also try out some of your applications and double-check my testing. | Like moving from one version of Windows to another or one version of MacOS to another, there are some changes that may cause issues with the existing software applications. While I have done some basic testing to make sure there aren't obvious issues with the applications, I am inviting you to also try out some of your applications and double-check my testing. | ||
| Line 44: | Line 44: | ||
===== Both my students and I are too busy to do any testing. What will happen if we don't do any testing? ===== | ===== Both my students and I are too busy to do any testing. What will happen if we don't do any testing? ===== | ||
That's not a problem. I just wanted to provide you with an opportunity to test drive the new cluster before it goes into production after the spring semester. If you don't any have time to test now, we can work together later on to resolve any issues you encounter. | That's not a problem. I just wanted to provide you with an opportunity to test drive the new cluster before it goes into production after the spring semester. If you don't any have time to test now, we can work together later on to resolve any issues you encounter. | ||
--> | |||
===== Are my files also available on this new cluster? ===== | ===== Are my files also available on this new cluster? ===== | ||
| Line 51: | Line 52: | ||
Nope. Just use your regular TCNJ username and password like you do on the current ELSA cluster. | Nope. Just use your regular TCNJ username and password like you do on the current ELSA cluster. | ||
<!-- | |||
===== How do I access the test cluster? ===== | ===== How do I access the test cluster? ===== | ||
For the test, you can use these names to access the ELSA3 cluster test: | For the test, you can use these names to access the ELSA3 cluster test: | ||
| Line 84: | Line 86: | ||
* 1 login node | * 1 login node | ||
* 1 Open OnDemand node | * 1 Open OnDemand node | ||
--> | |||
===== When will ELSA3 launch into production? ===== | ===== When will ELSA3 launch into production? ===== | ||
ELSA will be upgraded on May 21 & 22nd (Commencement days). Because of the campus power outage on Sunday, May 24th and Memorial Day on Monday, May 25th, ELSA3 will be down until Tuesday, May 26th. I hope the have the system up and operational in the afternoon. | ELSA will be upgraded on May 21 & 22nd (Commencement days). Because of the campus power outage on Sunday, May 24th and Memorial Day on Monday, May 25th, ELSA3 will be down until Tuesday, May 26th. I hope the have the system up and operational in the afternoon. | ||
Revision as of 12:52, 18 May 2026
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 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 module add command fails and you have an error like Lmod has detected the following error: The following module(s) are unknown: 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: module add and module load are synonymous.
module add matlab/R2021a
and replace it with one of these
module add matlab/R2025a or module add matlab
To see what modules are available, use the module avail command.
Example: module avail or module avail matlab
ELSA3 Upgrade 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.
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.
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.