|
|
Explanation: vmd cannot bind to its socket. (vmd is the NetBackup Volume Manager daemon on UNIX and Linux and the NetBackup Volume Manager service on Windows.) When vmd attempts to bind to its configured port number, system call fails. The call fails usually because another process having acquired the port before the vmd daemon or service started.
Examine the daemon debug log for a more detailed message on the system error.
If another process has the port, use other system commands to determine the process. Based on the result, either change the port number in your services file or map, or terminate the process that has acquired the port.
UNIX and Linux only: Another possible cause for this error is the use of the kill command to terminate vmd. To stop vmd, the recommended method is to use the option on the menu in vmadm. (Or use the equivalent command line request, vmctrldbm -t). The use of the kill command to stop this process can leave it unable to bind to its assigned port the next time it restarts. When the socket problem occurs, the daemon debug log contains lines similar to the following:
unable to obtain bound socket, Address already in use (125)