For account security, your password must meet the following criteria: At least ten (10) characters, A lowercase letter, An uppercase letter, A number, A symbol, Does not include your username, Is not any of your last 4 passwords.
Problem
Backups of the same client using some media servers fail with status 21: socket open failed
Error Message
status 21: socket open failed
Cause
Overview:
This host is a NetBackup client and can be successfully backed up by some remote media servers, but not by other remote media servers and not by itself acting as a NetBackup SAN media server.
Troubleshooting:
The
job details
confirms that job went active and that bpbrm encountered a problem connecting to the bpcd process on the client host.
4/19/2010 14:23:55 PM - Error bpbrm(pid=9629926)
bpcd on myclient exited with status 21: socket open failed
4/19/2010 14:26:00 PM - Error bpbrm(pid=9629926)
cannot send mail because BPCD on myclient exited with status 21: socket open failed
4/19/2010 14:26:02 PM - end writing
The
vnetd debug log
on the client host confirms that the media server host can connect to the client host and start the bpcd service.
It also shows that the media server host can connect to the client host to create the forwarding socket. But notice that the local process that should attach to the socket did not and vnetd timed out after 120 seconds and exited with status 9.
The
bpcd debug log
from the client host confirms that the service was started. After validating the connecting host versus the SERVER list, it attempted to attach to the forwarding socket, but was unsuccessful which resulted in the status 21.
Notice however, that the server validation sequence above consumed 124 seconds. During that time, the vnetd process holding the forwarding socket timed out and closed the socket, which was then unavailable to bpcd.
Notice also that the server validation included two delays of 62 seconds attempting to perform gethostbyname system calls for two of the servers. The name resolution process used by the operating system scanned several DNS servers before succeeding. There is also a server hostname that cannot be resolved. All of the remote media servers that can backup this client host are at the top of the SERVER list. All of the failing media servers, including the local host, are at the bottom of the SERVER list.
Solution
This problem can be resolved as follows.
Ensure that the client host can perform successful and timely hostname resolution of all SERVER entries in the bp.conf file.
Remove any SERVER entries for hosts that should not be connecting to this host.
In this case, the three problem some servers had been moved to another domain and no longer needed to contact this host. Removing the entries was the best solution.
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.
