Once you have grb_rs running, you can check to make sure that you will be able to submit jobs to it by issuing the following command from any machine that can reach the server on your network:
ADDRESS STATUS TYPE LICENSE PROCESSING #Q #R JL IDLE %MEM %CPU STARTED RUNTIMES VERSION server1 ALIVE COMPUTE VALID ACCEPTING 0 0 2 1h55m 2.35 3.69 2019-04-07 11:41:25 [8.0.1 8.1.1] 8.1.1-v8.1.1rc0
You are ready to submit jobs if both of the following are true:
- the STATUS column indicates that one or more servers are ALIVE
- the LICENSE column indicates that the license is VALID (or N/A for distributed workers).
If grbcluster is unable to connect or if it does not show any live nodes, then check your network and the log of the grb_rs nodes (the console output or <installdir>/bin/service.log if started as a service).
If a node has an INVALID license, the ERROR field will provide more information about the error. For example:
> grbcluster licenses --server=server1 --password=admin ADDRESS STATUS TYPE KEY EXP ORG USER APP VER CS DL ERROR server1 INVALID NODE false 0 No Gurobi license found...
Optionally, you can also check that submitting a job is successful. To this end, you may want to identify a machine from which the users will typically submit jobs and install the gurobi client package. Then, you can submit a job running the following command:
> gurobi_cl --server=server1 --password=pass misc07.mps
For more information on how to install the client and run gurobi_cl please refer to the section about using Remote Services.
Note that if you started the node with a specific port, you can specify it in the server URL:
> grbcluster nodes --server=server1:61000 --password=pass ... > gurobi_cl --server=server1:61000 --password=pass misc07.mps