After installing a new robot using the .RPM native installer package for Linux machines, the robot will appear to start but will never check in to the hub.
The robot.cfg file will contain only the following:
access_0 = 0
access_1 = 1
access_2 = 2
access_3 = 3
access_4 = 4
This is caused by extra spaces in between the keys, values, and equal signs in the nms-robot-vars.cfg file used for installation.
domain = MyDomain
hub = Myhub
hubrobotname = MyHubRobot
hubport = 48002
The file should be formatted thusly instead:
After correcting the nms-robot-vars.cfg, remove and re-install the .rpm package and the problem should be resolved.