| |||
| Home > Troubleshooting server configuration > How can I manage the size of the server debug log file? | |||
If you are administering a floating license server that is heavily used, you might find that the floating license server debug log becomes unmanageably large after a relatively short time. Very large log files in excess of 1GB in size can cause the license utilities to fail. You can control the size of the server debug log file in the following ways:
You can stop the server debug log from recording certain message
types by using the NOLOG directive in an options
file. You can turn off logging of license checkouts (OUT), checkins
(IN), and denied (DENIED) and queued (QUEUED) messages. If you normally
suppress server debug log messages, it might be necessary for you
to re-enable them to troubleshoot problems.
To turn off logging of checkins use:
NOLOG IN
To turn off logging of checkouts and queued requests two separate NOLOG lines are required:
NOLOG DENIED NOLOG QUEUED
When you restart the floating license server, you start a new floating license server debug log file. Restarting the server can be useful if you suspect a memory leak or similar problem that only becomes noticeable after an extended period. The server shutdown and restart process normally takes a few seconds to complete. See Setting Up a Floating License Server.
You can create a new server debug log without restarting the floating license server by using the lmswitch command. Regularly creating new debug logs, for example on a weekly basis, can help you to maintain organized records of floating license server activity. You can use this command on the Windows or Unix/Linux command line. Change to the directory where your floating license server utilities are installed, then type the command:
lmutil lmswitch -clicense_file_namearmlmdnew_logfile_name
where:
license_file_namespecifies the fully qualified path name of the license file being used
new_logfile_namespecifies the fully qualified path name of the new server debug log file.
Your original log file is closed with a message that the server
debug log is being switched to .
The top of new_logfile_name tells
you the name of the previous server debug log file.new_logfile_name