squeue
Status and Reason Codes#
The squeue
command details a variety of information on an active
job’s status with state and reason codes. Job state
codes describe a job’s current state in queue (e.g. pending,
completed). Job reason codes describe the reason why the job is
in its current state.
The following tables outline a variety of job state and reason codes you may encounter when using squeue to check on your jobs.
Job State Codes#
Status |
Code |
Explaination |
---|---|---|
COMPLETED |
|
The job has completed successfully. |
COMPLETING |
|
The job is finishing but some processes are still active. |
FAILED |
|
The job terminated with a non-zero exit code and failed to execute. |
PENDING |
|
The job is waiting for resource allocation. It will eventually run. |
PREEMPTED |
|
The job was terminated because of preemption by another job. |
RUNNING |
|
The job currently is allocated to a node and is running. |
SUSPENDED |
|
A running job has been stopped with its cores released to other jobs. |
STOPPED |
|
A running job has been stopped with its cores retained. |
See also
A full list of these Job State codes can be found in Slurm’s documentation.
Job Reason Codes#
Reason Code |
Explanation |
---|---|
|
One or more higher priority jobs is in queue for running. Your job will eventually run. |
|
This job is waiting for a dependent job to complete and will run afterward. |
|
The job is waiting for resources to become available and will eventually run. |
|
The job’s account is invalid. Cancel the job and rerun with the correct account. |
|
The job’s QoS is invalid. Cancel the job and rerun with the correct account. |
|
All CPUs assigned to your job’s specified QoS are in use; the job will run eventually. |
|
Maximum number of jobs for your job’s QoS have been met; the job will run eventually. |
|
All nodes assigned to your job’s specified QoS are in use; the job will run eventually. |
|
All CPUs assigned to your job’s specified partition are in use; the job will run eventually. |
|
Maximum number of jobs for your job’s partition have been met; the job will run eventually. |
|
All nodes assigned to your job’s specified partition are in use; the job will run eventually. |
|
All CPUs assigned to your job’s specified association are in use; the job will run eventually. |
|
Maximum number of jobs for your job’s association have been met; the job will run eventually. |
|
All nodes assigned to your job’s specified association are in use; the job will run eventually. |
See also
A full list of these Job Reason Codes can be found in Slurm’s documentation.