A job might not start for one of the following reasons:

• The queue has reached its maximum run limit
• Your job is waiting for resources
• Your mission share has run out
• The system is going into dedicated time
• Scheduling is turned off
• Your job has been placed on hold
• Your home filesystem or default /nobackup filesystem is down
• Your hard quota limit for disk space has been exceeded

You can often determine the reason a job does not start by running one of the following commands to view job status and information:

• To view job status and events that might specify the reason a job served by pbspl1 or pbspl4 failed to start, run tracejob job_id on the PBS server pbspl1 or pbspl4

  Note: Users have no access to pbs05a which serves jobs submitted to run on Cabeus gh200 nodes.

• To view all available information about the job, including status or any comments added by the administrator or scheduler that may explain why the job didn't start, run qstat -as job_id on an appropriate front-end system for the compute resources requested by your job.
• To find out whether the system is in dedicated time, run schedule all.

See Common Reasons Why Jobs Won't Start for more detailed troubleshooting information.