Bizzare module behaviour

Discovery Cluster
1

I was having trouble with my tmux sessions, I was getting messages like:

-bash: fork: retry: Resource temporarily unavailable
-bash: fork: retry: Resource temporarily unavailable

being spammed when I would type any commands, so I killed my sessions, disconnected and reconnected to the login node. Now I get the same messages when I try to use bash-completion on module names, e.g. typing “module load gTAB” which should attempt to list modules starting with letter “g”, I get:

module load g-bash: fork: retry: Resource temporarily unavailable
-bash: fork: retry: Resource temporarily unavailable

and then it hangs. If I load a module without using bash-completion, and then try running the command, I just get some random characters printed to the terminal

(base) [sagendor@discovery2 ~]$ module load tmux
(base) [sagendor@discovery2 ~]$ tmux ls
no server running on /scratch2/sagendor/tmux-214701/default
(base) [sagendor@discovery2 ~]$ tmux
(base) [sagendor@discovery2 ~]$ 62;9;c
2

This might have been a transient issue or perhaps a user doing something they shouldn’t have. For now I’m unable to reproduce. If this happens again in the future let us know and in the meantime you can try a different login node. For example since you were on discovery2, you could specify the discovery1 hostname.