15.04.2013 Views

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

NetBackup 4.5 Troubleshooting Guide for Windows - Symantec

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong><br />

Chapter 5, Media Manager Status Codes and Messages 315<br />

Status Codes<br />

Explanation: An attempt was made by ltid (the Media Manager device daemon on<br />

UNIX and the <strong>NetBackup</strong> Device Manager service on <strong>Windows</strong>) to send an internal<br />

process communications message to a robotic daemon/process using an already existing<br />

internal message queue. An error was encountered in the message communications. The<br />

error probably indicates a lack of system resources <strong>for</strong> message queues.<br />

Recommended Action:<br />

1. Examine command output (if available), debug logs, and system logs <strong>for</strong> messages<br />

related to the error.<br />

a. Enable debug logging by creating the necessary directories/folders. Increase the<br />

level of verbosity by adding the VERBOSE option in the vm.conf file and<br />

restarting the daemons/services, or execute the command’s verbose option, if<br />

available.<br />

b. Retry the operation and examine the logs.<br />

2. On UNIX servers, gather output from the ipcs -a command to see what resources<br />

are currently in use. Investigate whether the robotic daemon/process on the local<br />

device host is tied up in communications with devices or other components.<br />

Device Management Status Code: 6<br />

Message: Error in Receiving Daemon Message<br />

Explanation: An attempt was made by ltid (the Media Manager device daemon on<br />

UNIX and the <strong>NetBackup</strong> Device Manager service on <strong>Windows</strong>) to receive or process an<br />

internal process communications message to a robotic daemon/process using an already<br />

existing internal message queue, but an error was encountered in the message<br />

communications. The error probably indicates a lack of system resources <strong>for</strong> message<br />

queues, or mismatched software components.<br />

Recommended Action:<br />

1. Examine command output (if available), debug logs, and system logs <strong>for</strong> messages<br />

related to the error.<br />

a. Enable debug logging by creating the necessary directories/folders. Increase the<br />

level of verbosity by adding the VERBOSE option in the vm.conf file and<br />

restarting the daemons/services, or execute the command’s verbose option, if<br />

available.<br />

b. Retry the operation and examine the logs.<br />

<strong>NetBackup</strong> <strong>4.5</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> <strong>for</strong> <strong>Windows</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!