Documentation

Verification

Once you have grb_rs running, you can check to make sure that you will be able to submit jobs to it.

Log In with a Cluster Manager

As we have explained earlier, the Cluster Manager initially creates three default users with predefined passwords:

• standard user: gurobi / pass
• administrator: admin / admin
• system administrator: sysadmin / cluster

These default accounts are provided to simplify installation; you should change the passwords or delete the accounts before actually using the cluster.

You can check that you can log in using the sysadmin account with the grbcluster command-line tool:

> grbcluster login --manager=http://mymanager:61080 --username=sysadmin
info  : Using client license file '/home/jones/gurobi.lic'
Password for sysadmin:
info  : User gurobi connected to http://mymanager:61080, session will expire on...

Log In without a Cluster Manager

With a self-managed cluster, there are no user accounts, and the access level is determined by the password used. Here are the default passwords (which can be changed in the configuration file):

• standard user: pass
• administrator: admin
• system administrator: cluster

In this case, you need to log in to one of the nodes and provide the system administrator password:

> grbcluster login --server=http://server1:61000
info  : Using client license file '/home/jones/gurobi.lic'
Enter password (return to use default):
info  : Connected to https://server1:61000

Note that the password you provide is stored in clear in the license file (for future use by other commands). With this in mind, make sure that access to the license file is restricted.

Accessing the Cluster

Once you have verified that you can log in, you should also check the list of nodes with the command:

> grbcluster nodes
ID       ADDRESS       STATUS TYPE    LICENSE PROCESSING #Q #R JL IDLE %MEM  %CPU
b7d037db server1:61000 ALIVE  COMPUTE VALID   ACCEPTING  0  0  10 <1s  10.89 4.99

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.

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 node licenses
ID       ADDRESS       STATUS  TYPE KEY EXP ORG USER APP VER CS    DL  ERROR
b7d037db server1:61000 INVALID NODE                          false 0   No Gurobi license found...

You may also want to verify that it is possible to submit a job to your cluster. 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 with a command like the following:

> gurobi_cl misc07.mps

For more information on how to install the client and run gurobi_cl, please refer to the section about using Remote Services.