Platform LSF Administrator's Primer Version 6.2
Chapter 2
Working with LSF
Platform LSF Administrator’s Primer
23
Other useful
commands
◆
The lshosts command displays configuration information for LSF hosts and
their static resource information.
◆
The lsinfo command displays cluster configuration information about resources,
host types, and host models.
Checking LSF Batch configuration (badmin)
badmin ckconfig -v
The badmin command controls and monitors the operation of the LSF Batch system.
Use the
badmin ckconfig command to check the LSF Batch configuration files. The
-v flag displays detailed information about the configuration:
% badmin ckconfig -v
Checking configuration files ...
Dec 20 12:22:55 2005 20246 6 6.2 minit: Trying to call LIM to get cluster name
...
Dec 20 12:22:55 2005 20246 6 6.2 Batch is enabled
Dec 20 12:22:55 2005 4433 6 6.2 Checking Done
---------------------------------------------------------
No errors found.
The messages shown above are typical output from badmin ckconfig -v. Other
messages may indicate problems with the LSF Batch configuration.
See Chapter 6, “Troubleshooting LSF Problems” or the Platform LSF Reference for
help with some common configuration errors.
Finding out LSF Batch system status (bhosts and bqueues)
To use LSF Batch commands, the cluster must be up and running. See “Starting your
cluster” on page 18 for information about starting LSF daemons.
bhosts
The bhosts command tells you if LSF Batch is running properly. bhosts displays the
status of LSF Batch server hosts in the cluster, and other details about the batch hosts:
◆
Maximum number of job slots allowed by a single user
◆
Total number of jobs in the system, jobs running, jobs suspended by users, and jobs
suspended by the system
◆
Total number of reserved job slots
The status should be
ok for all hosts in your cluster. For example:
% bhosts
HOST_NAME STATUS JL/U MAX NJOBS RUN SSUSP USUSP RSV
hosta ok - - 0 0 0 0 0
hostb ok - - 0 0 0 0 0
hostc ok - - 0 0 0 0 0
hostd ok - - 0 0 0 0 0
If you see the message
batch system daemon not responding ... still trying