Managing error logs

Error logs maintain important information about LSF License Scheduler operations. When you see any abnormal behavior in License Scheduler, you should first check the appropriate error logs to find out the cause of the problem.

Log files grow over time. These files should occasionally be cleared, either by hand or using automatic scripts.

Daemon error logs

Log files are reopened each time a message is logged, so if you rename or remove a daemon log file, the daemons will automatically create a new log file.

The License Scheduler daemons log messages when they detect problems or unusual situations. The daemons can be configured to put these messages into files. The error log file names for the LSF License Scheduler system daemons are:

  • bld.log.host_name

  • blcollect.log.host_name

License Scheduler daemons log error messages in different levels so that you can choose to log all messages, or only log messages that are deemed critical.

Controlling error message logging level

License Scheduler logs error messages in different levels so that you can choose to log all messages, or only log messages that are deemed critical.

Set LS_LOG_MASK in lsf.licensescheduler to control message logging for License Scheduler daemons. LS_LOG_MASK Specifies the logging level of error messages for LSF License Scheduler daemons.

The level specified by LS_LOG_MASK determines which messages are recorded and which are discarded. All messages logged at the specified level or higher are recorded, while lower level messages are discarded.

If LS_LOG_MASK is not defined, the value of LSF_LOG_MASK in lsf.conf is used. If neither LS_LOG_MASK nor LSF_LOG_MASK is defined, the default is LOG_WARNING.

The log levels in order from highest to lowest are:

  • LOG_WARNING

  • LOG_DEBUG

  • LOG_DEBUG1

  • LOG_DEBUG2

  • LOG_DEBUG3

The most important License Scheduler log messages are at the LOG_WARNING level. Messages at the LOG_DEBUG level are useful for debugging.

For debugging purposes, the level LOG_DEBUG contains the fewest number of debugging messages and is used for basic debugging. The level LOG_DEBUG3 records all debugging messages, and can cause log files to grow very large; it is not often used. Most debugging is done at the level LOG_DEBUG2.