Hello,
I have a badly behaving user that I need to speak with and want to temporarily
disable their ability to submit jobs. I know I can change their account
settings to stop them. Is there another way to set a block on a specific
username that I can lift later without removing the user/account
account slurmaccount user=baduser set maxjobs=0
Sean
From: slurm-users
mailto:slurm-users-boun...@lists.schedmd.com>>
on behalf of Markuske, William mailto:wmarku...@sdsc.edu>>
Sent: Friday, 26 May 2023 09:16
To: slurm-users@lists.schedmd.com
at 16:34, Ryan Novosielski wrote:
I tend not to let them login. It will get their attention, and prevent them
from just running their work on the login node when they discover they can’t
submit. But appreciate seeing the other options.
Sent from my iPhone
On May 25, 2023, at 19:19, Mar
Hello Joe,
You haven't defined any memory allocation or oversubscription in your
slurm.conf so by default it is giving a full node's worth of memory to each
job. There are multiple options that you can do but what you probably want to
do is make both CPU and memory a selected type with the para
Are you starting the slurmd via 'slurmd -Z' on the dyanmic node?
The next steps would be to check the slurmctld log from the master and slurmd
log for the invalid node. Those should provide more insight into why the node
is seen as invalid. If you can attach those we might be able to see the iss
