UIM robot .rpm installer fails to install robot - robot.cfg file does not contain valid configuration

Document ID : KB000039087
Last Modified Date : 14/02/2018
Show Technical Document Details

Symptoms:

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:

<controller>
   access_0 = 0
   access_1 = 1
   access_2 = 2
   access_3 = 3
   access_4 = 4
</controller>

 

Cause:

This is caused by extra spaces in between the keys, values, and equal signs in the nms-robot-vars.cfg file used for installation.

Example:

domain = MyDomain
hub = Myhub
hubrobotname = MyHubRobot
hubport = 48002

Resolution:

The file should be formatted thusly instead:

domain=MyDomain
hub=Myhub
hubrobotname=MyHubRobot
hubport=48002

After correcting the nms-robot-vars.cfg, remove and re-install the .rpm package and the problem should be resolved.