Differences

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

--- ssh_login_nopass [2026/04/29 22:12] – pwolinsk
+++ ssh_login_nopass [2026/05/10 21:44] (current) – pwolinsk
@@ Line 1: / Line 1: @@
 ==== SSH Password-less Login ====
-The secure shell (SSH) server on **hpc-portal1.hpc.uark.edu** does not accept passwords as an authentication method. Instead, SSH key files are used for access. A public SSH key file is stored in your account on Pinnacle. A matching private key (pinnacle.key) file has to be supplied as a parameter to the ssh command on the client to log in.
+The secure shell (SSH) server on **hpc-portal2.hpc.uark.edu** does not accept passwords as an authentication method. Instead, SSH key files are used for access. A public SSH key file is stored in your account on Pinnacle. A matching private key (pinnacle.key) file has to be supplied as a parameter to the ssh command on the client to log in.
 <code>
-ssh -i pinnacle.key ffinfinn@hpc-portal1.hpc.uark.edu
+ssh -i pinnacle.key ffinfinn@hpc-portal2.hpc.uark.edu
 </code>
 Both private and public keys are generated and configured automatically on Pinnacle via the web portal. To enable SSH password-less access:
-**1.** Log into the web portal at: https://hpc-portal1.hpc.uark.edu
+**1.** Log into the web portal at: https://hpc-portal2.hpc.uark.edu
 **2.** In the top menu go to **Clusters -> SSH keys**
@@ Line 24: / Line 24: @@
 **Download** button at the top. The file will likely be saved to your **Downloads** directory.
-**5.** Before the file can be used for SSH, the file permissions must be updated
+**5.** Before you can use the file for SSH, the file permissions must be updated
 to read-only for owner, mode ''400'' on MacOS and Linux:
@@ Line 35: / Line 35: @@
 <code>
-ssh -i pinnacle.key ffinfinn@hpc-portal1.hpc.uark.edu
+ssh -i pinnacle.key ffinfinn@hpc-portal2.hpc.uark.edu
-  ************ PLEASE CITE US in your publications *****************************
+  ************ PLEASE CITE AHPCC ********** in your publications ***************
+  ******************************************************************************
   **    This research is supported by the Arkansas High Performance Computing **
   **    Center which is funded through multiple National Science Foundation   **
   **    grants and the Arkansas Economic Development Commission.              **
   ******************************************************************************
+  Login nodes are for file operations and job submission.
-  Login nodes are for file operations and job submission.
+    - Don't run R or Python on login nodes.
-  All login nodes run a different kernel than compute nodes, so:
+  To start an interactive job on a shared cloud compute node:
-    - Don't compile on login nodes. Resulting code won't work on compute nodes.
+     srun -N1 -n1 -c1 -p cloud72 -q cloud -t 72:00:00 --pty /bin/bash
-    - Don't run R or Python on login nodes.
-  For a shared cloud compute node:
-     srun -N1 -n1 -c1 -p cloud72 -q cloud -t 72:00:00 --pty /bin/bash
 Last login: Fri Apr 10 10:14:51 2026 from 167.224.131.232