NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows
Chapter 5, Media Manager Status Codes and Messages 361
Status Codes
2. On UNIX servers, gather the output of the ipcs -a command to see what resources
are currently in use.
Robot Error Status Code: 5
Message: Error in getting process Id
Explanation: A robotic daemon/process was unable to obtain its own process identifier
due to a system call failure.
Recommended Action: Investigate operating system functionality regarding a process
obtaining its own process identifier.
Robot Error Status Code: 6
Message: No devices are configured on the robot
Explanation: A robotic daemon/process was started, but no drives are configured for the
robot.
Recommended Action: Some robotic daemons/processes will not run if there are no
drives configured for them to manage. Add or reconfigure one or more drives to be in the
associated robot. Then, stop and restart ltid (the Media Manager device daemon on
UNIX or NetBackup Device Manager service on Windows).
Robot Error Status Code: 7
Message: No robots are configured
Explanation: A robotic daemon/process was started, but no robots of the associated robot
type are configured.
Recommended Action: Robotic daemons/processes will not run if there are no robots
configured for the associated robot type. Add or reconfigure one or more robots, then stop
and restart ltid (the Media Manager device daemon on UNIX or NetBackup Device
Manager service on Windows).
Robot Error Status Code: 8
Message: No memory available
Explanation: A robotic daemon/process was unable to allocate memory. This error occurs
when there is insufficient system memory available. This could be caused by the system
being overloaded with too many processes and there is not enough physical and virtual
memory.
Recommended Action: Free up memory by terminating unneeded processes. Add more
swap space or physical memory.
NetBackup 4.5 Troubleshooting Guide for Windows