Hello All,
Yggdrasil
@Lena.Parc : no computing tasks on the login node, no compiling, building, or anything like that. 
I wanted to restrict you all to just basic commands like vim, emacs, nano, ls, rsync, and Slurm on the login node, but my kind colleagues keep stopping me from being too harsh, so consider yourself lucky! 
(joke… or not I keep the mystery)
@Max.Briel You have vscode-server processes running on the login node and you source Conda in your .bashrc. The total number of processes you’re spawning exceeds the TaskLimit.
I’ve increased the limit again for now, but after some quick tests, the more SSH-remote VS Code sessions I open, the more tasks get created. Even when I terminate a VS Code session (exit command in the VS Code terminal), the processes on the login node stay alive in sleep mode. What a nightmare… Increasing the limit won’t solve the root cause, VS Code just keeps taking more and more. Such a child…
I think VS Code keeps those sleeping processes around to reconnect to the same session, maybe like tmux, but I’m not an expert. 
To fully clean my VS Code processes and avoid fork issues, I run:
- List VS Code processes:
pgrep -f vscode
- Kill all VS Code processes:
pkill -f vscode
Baobab
The recent reboot of the Baobab login node triggered an update to the process limits configuration.
I manually removed the limitations on Baobab for now. I plan to fix this properly next Monday, but for now, I’m off for the weekend! 