Some nimbus agent (robot) processes were not starting on Linux

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Problem: Nimbus agent (process) is not starting on Linux machine(remote hub)

Cause

• The root cause of the nimbus robot not starting completely was that the first_probe_port was set to 48005 instead of 48000 so either something was using that port or something else was blocking/interfering with the robot/robot process startup.

Resolution

1. Changed the first_probe_port in the robot.cfg to 48000 (default) from its setting of 48005.
2. Then the spooler and all other nimbus robot processes were listed when the nimbus.service was restarted.
3. Afterward, the hub and robot GUIs could be opened without erroring as well.

Additional Information

Before the resolution, we had to reboot the Linux machine to force the nimbus processes to stop.