Important note: most Gurobi licenses do not use the token server.
You should only follow these instructions if you are setting up
a floating license. If you are not sure whether
you need to start a token server, you can examine the
contents of your
If it contains the line
TYPE=TOKEN, and does
not contain the line
MACHINELIMIT=0, then you need
a token server.
To start the Linux token server daemon, run the program grb_ts (with no arguments) on your token server machine. You only need to do this once — the token server will keep running until you stop it (or until the machine is shut down). Be sure that the license key file has been installed before running this program. Note that the token server runs as a user process, so you do not need root privileges to start it.
If you would like the token server to restart automatically when the machine is rebooted, there are a number of options for doing so (including /etc/rc.local and upstart). You should talk to your system administrator.
To stop a running token server, you can issue the grb_ts -s command. You can also use the ps command to find the relevant process ID, and the kill command to terminate that process.
Output from the token server goes to the system log (/var/log/syslog). You should see a message similar to the following when you start the server:
Mar 5 12:37:21 mymachine grb: Gurobi Token Server started: Sat Mar 5 12:37:21 2022
By default, the token server only produces logging output when it starts. To obtain more detailed logging information, start the token server with the -v switch. This will produce a log message each time a token is checked in or out.
The token server forks off a separate process that runs in the background. Use the -n switch to run it in the foreground instead.
If you run into trouble accessing the token server, check to see if the server is running firewall software that is blocking access to some ports. The Gurobi token server uses port number 41954 by default, so you'll need to open access to that port on the server. Please consult the documentation for your firewall software to determine how to do this. If there's a conflict on the default port, you can choose a different one by adding a PORT line to both the server and the client license key files:
You can choose any available port number.
Clients of the token server also need simple license files. Your next step is to set up a client license.
Once your token server is running and you've set up a client license, you can move on to testing the license.
Once you've set up a client license, you can test the state of the
token server at any time, as well as get a list of the clients that
are currently using tokens, by typing