Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

RedHat 6.5 Client Error status 24 socket write failed

Created: 02 May 2013 | 6 comments

I'm getting the following error  bptestbpcd: EXIT status = 24

when running C:\Program Files\Veritas\NetBackup\bin>bptestbpcd -client <client> -debug -verbose

After adding Verbose = 5 in the bp.conf file and running the command I get this errror in the logs:

10:50:35.410 [2074] <2> ReadKeyfile: keyfile /usr/openv/netbackup/keyfile does not exist
 
10:50:35.410 [2074] <2> bpcd main: ReadKeyfile failed
10:50:35.410 [2074] <2> bpcd main: offset to GMT 18000
10:50:35.410 [2074] <2> logconnections: BPCD ACCEPT FROM 172.30.10.95.61896 TO 192.168.100.105.13724
10:50:35.410 [2074] <2> bpcd main: setup_sockopts complete
10:50:35.414 [2074] <2> vauth_acceptor: vauth_comm.c.337: no methods for address: no authentication required
10:50:35.414 [2074] <2> bpcd main: no authentication required
10:50:35.415 [2074] <8> bpcd peer_hostname: gethostbyaddr failed : HOST_NOT_FOUND (1)
10:50:35.415 [2074] <16> bpcd peer_hostname: gethostbyaddr failed to return peer host, herrno = 1
10:50:35.415 [2074] <16> bpcd main: Couldn't get peer hostname
 
Any ideas?
 
Thanks
 
Mike
Operating Systems:

Comments 6 CommentsJump to latest comment

mph999's picture

At first glance it seems to be a name resolution issue.

Make sure the server you are running the command from can forward/ reverse lookup the target, and vice-versa.

gethostbyaddr failing is the operating system complaining, nbu is just reporting the issue.

Martin

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805
 
revaroo's picture
10:50:35.410 [2074] <2> logconnections: BPCD ACCEPT FROM 172.30.10.95.61896 TO 192.168.100.105.13724
10:50:35.410 [2074] <2> bpcd main: setup_sockopts complete
10:50:35.414 [2074] <2> vauth_acceptor: vauth_comm.c.337: no methods for address: no authentication required
10:50:35.414 [2074] <2> bpcd main: no authentication required
10:50:35.415 [2074] <8> bpcd peer_hostname: gethostbyaddr failed : HOST_NOT_FOUND (1)
10:50:35.415 [2074] <16> bpcd peer_hostname: gethostbyaddr failed to return peer host, herrno = 1
10:50:35.415 [2074] <16> bpcd main: Couldn't get peer hostname
 
ok so gethostbyaddr failed: HOST_NOT_FOUND means the server could not resolve the IP to a hostname.
Check your hosts files on the server you run the bptestbpcd from AND the server or client you are running it too, to ensure that they can resolve the IP to hostnames of each other.
 
 
 
MaykelF0209's picture

Ok, thanks for the responses.  I've modified the host files on both the Linux box and the media server. I restarted the network in the Linux box and I still get the same error. 

There was no entry in the hosts files in the Linux box so I added it with the media server name and IP

MaykelF0209's picture

Got it working, I had to add it to the host file with the FQDN and not just the host name

revaroo's picture

Excellent. These issues are 99% of the time hostname issues and looking at the hosts file to ensure you have the IP's referenced to a hostname (and that hostname entered as a SERVER entry in the bp.conf) solves the issue.

mph999's picture

Hmm, the good new is revaroo agreed with me, the bad news is it still doesn't work ...

From the meachine you ran the command from lets run

nbdna -phase 2

This should go out and investigate what servers it knws about from the NBU config, when it finishes it geives the location of the output (shoudl be in the 'output' directory.  In there there are several files, probably the best one to look at has 'progress' in its name.  This should show any failures around name resolution.

Also, in /etc/resolve.conf, for the hosts entry, does it show 'files' first.

Martin

Regards,  Martin
 
Setting Logs in NetBackup:
http://www.symantec.com/docs/TECH75805