Re: [slurm-users] how to find out why a job won't run?

I'm also interested in this. Another example: "Reason=(ReqNodeNotAvail)" is all that a user sees in a situation when his/her job's walltime runs into a system maintenance reservation. * on Friday, 2018-11-23 09:55 -0500, Steven Dick wrote: > I'm looking for a tool that will tell me why a spec

[slurm-users] how to easily to obtain jobid for array jobs?

Dear slurm-users, My users complain about not being able to cancel array jobs (on slurm 17.11.3). The problem is that squeue by default outputs the %i (job step id) for array jobs, which cannot be used in scancel. What /can/ be used is %A (job id). How can I tell users to easily find that num

[slurm-users] priority: 'job size'-factor scaling parameter

Dear Slurm users, Is there a 'Job Size'-factor equivalent of the 'Job Age'-factor's PriorityMaxAge parameter in Slurm? What I am looking for is a scaling parameter (or threshold parameter) to normalize the job size factor to a value of 1 for '10-core 1-hour' jobs instead of for 1-core 1-mi

[slurm-users] priority: 'job size'-factor scaling parameter

Dear Slurm users, Is there a 'Job Size'-factor equivalent of the 'Job Age'-factor's PriorityMaxAge parameter in Slurm? What I am looking for is a scaling parameter (or threshold parameter) to normalize the job size factor to a value of 1 for '10-core 1-hour' jobs instead of for 1-core 1-mi