Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
habrok:additional_information:known_issues [2024/07/16 13:55] – [New server hostkey (21/03/2024 & 15/07/2024)] fokkehabrok:additional_information:known_issues [2025/07/01 11:59] (current) – [Last updated] pedro
Line 7: Line 7:
  
 ===== Getting e-mails on job status changes ===== ===== Getting e-mails on job status changes =====
-The Slurm scheduler has not been connected to a mail server and getting mail notifications is not possible.+The Slurm scheduler has not been connected to a mail server and getting mail notifications is not possible. Because this caused emails from the RUG domain to be trapped by spam filters, we regrettably have no plans to enable email notifications in the future
  
 ===== Wrong software stack used for interactive jobs ===== ===== Wrong software stack used for interactive jobs =====
Line 13: Line 13:
  
 ===== Software using Intel MPI fails when using ''mpirun'' ===== ===== Software using Intel MPI fails when using ''mpirun'' =====
- 
 This seems to happen for jobs requesting a larger number of nodes, and only with ''mpirun''. Please see this [[habrok:examples:mpi#intel_mpi | Intel MPI]] section for more information about using ''srun'' instead. This seems to happen for jobs requesting a larger number of nodes, and only with ''mpirun''. Please see this [[habrok:examples:mpi#intel_mpi | Intel MPI]] section for more information about using ''srun'' instead.
  
-===== New server hostkey (21/03/2024 & 15/07/2024) ===== +===== OpenMPI issues with the ''foss2024a'' and ''foss2025a'' toolchains ===== 
- +Due to a bug in the schedulerOpenMPI 5 currently only works with ''mpirun'' (i.e. not with ''srun'') on the parallel nodes. This will be fixed during the next Hábrók maintenance by upgrading the schedulerThis issue only affects (user installedsoftware built with these toolchains, and the few Hábrók modules using these toolchains (primarily ''R/4.4.2-gfbf-2024a'' and dependencies).
-In order to bring Hábrók back online after the incident on 16/03/2024 we had to reinstall and reconfigure the login and interactive nodes. Because of thisthese nodes now have new server host keysThis means that connecting to Hábrók results in (correctwarnings that these keys no longer match those that had been registered on your system when you connected for the first time.  +
- +
-On 15/07/2024 we had to reinstall the interactive nodes to fix a configuration issue. +
- +
-Normally, checking the server hostkey ensures that you are not inadvertently connecting to a system posing as Hábrók (known as a man-in-the-middle attack) by warning you that you are actually connecting to another machine. You can safely ignore this check at this time because Hábrók's host keys //have indeed changed// due to the reinstallation. +
- +
-==== MobaXterm ==== +
- +
-When reconnecting you will see a pop up window. Simply press "**Accept the new server hostkey and carry on connecting**" +
- +
-{{:habrok:additional_information:remote_server_id_changed.png?400|}} +
- +
-==== ssh connections on a terminal ==== +
- +
-You will see a message with:  +
- +
-<code> +
-@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ +
-@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @ +
-@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ +
-IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! +
-Someone could be eavesdropping on you right now (man-in-the-middle attack)+
-It is also possible that a host key has just been changed. +
-The fingerprint for the ED25519 key sent by the remote host is +
-SHA256:LnOMDB7/5L0OKJojsXb2CovSUGvd2k0U0oJ8L3xR2HI. +
-Please contact your system administrator. +
-Add correct host key in /home/user/.ssh/known_hosts to get rid of this message. +
-Offending ED25519 key in /home/user/.ssh/known_hosts:13 +
-  remove with: +
-  ssh-keygen -f "/home/user/.ssh/known_hosts" -R "login1.hb.hpc.rug.nl" +
-Host key for login1.hb.hpc.rug.nl has changed and you have requested strict checking. +
-Host key verification failed. +
-</code> +
- +
-Follow the instructions on the message and run: +
- +
-<code> +
-ssh-keygen -f "/home/user/.ssh/known_hosts" -R "login1.hb.hpc.rug.nl" +
-</code>+
  
-**Note that your command may be different, as the path to the ''known_hosts'' file is likely different in your situation**. The suggestion in the warning message should give you the correct path.+==== Page last updated on ==== 
 +2025-07-01