search cancel

UIM - Linux robots are inactive in IM and AC

book

Article ID: 201448

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

After install the robot on two redhat linux boxes, they still appears as offline in Infrastructure Manager (IM) and Admin Console (AC).



Cause

The controller logs at loglevel 5 show the controller is continually restarting

Oct  9 15:04:51:304 [140001266947840] 0 Controller: ----- Robot controller 9.30 [Build 9.30.1264, Mar 10 2020] started -----
Oct  9 15:04:52:318 [140001266947840] 0 Controller: Going down...
Oct  9 15:04:59:304 [139711771412224] 0 Controller: ----- Robot controller 9.30 [Build 9.30.1264, Mar 10 2020] started -----
Oct  9 15:05:00:319 [139711771412224] 0 Controller: Going down...
Oct  9 15:05:07:306 [140317483435776] 0 Controller: ----- Robot controller 9.30 [Build 9.30.1264, Mar 10 2020] started -----
Oct  9 15:05:08:322 [140317483435776] 0 Controller: Going down...
Oct  9 15:05:15:307 [140502078105344] 0 Controller: ----- Robot controller 9.30 [Build 9.30.1264, Mar 10 2020] started -----
Oct  9 15:05:16:321 [140502078105344] 0 Controller: Going down...
Oct  9 15:05:23:308 [139956577425152] 0 Controller: ----- Robot controller 9.30 [Build 9.30.1264, Mar 10 2020] started -----
Oct  9 15:05:24:322 [139956577425152] 0 Controller: Going down...

A further reviewing, showed the service went down after next message:

Oct  9 15:04:52:316 [140001266947840] 4 Controller: nimGetIpList - found |||||192.168.1.20|10.10.10.101|
Oct  9 15:04:52:316 [140001266947840] 1 Controller: check_ipchange - old ip 172.16.24.91 no longer in ip list |||||192.168.1.20|10.10.10.101|
Oct  9 15:04:52:316 [140001266947840] 2 Controller: ServiceStop
...
Oct  9 15:04:52:318 [140001266947840] 0 Controller: Going down...

Environment

Release : 20.1

Component: Robot RPM

Resolution

This may occurs if the robot config file doesn't have an IP address defined for it.

To resolve the problem:

1. Stop the nimbus service (systemctl stop nimbus)

2. Backup, and edit the <nimsoft>/robot/robot.cfg adding/modifying the robotip attribute with the IP address the service will bind to. For instance in the above case, the available ip addresses were: 192.168.1.20 and 10.10.10.101. If the ip selected is 192.168.1.20, the file would look as follow:

<controller>
...
   robotip = 192.168.1.20
...
   <environment>
      LD_LIBRARY_PATH = .:$LD_LIBRARY_PATH
   </environment>
</controller>

3. Start the nimbus service. (systemctl start nimbus)

Additional Information

How to change the IP Address for a Robot
https://knowledge.broadcom.com/external/article?articleId=35041

Recommended procedure for robot rename or change of IP
https://knowledge.broadcom.com/external/article?articleId=137766

CA UIM Hub restarts by itself without user prompting
https://knowledge.broadcom.com/external/article?articleId=38221