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.

Status Codes<br />

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

<strong>NetBackup</strong> Status Code: 144<br />

Message: invalid command usage<br />

Explanation: This status code is due to a <strong>NetBackup</strong> process being started with improper<br />

options or an incompatibility in the product.<br />

Recommended Action: Either correct the command or verify that all <strong>NetBackup</strong> binaries<br />

are at the same version level.<br />

<strong>NetBackup</strong> Status Code: 145<br />

Message: daemon is already running<br />

Explanation: There is another copy of the process executing.<br />

Recommended Action: Terminate the current copy of the process and then restart the<br />

process.<br />

<strong>NetBackup</strong> Status Code: 146<br />

Message: cannot get a bound socket<br />

Explanation: The service could not bind to its socket. A system call failed when the<br />

service attempted to bind to its configured port number. This is usually caused by<br />

another process having acquired the port be<strong>for</strong>e the service started.<br />

Recommended Action:<br />

1. Examine the <strong>NetBackup</strong> Problems and All Log Entries reports.<br />

2. Create bprd and bpdbm debug log directories and retry the operation. Check the<br />

resulting logs to see the system error message resulting from the attempt.<br />

If another process has the port, use other system commands to determine the process.<br />

Based on this research, either change the port number in your services file or map<br />

or terminate the process that has acquired the port.<br />

To identify a bprd or bpdbm problem, look <strong>for</strong> lines similar to the following in the<br />

debug log <strong>for</strong> the respective process:<br />

getsockbound: bind() failed, Address already in use (114)<br />

listen_loop: cannot get bound socket. errno = 114<br />

terminate: termination begun...error code = 146<br />

Similar entries can appear in the reports.<br />

3. If the problem persists longer than ten minutes, it is possible that it will be necessary<br />

to reboot the server.<br />

116 <strong>NetBackup</strong> <strong>Troubleshooting</strong> <strong>Guide</strong> - <strong>Windows</strong> NT/2000<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!