For a floating (or site) license, the token server service or daemon (grb_ts) logs events to the system log. In the default mode, the logged events include startup, shutdown, and failed token check-outs.
Verbose mode
In default mode, the token server log does not log check-in and check-out events. Logging of check-in/check-out events can be enabled by switching to verbose mode. Verbose mode produces a log message each time a token is checked in or out.
Token server logging can be made verbose by either:
- Adding the following line to the license file:
VERBOSE=1
- Specifying -v on the command line for the token server process or daemon:
grb_ts -v
On Windows
On Windows, you can view these log entries in the Event Viewer under "Windows Logs > Application." The event source for the token server entries is "grb".
On Linux
On Linux, these events are logged to /var/log/syslog. The permissions to access this file are set by the system administrator.
To view the usage history of a Linux token server from the command line, you can use:
cat /var/log/syslog | grep grb
Note: /var/log/syslog is the default logging location for Debian-based systems like Ubuntu. The logging location for Red Hat-based systems like RHEL or CentOS is /var/log/messages.
Linux examples
Example of a "limit exceeded" error entry in the Linux system log:
May 29 18:13:26 ubuntu grb[4310]: Request denied: use limit (1) exceeded
Examples of check-in/check-out events:
May 29 18:13:35 ubuntu grb[4310]: Issued license 0, 1/1/1 active,
host ubuntu (127.0.0.1), PID 4514, user dj
May 29 18:13:38 ubuntu grb[4310]: Checked in license 0, 0/0/0 active,
host ubuntu (127.0.0.1), PID 4514, user dj
Note: The number triple in the log displays the current number of uses/users/machines
.
Customizing syslog on Linux
For rsyslogd (the default system logger for Ubuntu):
- Create a new file called /etc/rsyslog.d/30-grb.conf which consists of:
# Change logging of Gurobi messages
:programname, isequal, "grb" /var/log/gurobi.log
# Stop logging anything that matches the previous rule
& ~ - Restart the rsyslog daemon via the command service rsyslog restart and restart the Gurobi token server. You can specify a log file of your choice by changing /var/log/gurobi.log in your configuration file.
Further information
- How do I set up and use a floating token server license?
- How do I check the status of the token server from a client?
- How do I check the availability of floating license tokens?
- How do I release a shared license?
- How do I instruct Gurobi to produce a log file?
Comments
0 comments
Article is closed for comments.