Example alarms from the controller log:
Mar 18 00:10:34:349  Controller: Failed to send set_hub to spooler (communication error)
Mar 18 00:25:34:380  Controller: Failed to send set_hub to spooler (communication error)
Mar 18 00:40:34:215  Controller: Failed to send set_hub to spooler (communication error)
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.
Checking customers' alarms we have seen that this alarm is generated at a fixed frequency.? In a short time the alarm usually clears.
Since the robot is queuing messages no information is being lost.? The alarm can be ignored, but it does indicate some form of connectivity issue.
Try redeploying the robot_update package for the given version of robot deployed.
Stop the Robot by stopping the Nimsoft Robot Watcher Service or using the niminit command (UNIX/LINUX).
Then clear (delete all niscache files) in the niscache directory on the robot machine in the Nimsoft installation directory.
Start the robot.
If you are currently running robot 7.10, try robot 7.00 or 7.05 instead - there's some evidence that this problem occurs much more frequently in robot v7.10, and 7.10 has been pulled from production (for other reasons) so it's a good idea not to run v7.10 anyway.