User guide

Appendix G - The Debug Log File
Debug Log Messages
136 FLEXnet Licensing End User Guide
Redirecting Debug Log Output for a Running Vendor Daemon
It is possible to redirect the debug log output for a particular vendor daemon to a different file.
There are two ways to do this:
• Change the DEBUGLOG line to the options file for the vendor daemon and reread its
options file by invoking
lmreread. See “DEBUGLOG” for more details.
• Invoke
lmswitch on the vendor daemon. See “lmswitch” for more details.
Limiting Debug Log Output for a Vendor Daemon
By default, debug log output contains all events. To limit the events that are logged for a
particular vendor daemon, add a NOLOG line to the options file of that vendor daemon. See
“NOLOG” for more details. One of the reasons you may want to limit the events that are logged
is to reduce the size of the debug log output.
Debug Log Messages
FLEXnet Licensing processes generate debug log files in the following format:
hh:mm:ss (daemon) message
where:
The debug log files can be used to:
• Diagnose configuration problems
• Diagnose daemon software errors
Note A debug log file cannot be used for usage reporting with SAMreport.
hh
:mm:ss Time that the message was logged.
daemon Either
lmgrd or the vendor daemon name. In the case where a single
copy of the daemon cannot handle all of the requested licenses, an
optional “_” followed by a number indicates that this message comes
from a forked daemon.
message The text of the message.