Troubleshooting

Techniques

  • Run blstat to check the current license usage information.

  • Run blusers to check the current job and license usage. This information is the set intersection of License Scheduler Jobs and FlexNet information.

  • Run blinfo command to check the current License Scheduler configuration.

  • Run BLD -C to run a check to see if configuration is correct. This action in conjunction with LOG_DEBUG writes detailed configuration settings to the debug log.

  • Turn on debugging by setting LSF_LOG_MASK=LOG_DEBUG and reconfiguring the daemon with bladmin reconfig all.

  • Set the log class for mbatchd debug (LSB_DEBUG_MBD) in lsf.conf: LC_LICSCHED.

  • Timing information can be logged using LSB_TIME_SCH=timelevel (similar to LSB_TIME_MBD) in lsf.conf.

  • Run bhosts -s to check if resources are being reported correctly to LSF.

File locations

  • BLD logs are in the standard $LSF_LOGDIR.

  • BLCOLLECT logs are in /tmp or $LSF_LOGDIR on the hosts the daemon is running.

  • Core files from BLD, BLCOLLECT, mbatchd, lim, and mbsched are located in /tmp on the daemon local hosts.

Check if lmstat is supported by blcollect

  1. Create shell script to output (for example, echo) target lmstat output.

  2. Point LMSTAT_PATH in lsf.licensescheduler to the shell script.

  3. If LIC_COLLECTOR is not set, restart the bld to restart blcollect. If LIC_COLLECTOR is set, kill blcollect and restart blcollect manually.

  4. Observe the blcollect log to view if there are any errors to determine whether blcollect is able to parse lmstat output properly.