25.06.2015 Views

Administering Platform LSF - SAS

Administering Platform LSF - SAS

Administering Platform LSF - SAS

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Setting Daemon Timing Levels<br />

Chapter 42<br />

Troubleshooting and Error Messages<br />

The timing log level for <strong>LSF</strong> daemons is set in lsf.conf with the parameters<br />

LSB_TIME_CMD, LSB_TIME_MBD, LSB_TIME_SBD, LSB_TIME_SCH,<br />

<strong>LSF</strong>_TIME_LIM, <strong>LSF</strong>_TIME_RES.<br />

The location of log files is specified with the parameter <strong>LSF</strong>_LOGDIR in<br />

lsf.conf. Timing is included in the same log files as messages.<br />

To change the timing log level, you need to stop any running daemons, change<br />

lsf.conf, and then restart the daemons.<br />

It is useful to track timing to evaluate the performance of the <strong>LSF</strong> system. You<br />

can use the lsadmin and badmin commands to temporarily change the timing<br />

log level for specific daemons such as LIM, RES, mbatchd, sbatchd, and<br />

mbschd without changing lsf.conf.<br />

How the timing<br />

log level takes<br />

effect<br />

The timing log level you set will only be in effect from the time you set it until you<br />

turn the timing log level off or the daemon stops running, whichever is sooner. If the<br />

daemon is restarted, its timing log level is reset back to the value of the<br />

corresponding parameter for the daemon (LSB_TIME_MBD, LSB_TIME_SBD,<br />

<strong>LSF</strong>_TIME_LIM, <strong>LSF</strong>_TIME_RES). Timing log messages are stored in the same file as<br />

other log messages in the directory specified with the parameter <strong>LSF</strong>_LOGDIR in<br />

lsf.conf.<br />

Limitations<br />

When debug or timing level is set for RES with lsadmin resdebug, or<br />

lsadmin restime, the debug level only affects root RES. The root RES is the<br />

RES that runs under the root user ID.<br />

An application RES always uses lsf.conf to set the debug environment. An<br />

application RES is the RES that has been created by sbatchd to service jobs<br />

and run under the ID of the user who submitted the job.<br />

This means that any RES that has been launched automatically by the <strong>LSF</strong><br />

system will not be affected by temporary debug or timing settings. The<br />

application RES will retain settings specified in lsf.conf.<br />

Timing level commands for daemons<br />

The total execution time of a function in the <strong>LSF</strong> system is recorded to evaluate<br />

response time of jobs submitted locally or remotely.<br />

The following commands set temporary timing options for LIM, RES, mbatchd,<br />

sbatchd, and mbschd.<br />

lsadmin limtime [-l timing_level] [-f logfile_name] [-o] [host_name]<br />

lsadmin restime [-l timing_level] [-f logfile_name] [-o] [host_name]<br />

badmin mbdtime [-l timing_level] [-f logfile_name] [-o]<br />

badmin sbdtime [-l timing_level] [-f logfile_name] [-o] [host_name]<br />

badmin schdtime [-l timing_level] [-f logfile_name] [-o]<br />

For debug level examples, see “Setting Daemon Message Log to Debug Level”<br />

on page 540.<br />

For a detailed description of lsadmin and badmin, see the <strong>Platform</strong> <strong>LSF</strong><br />

Reference.<br />

<strong>Administering</strong> <strong>Platform</strong> <strong>LSF</strong> 543

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!