NetBackup status code: 146
Message: cannot get a bound socket
Explanation: The service or daemon did not bind to its socket. A system call fails when the daemon (UNIX) or service (Windows) attempts to bind to its configured port number. This error is usually caused when another process acquired the port before the daemon or service started.
Recommended Action: Do the following, as appropriate:
Examine the NetBackup Problems and All Log Entries reports.
Create bprd and bpdbm debug log directories and retry the operation. Check the resulting logs to see the system error message that resulted from the attempt.
If another process has the port, use other system commands to determine the process. Based on this research, either change the port number in your
servicesfile or map or terminate the process that acquired the port.On UNIX, another possible cause for this error is the use of the kill command to terminate bprd or bpdbm. To stop bpdbm, use the
/usr/openv/netbackup/bin/bpdbm -terminatecommand. Use of the kill command to stop these processes can leave them unable to bind to their assigned ports the next time they are started.To identify a bprd or a bpdbm problem, look for lines similar to the following in the debug log for the respective process:
<16> getsockbound: bind() failed, Address already in use (114) <32> listen_loop: cannot get bound socket. errno = 114 <4> terminate: termination begun...error code = 146
Similar entries can appear in the reports.
If the problem persists longer than 10 minutes, it may be necessary to restart the server.
Click here to view technical notes and other information on the Veritas Technical Support website about this status code.