LSF Version 7.3 - Running Jobs With Platform LSF

Viewing Job Pend and Suspend Reasons (bjobs -p)
When you submit a job, it may be held in the queue before it starts running and it may
be suspended while running. You can find out why jobs are pending or in suspension
with the
bjobs -p option.
You can combine
bjob options to tailor the output. For more details on these or other
bjobs options, see the bjobs command in the Platform LSF Command Reference.
◆ “Pending jobs and reasons” on page 45
◆ “Viewing pending and suspend reasons with host names” on page 45
◆ “Viewing suspend reasons only” on page 46
Pending jobs and reasons
bjobs -p displays information for pending jobs (PEND state) and their reasons. There
can be more than one reason why the job is pending.
For example:
bjobs -p
JOBID USER STAT QUEUE FROM_HOST JOB_NAME SUBMIT_TIME
7678 user1 PEND priority hostD verilog Oct 28 13:08
Queue’s resource requirements not satisfied:3 hosts;
Unable to reach slave lsbatch server: 1 host;
Not enough job slots: 1 host;
The pending reasons also mention the number of hosts for each condition.
You can view reasons why a job is pending or in suspension for all users by combining
the
-p and -u all options.
Viewing pending and suspend reasons with host names
To get specific host names along with pending reasons, use the -p and -l options with
the
bjobs command.
For example:
bjobs -lp
Job Id <7678>, User <user1>, Project <default>, Status <PEND>, Queue <priority>
, Command <verilog>
Mon Oct 28 13:08:11: Submitted from host <hostD>,CWD <$HOME>, Requested
Resources <type==any && swp>35>;
PENDING REASONS:
Queue’s resource requirements not satisfied: hostb, hostk, hostv;
Unable to reach slave lsbatch server: hostH;
Not enough job slots: hostF;
SCHEDULING PARAMETERS:
r15s r1m r15m ut pg io ls it tmp swp mem
loadSched - 0.7 1.0 - 4.0 - - - - - -
loadStop - 1.5 2.5 - 8.0 - - - - - -