14.7 Problems with Individual Jobs
To determine why a particular job will not start, there are several commands which can be helpful.
Checkjob will evaluate the ability of a job to start immediately. Tests include resource access, node state, job constraints (ie, startdate, taskspernode,QOS, etc). Additionally, command line flags may be specified to provide further information.
-l <POLICYLEVEL> // evaluate impact of throttling
policies on job feasibility
-n <NODENAME> // evaluate
resource access on specific node
-r <RESERVATION_LIST> // evaluate access to specified
reservations
Display detailed status of node
Display high level summary of job attributes and perform sanity check on job attributes/state.
Display various reasons job is considered 'blocked' or 'non-queued'.
Determine general resource availability subject to specified constraints.
See also:
Diagnosing System Behavior/Problems