Why won't my job start?

Here are some common reasons why your job might not have started:

• If you are asking for more resources (such as cores, memory, or walltime) than are currently available, your job must wait for the requested resources to become available before your job can start. See also Slurm Job Right-Sizing.
• Some job configurations will never run; it is important to check that the resources your job is requesting can be provided in the job queue submitted. Check the  job queues and associated resources when choosing an appropriate queue for your job.
• MSI performs scheduled maintenance on the first Wednesday of each month. It might be maintenance day or you may be requesting a walltime of such a length that your job cannot finish before the next maintenance window; jobs will not start if they cannot complete.
• If your group's recent usage has been larger than your group's fairshare target on a particular machine, your jobs will have lower priority and may take longer to start.

Further information for a specific job can be obtained using the command, replacing jobID number with your own job ID number: 

• squeue -j  jobIDnumber