Administering Platform LSF - SAS

Setting Daemon Message Log to Debug Level
Setting Daemon Message Log to Debug Level
How the message
log level takes
effect
The message log level for LSF daemons is set in lsf.conf with the parameter
LSF_LOG_MASK. To include debugging messages, set LSF_LOG_MASK to one
of:
◆ LOG_DEBUG
◆ LOG_DEBUG1
◆ LOG_DEBUG2
◆ LOG_DEBUG3
By default, LSF_LOG_MASK=LOG_WARNING and these debugging messages
are not displayed.
The debugging log classes for LSF daemons is set in lsf.conf with the
parameters LSB_DEBUG_CMD, LSB_DEBUG_MBD, LSB_DEBUG_SBD,
LSB_DEBUG_SCH, LSF_DEBUG_LIM, LSF_DEBUG_RES.
The location of log files is specified with the parameter LSF_LOGDIR in
lsf.conf.
You can use the lsadmin and badmin commands to temporarily change the
class, log file, or message log level for specific daemons such as LIM, RES,
mbatchd, sbatchd, and mbschd without changing lsf.conf.
The message log level you set will only be in effect from the time you set it until you
turn it off or the daemon stops running, whichever is sooner. If the daemon is
restarted, its message log level is reset back to the value of LSF_LOG_MASK and the
log file is stored in the directory specified by LSF_LOGDIR.
Limitations
When debug or timing level is set for RES with lsadmin resdebug, or
lsadmin restime, the debug level only affects root RES. The root RES is the
RES that runs under the root user ID.
Application RESs always use lsf.conf to set the debug environment.
Application RESs are the RESs that have been created by sbatchd to service
jobs and run under the ID of the user who submitted the job.
This means that any RES that has been launched automatically by the LSF
system will not be affected by temporary debug or timing settings. The
application RES will retain settings specified in lsf.conf.
540
Administering Platform LSF