UIM Robot Unable to Spool Message
search cancel

UIM Robot Unable to Spool Message

book

Article ID: 33661

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) Unified Infrastructure Management for Mainframe CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

Getting alarms from my robots "Unable to spool Message"

What does this mean and how do I correct this?

Environment

  • Release: Any
  • Component: ROBOT

Resolution

Example message:
"Unable to spool message NimsoftID: B#########-3xxx3: [Message spooling]"

In general, when the alarm message "Unable to spool message" is seen, there are a few reasons this could occur:

1. We cannot write out to the local file system due to low disk space or the disk is full.

2. There is something blocking the port we are trying to communicate on such as a firewall. Firewalls should be disabled or allow ports 48000-48100.
    (Also set first_probe_port = 48000 in the robot.cfg)

3. The robot is 'temporarily' busy

Therefore, these alarms should be automatically cleared whenever the respective reason is resolved.

If you do not want those alerts, you may close them using a NAS AO profile or exclude them via nas preprocessing rule.

Create a NAS AO profile

In the message description enter a regular expression which will match the alarm description and action as close immediately after it is raised. (On arrival). Use a message filter such as->    /.*Unable to spool.*/

As long as you are receiving alarms, and can telnet to and from that robot, then the messages are most likely transient/benign.

Please also to make sure that the Nimsoft folder is 100% excluded from your Anti-virus software.
 
Please also be sure to check that there is sufficient disk space where the robot is installed.

Additional Information

Please also refer to the following KB Article:

Spooler unable to reset out-queue