Common problems/issues

I don't seem my folder when I do ls /zfs or ls /scratch2

We recently introduced autofs feature that automatically mounts the user directory to /zfs and /scratch2 file system when they access it, and unmounts it after 5 minutes of inactivity. This feature increases the robustness of our file system, and will greatly decrease the visual clutter (especially important if you are accessing Palmetto through a graphical interface). Due to the automatic mounting, you will not initially see your folder in /scratch2 or /zfs, and tab completion won't work. However, the folder is still there. You can cd directly into it, and you will not have any issues:

$ cd /zfs/mygroup
$ cd /scratch2/myusername

After you access it, you will see it when you do ls /zfs or ls /scratch2. If you won't use it for 5 minutes or longer, it will be unmounted, so next time you will have to cd into it in order to see it.

Program crashes on login node with message Killed

When running commands or editing files on the login node, users may notice that their processes end abruptly with the error message Killed. Processes with names such as a.out, matlab, etc., are automatically killed on the login node because they may consume excessive computational resources. Unfortunately, this also means that benign processes, such as editing a file with the word matlab as part of its name could also be killed.

Solution: Request an interactive session on a compute node (qsub -I), and then run the application/command.

Home or scratch directories are sluggish or unresponsive

The /home and /scratch directories can become slow/unresponsive when a user (or several users) read/write large amounts of data to these directories. When this happens, all users are affected as these filesystems are shared by all nodes of the cluster.

To avoid this issue, keep in mind the following:

  1. Never use the /home directory as the working directory for jobs that read/write data. If too many jobs read/write data to the /home directory, it can render the cluster unusable by all users. Copy any input data to one of the /scratch directories and use that /scratch directory as the working directory for jobs. Periodically move important data back to the /home directory.

  2. Try to use /local_scratch whenever possible. Unlike /home or the /scratch directories, which are shared by all nodes, each node has its own /local_scratch directory. It is much faster to read/write data to /local_scratch, and doing so will not affect other users. (see example [here])(

For MacOS user, first time login to Palmetto

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 RSA key sent by the remote host is
Please contact your system administrator.
Add correct host key in /Users/abcd/.ssh/known_hosts to get rid of this message.
Offending RSA key in /Users/abcd/.ssh/known_hosts: **1**
RSA host key for has changed and you have requested strict checking.
Host key verification failed.

Resolution: type one of the following command into the terminal before login to Palmetto (Note the number must match with the given key):

$ sed -i '**1**d' ~/.ssh/known_hosts
$ perl -pi -e 's/\Q$_// if ($. == **1**);' ~/.ssh/known_hosts

Error when creating conda environment after loading anaconda module

If error occurs, please try the following command:

`$ export LD_PRELOAD="" `