SLURM/JobStatus

Job Status

SLURM offers a variety of tools to check the status of your jobs before, during, and after execution. When you first submit your job, SLURM should give you a job ID which represents the resources allocated to your job. Individual calls to srun will spawn job steps which can also be queried individually.

squeue

The squeue command shows job status in the queue. Helpful flags:

• -u username to show only your jobs (replace username with your UMIACS username)
• --start to estimate start time for a job that has not yet started and the reason why it is waiting
• -s to show the status of individual job steps for a job (e.g. batch jobs)

Examples:

[username@nexusclip00 ~]$ squeue -u username
             JOBID PARTITION     NAME     USER ST       TIME  NODES NODELIST(REASON)
               162      tron helloWor username  R       0:03      2 tron[00-01]

[username@nexusclip00 ~]$ squeue --start -u username
             JOBID PARTITION     NAME     USER ST          START_TIME  NODES SCHEDNODES           NODELIST(REASON)
               163      tron helloWo2 username PD 2020-05-11T18:36:49      1 tron02               (Priority)

[username@nexusclip00 ~]$ squeue -s -u username
         STEPID     NAME PARTITION     USER      TIME NODELIST
          162.0    sleep      tron username      0:05 tron00
          162.1    sleep      tron username      0:05 tron01

sstat

The sstat command shows metrics from currently running job steps. If you don't specify a job step, the lowest job step is displayed.

sstat --format JobID,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize <$JOBID>.<$JOBSTEP>

[username@nexusclip00 ~]$ sstat --format JobID,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize 171
       JobID   NTasks             Nodelist     MaxRSS  MaxVMSize     AveRSS  AveVMSize 
------------ -------- -------------------- ---------- ---------- ---------- ---------- 
171.0               1               tron00          0    186060K          0    107900K 
[username@nexusclip00 ~]$ sstat --format JobID,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize 171.1
       JobID   NTasks             Nodelist     MaxRSS  MaxVMSize     AveRSS  AveVMSize 
------------ -------- -------------------- ---------- ---------- ---------- ---------- 
171.1               1               tron01          0    186060K          0    107900K 

Note that if you do not have any jobsteps, sstat will return an error.

[username@nexusclip00 ~]$ sstat --format JobID,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize 172
       JobID   NTasks             Nodelist     MaxRSS  MaxVMSize     AveRSS  AveVMSize 
------------ -------- -------------------- ---------- ---------- ---------- ----------
sstat: error: no steps running for job 237

If you do not run any srun commands, you will not create any job steps and metrics will not be available for your job. Your batch scripts should follow this format:

#!/bin/bash
#SBATCH ...
#SBATCH ...
# set environment up
module load ...

# launch job steps
srun <command to run> # that would be step 1
srun <command to run> # that would be step 2

sacct

The sacct command shows metrics from past jobs.

[username@nexusclip00 ~]$ sacct
       JobID    JobName  Partition    Account  AllocCPUS      State ExitCode 
------------ ---------- ---------- ---------- ---------- ---------- -------- 
162          helloWorld       tron      nexus          2  COMPLETED      0:0 
162.batch         batch                 nexus          1  COMPLETED      0:0 
162.0             sleep                 nexus          1  COMPLETED      0:0 
162.1             sleep                 nexus          1  COMPLETED      0:0 
163          helloWorld       tron      nexus          2  COMPLETED      0:0 
163.batch         batch                 nexus          1  COMPLETED      0:0 
163.0             sleep                 nexus          1  COMPLETED      0:0 

To check one specific job, you can run something like the following (if you omit .<$JOBSTEP>, all jobsteps will be shown):

sacct  --format JobID,jobname,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize,Elapsed -j <$JOBID>.<$JOBSTEP>

[username@nexusclip00 ~]$ sacct --format JobID,jobname,NTasks,nodelist,MaxRSS,MaxVMSize,AveRSS,AveVMSize,Elapsed -j 171
       JobID    JobName   NTasks        NodeList     MaxRSS  MaxVMSize     AveRSS  AveVMSize    Elapsed 
------------ ---------- -------- --------------- ---------- ---------- ---------- ---------- ---------- 
171          helloWorld              tron[00-01]                                               00:00:30 
171.batch         batch        1          tron00          0    119784K          0    113120K   00:00:30 
171.0             sleep        1          tron00          0    186060K          0    107900K   00:00:30 
171.1             sleep        1          tron01          0    186060K          0    107900K   00:00:30 

Job Codes

If you list the current running jobs and your job is in PD (Pending), SLURM will provide you some information on what the reason for this in the NODELIST parameter. You can use scontrol show job <jobid> to get all the parameters for your job to help identify why your job is not running.

[username@nexusclip00 ~]$ squeue -u username
JOBID  PARTITION     NAME     USER     ST       TIME  NODES NODELIST(REASON)
1           tron     bash     username PD       0:00      1 (AssocGrpGRES)
2           tron     bash     username PD       0:00      1 (Resources)
3           tron     bash     username PD       0:00      1 (Priority)
4           tron     bash     username PD       0:00      1 (QOSMaxGRESPerUser)
5           tron     bash     username PD       0:00      1 (ReqNodeNotAvail, Reserved for maintenance)

Some common ones are as follows:

• Resources - The cluster does not currently have the resources to fit your job in your selected partition.
• Priority - The cluster has reserved resources for higher priority jobs in your selected partition.
• QOSMax*PerUser or QOSMax*PerUserLimit - The quality of service (QoS) your job is running in has some limit per user (CPU, mem, GRES, etc.). Use show_qos and show_partition_qos to identify the limit(s) and then use scontrol show job <jobid> for each of your jobs running in that QoS to see the resources they are currently consuming.
• AssocGrpBilling - The SLURM account you are using has a limit on the overall billing amount available in total for the account. Use sacctmgr show assoc account=<accountname> where user= to identify the limit, replacing <accountname> with the account you are submitting your job with. You can see all jobs running under the account and their billing values by running squeue -A <accountname> -O "JobId:.18 ,Partition:.9 ,Name:.8 ,UserName:.8 ,StateCompact:.2 ,TimeUsed:.10 ,NumNodes:.6 ,ReasonList:45 ,tres-alloc:80".
• ReqNodeNotAvail - None of the nodes that could run your job (based on requested partition/resources) currently have the resources to fit your job. Alternatively, if you also see Reserved for maintenance, there is a reservation in place (often for a maintenance window). You can see the current reservations by running scontrol show reservation. Often the culprit is that you have requested a TimeLimit that will conflict with the reservation. You can either lower your TimeLimit such that the job will complete before the reservation begins, or leave your job to wait until the reservation completes.

SLURM's full list of reasons/explanations can be found here.