Failed to send set_hub to spooler (communication error)

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Example alarms from the controller log:

Mar 18 00:10:34:349 [1452] Controller: Failed to send set_hub to spooler (communication error)
Mar 18 00:25:34:380 [1452] Controller: Failed to send set_hub to spooler (communication error)
Mar 18 00:40:34:215 [1452] Controller: Failed to send set_hub to spooler (communication error)

Environment

• UIM, any version

Cause

• This alarm is caused by the robot not being able to connect to the hub
• The robot then spools up alarms and QoS messages
• When connectivity is restored, the alarms are received

Resolution

1. Try redeploying the robot_update package for the given version of robot that is already deployed
2. Stop the Robot by stopping the Nimsoft Robot Watcher Service or using the niminit command (UNIX/LINUX)
3. Then clear (delete all niscache files) in the niscache directory on the robot machine in the Nimsoft installation directory
4. Start the robot

Additional Information

This alarm is generated at a fixed frequency. In a short time, the alarm usually clears.

Since the robot is still queuing messages no information is being lost. The alarm can be ignored, but it does usually indicate some form of connectivity issue.

Also, the Windows event viewer may show a crash of the controller in the Application event log:

Faulting application name: controller.exe, version: 0.0.0.0, time stamp: 0x5ac8a095 
Faulting module name: NIM_SHARED.dll, version: 0.0.0.0, time stamp: 0x5ac89db1 
Exception code: 0xc0000005 
Fault offset: 0x00000000000211e7 
Faulting process id: 0x604 
Faulting application start time: 0x01d4dbf53494246e 
Faulting application path: C:\Program Files\Nimsoft\robot\controller.exe 
Faulting module path: C:\Program Files\Nimsoft\robot\NIM_SHARED.dll 
Report Id: ad274b63-48fd-11e9-80ea-0050569c4af0 
Faulting package full name: 
Faulting package-relative application ID: