Accessing Job Logs
Gurobi Optimizer log output from a previous or currently running job can be retrieved by using the log command. For example:
> grbcluster --server=server1 --password=pass log 78400806 MIR: 3 Flow cover: 43 Explored 178942 nodes (1207578 simplex iterations) in 93.24 seconds Thread count was 2 (of 2 available processors) Solution count 10: 1.20001e+09 1.35001e+09 1.50001e+09 ... 1.65835e+09 Optimal solution found (tolerance 1.00e-04) Best objective 1.200012600000e+09, best bound 1.200000244174e+09, gap 0.0010%
The argument to this command is the JOBID for the job of interest (which can be retrieved using the jobs command), you can use the full ID or the short ID. If you don't specify a JOBID, the command will display the log for the last job submitted.
The log command accepts the following arguments:
Usage: grbcluster log <JOBID> [flags] Important flags: -b, --begin Display log from the beginning -f, --continuous Display log continuously until job completion -n, --lines int Display only the last n lines (default 10)
For example, to get the entire log, from the beginning of the job, use the -b (or --begin) flag.
> grbcluster --server=server1 --password=pass log 78400806 -b
You can get a continuous feed of the log for a running optimization job with the -f (or --continuous) flag.
