GENERAL ERROR: The Volume Manager service (vmd) will not stay running on a Windows master or media server.
| Article:TECH19068 | | | Created: 2002-01-18 | | | Updated: 2011-05-10 | | | Article URL http://www.symantec.com/docs/TECH19068 |
Problem
GENERAL ERROR: The Volume Manager service (vmd) will not stay running on a Windows master or media server.
Error
Could not connect to vmd on host
unable to obtain bound socket
no port number available for vmd
Solution
Overview:
The Volume Manager service (vmd) will not stay running on a Windows master or media server.
Troubleshooting:
This behavior has been seen in situations where the Windows services file is missing entries for the NetBackup processes.
The Volume Manager service (vmd) will not stay running on a Windows master or media server.
Troubleshooting:
This behavior has been seen in situations where the Windows services file is missing entries for the NetBackup processes.
Running the command on the problem master or media server
<install dir>\volmgr\bin\vmoprcmd -d
returns:
Could not connect to vmd on host
Log Files:
The Debug\Daemon log on the system will show:
14:09:40 [2756] <16> vm_getservbyname: getservbyname() failed after 3 attempts for vmd/tcp
14:09:40 [2756] <16> getsockbound: cannot find Internet service vmd/tcp
14:09:40 [2756] <16> vmd: unable to obtain bound socket, no port number available for vmd (0)
14:09:40 [2756] <16> vmd: terminating - daemon cannot obtain socket (58)
Log Files:
The Debug\Daemon log on the system will show:
14:09:40 [2756] <16> vm_getservbyname: getservbyname() failed after 3 attempts for vmd/tcp
14:09:40 [2756] <16> getsockbound: cannot find Internet service vmd/tcp
14:09:40 [2756] <16> vmd: unable to obtain bound socket, no port number available for vmd (0)
14:09:40 [2756] <16> vmd: terminating - daemon cannot obtain socket (58)
The following messages may also be seen in the Windows Application Event Viewer:
unable to obtain bound socket
no port number available for vmd
Resolution:
This issue can be resolved by adding the NetBackup port entries into the services file.
1. Open the services file with a text editor (ex. Notepad):
%system_root%\system32\drivers\etc\services
2. Verify that the following entries are listed in the services file:
bpcd 13782/tcp
bprd 13720/tcp
vopied 13783/tcp
vnetd 13724/tcp
bpdbm 13721/tcp
vmd 13701/tcp
acsd 13702/tcp
tl8cd 13705/tcp
odld 13706/tcp
ts8d 13709/tcp
tldcd 13711/tcp
tl4d 13713/tcp
tsdd 13714/tcp
tshd 13715/tcp
tlmd 13716/tcp
tlhcd 13717/tcp
lmfcd 13718/tcp
bpjobd 13723/tcp
rsmd 13719/tcp
nbdbd 13784/tcp
visd 9284/tcp
3. Save and close the file.
4. Restart NetBackup services when there is no job activity.
Note: The ports listed are from a default NetBackup installation. If these ports have been changed from the default, modify accordingly.
4. Restart NetBackup services when there is no job activity.
Note: The ports listed are from a default NetBackup installation. If these ports have been changed from the default, modify accordingly.
|
|
| Value | 58 |
| Description | NetBackup Error 58: daemon cannot obtain socket |
| Value | 70 |
| Description | NetBackup Error 70: Could not connect to vmd on host |
Legacy ID
245708
Article URL http://www.symantec.com/docs/TECH19068
Terms of use for this information are found in Legal Notices
Thank you.