Manually Parse a Debug Log

If the debug log environment is not suitable for live monitoring, logs can be manually parsed using the appropriate parsing command for each license manager type:

  • FlexNet Publisher debug logs
  • DSLS™ debug logs
  • Altium™ debug logs

This section describes how to enable FlexNet Publisher debug logs using a static or a daily rotating debug log. We recommend using a daily rotating log.

This process takes several steps.

Static Debug Logs

A static debug log is one that captures both the lmgrd and vendor daemon output. The lmgrd daemon contributes date stamps, while the vendor daemon contributes all license activity. (lmgrd is the FlexNet Publisher daemon, which allows Monitor to gather data.) At license server startup time, pass the -l </path/to/debug/log> option to lmgrd. This will create a debug log that will contain all the information necessary for Monitor to properly analyze the log contents. However, this file is not rotatable, and it will require a restart of the server to rotate the log. This type of log will also grow over time, the rate at which is determined by the amount of activity on the license server. Hence, we recommend you use the daily rotating debug log.

Rotating Debug Logs (Recommended)

A rotating debug log is one that captures only the vendor daemon output, which means there will be no date stamps in the file. Because of this, there is a chance for inaccurate assumptions in the log. For example, if license activity ceases for more than 24 hours, the day will become unknown due to there not being a visible roll-over at midnight.

To address this, the log must be rotated daily, typically a few minutes after midnight. This ensures that the license activity is current for n 24-hour period and will keep the file size small. Monitor will need to be configured to automatically look for a daily log file. For this to work properly, the debug log must be rotated to a file with a name reflecting the current date, in the format of <fileName>.<YYYYMMDD>, using the lmswitch command in conjunction with a task scheduling facility.