NetBackup status code: 23 - How to troubleshoot backups that fail with status 23 "socket read failed".
Problem
How to troubleshoot backups that fail with status 23 "socket read failed".
Overview:
This document discusses how to troubleshoot backups that fail with status 23 "socket read failed". Backups may fail with a status 23 when the client is unable to resolve the connecting media server's ip address.
Error Message
socket read failed
Client Log Files:
Examine the client's bpcd log for issues related to host name or address resolution:
12:44:38.619 [4804.5184] <2> logconnections: BPCD ACCEPT FROM 10.1.2.3.47204 TO 10.1.2.37.13724
12:44:38.619 [4804.5184] <2> bpcd main: setup_sockopts complete
12:44:43.134 [4804.5184] <8> bpcd peer_hostname: gethostbyaddr failed : The requested name is valid, but no data of the requested type was found.
(0)
12:44:43.134 [4804.5184] <16> bpcd peer_hostname: gethostbyaddr failed to return peer host, herrno = 0
12:44:43.134 [4804.5184] <16> bpcd main: Couldn't get peer hostname
Cause
Troubleshooting:
In the above case, the initial connection from the media server (IP=10.1.2.3) is made to the client (IP=10.1.2.37). The first indication of a failure can be seen in the line containing the following message:
<8> bpcd peer_hostname: gethostbyaddr failed
This indicates that the client in this case is unable to resolve the media server's IP address, 10.1.2.3. In this instance, it is likely that an nslookup
of 10.1.2.3 will fail, as will running 'bpclntcmd -ip 10.1.2.3
'.
Run the name resolution test using the 'bpclntcmd -hn [host name]
' command to ensure the hostname is resolving correctly.
Solution
Resolution:
Correct the hostname resolution issue either at the DNS server or by including the appropriate hosts file entry for the master server on the client.
Note: The hosts files are located the following directory...
- Windows: %SystemRoot%\system32\drivers\etc
- UNIX/Linux: /etc