What does the alarm failed to send set_hub to spooler (communication error) specifically mean?
The frequency of these alerts have increased in our environment. Any ideas? The filesystem or drive where Nimbus is installed has plenty of space. Not sure what else to check for.
I'm getting the exact same error. My hub won't start during a nimldr install. I'm running a 32-bit version of Linux.
On the linux side you may want to make sure selinux is turned off, or at least there is a policy for nimsoft to be excluded.
Thanks Neal, that was precisely the issue.
We are also getting this alarm in our environment more frequently after updating to newest version. Apparently for no reason, it is not at network issue, and relates to different robots.
I am seeing these alerts on AS400 boxes - anyone have any idea what I should be checking for? Something similar to Neil's selinux fix?
I was basically told to use a older version of the probe. Which reminds me I should follow up on this issue
Retrieving data ...