Troubleshooting guide

Chapter 4, Status Codes and Messages 137
Status Codes
Recommended Action: Either correct the command or verify that all NetBackup binaries
are at the same version level.
Status Code: 145
Message: daemon is already running
Explanation: There is another copy of the process executing.
Recommended Action: Terminate the current copy of the process and then restart the
process.
Status Code: 146
Message: cannot get a bound socket
Explanation: The daemon (service on Windows NT/2000) could not bind to its socket. A
system call failed when the daemon (UNIX) or service (Windows NT/2000) attempted to
bind to its configured port number. This is usually caused by another process having
acquired the port before the daemon or service started.
Recommended Action:
1. Examine the NetBackup Problems and All Log Entries reports.
2. Create bprd and bpdbm activity log directories and retry the operation. Check the
resulting logs to see the system error message resulting 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 services file or map
or terminate the process that has acquired the port.
On UNIX, another possible cause for this error is terminating bprd or bpdbm with the
kill command. If you have to stop bprd, the recommended method is to use the
Terminate Request Daemon option on the Special menu in bpadm (or the equivalent
option in xbpadm). To stop bpdbm, use the /usr/openv/netbackup/bin/bpdbm
-terminate command. Using 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 bpdbm problem, look for lines similar to the following in the
activity 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.