User guide

FLEXnet Licensing End User Guide 135
The Debug Log File G
The license server produces both debug log files and report log files. The focus of this appendix
is debug log files. For information on report log files see Appendix F, “The Report Log File.”
A debug log file contains status and error messages useful for debugging the license server.
A license server always generates debug log output. Some of the debug log output describes
events specific to
lmgrd and some of the debug log output describes events specific to each
vendor daemon.
Managing Debug Log Output
As lmgrd and its vendor daemons run for a period of time, the volume of this output increases.
As it gets older, the value of the debug log output decreases; therefore, it may be necessary for
you to separate old debug log output from current output; either archive or delete the old output.
For performance, it is suggested that each debug log file be a on disk that is local to the machine
that is running
lmgrd and its vendor daemons. However, if the debug log file must be on a
remotely-mounted disk and you find that the license server is too slow, start
lmgrd with the -
nfs_log
option to improve performance.
See “Debug Log Messages” for a description of the debug log output format.
Capturing Debug Log Output for a License Server
By default, lmgrd and the vendor daemons it manages write debug log output to standard out.
To put this debug log output in a file, either redirect the output of the license server to a file or
start
lmgrd with the -l debug_log_path option.
Capturing Debug Log Output for a Particular Vendor Daemon
The debug log output from different vendor daemons controlled by the same license server can
be written to their own files (v8.0+ vendor daemon). There are two ways to do this:
• Add the DEBUGLOG line to the options file for each vendor daemon. See “DEBUGLOG”
for more details.
• Invoke
lmswitch on the vendor daemon. See “lmswitch” for more details.
Note that
lmgrd writes its own debug log output to standard out.