Totally agree with the solution. We were running slurm 15.xx for some time
and the manual job edit was miserable. In 16 the command noted was
created. Have used it often and been pleased.
Doug
On Wed, Jan 8, 2020 at 7:40 AM Douglas Jacobsen wrote:
> Try running `sacctmgr show runawayjobs`;
Hello Angelines,
for me (Slurm 19.05.2) the following command seems to work:
sacctmgr update user set maxsubmitjobs=0
Job submission is then rejected with the following message:
$ sbatch job.slurm
sbatch: error: AssocMaxSubmitJobLimit
sbatch: error: Batch job submission failed: Job violates a
The way we use is to create a qos called “batchdisable” that is disallowed
on all partitions. Then set the user association qos list to only
batchdisable. This deauthorizes the user from submitting to all partitions.
On Wed, Jan 8, 2020 at 05:52 Angelines wrote:
> Hello,
>
> I need to forbid a
Try running `sacctmgr show runawayjobs`; it should give you the list of
running/pending jobs (from slurmdbd's perspective) that are unknown to
slurmctld. It will give you the option to "fix" it, however note that
fixing will set the end time of the job to the start time, so the
accounting will be
Good afternoon everyone,
when trying to collect some accounting information from my Slurm cluster,
I found a couple of jobs that haven't been recorded as "finished", and
therefore show up in every single day accounting since their start date.
All those jobs have been started within a 2-hour perio
Hello,
I need to forbid a user to submmits jobs, I have used:
sacctmgr modify user where name=us cluster=cl account=ac set maxsubmitjobs=0
and with maxjobs=0 but it doesn't work
Could someone help me please?
Thanks in advance
--
Angelines Alb
