Robot.cfg file was corrupted and robot turned red and robot watcher services stopped

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

The nimbus service for a particular RHEL 8 machine went down.

In the past we addressed CDM memory utilization issues on this server by deploying cdm 8.06 T1, after which the nimbus service was running correctly. However, following OS patching and a server restart, the nimbus service stopped and the configuration file became corrupted.

We would like to understand the root cause of this issue. For reference, the controller configuration ended up almost completely truncated as follows:

<controller>
reuse_async_session = 1
</controller>

Environment

• DX UIM 23.4 CU 4
• Redhat 8
• Robot 23.4.5

Resolution

Recreate or restore a good known copy of the robot.cfg file

1. ./niminit stop
2. ps -ef|grep nim (make sure all robot processes are down)
3. Restore robot.cfg and/or reconfigure if necessary
4. ./niminit start
5. ./niminit status
6.  Run ps -ef | grep nim (controller, as well as the hdb and spooler probes should be running)
7. When the robot is up and running, set the loglevel to 5 and logsize to 50000 just in case corruption reoccurs for some reason.
8. Once any previously deployed probes have been added back to the robot through MCS Profile deployment/automation or manual deployment/configuration, recheck the controller.log to make sure the robot is functioning properly with no errors.