(24) socket write failed

[vilhena]

Hello there.

I saw some discussion related to this topic here, but the discussion was closed and there were no official answers to the problem.

So, I have a client in a policy which fails backup with '(24) socket write failed' error.

I've did a lot of googling, but didn't come up with any solution. The only thing I discovered is that when I execute this command:' bpgetconfig -g client_name ' from the master server I get the following info:

Client of master.server.name
Linux, RedHat2.6
6.5.4
NetBackup
6.5
650000
/usr/openv/netbackup/bin
Linux 2.6.18-194.el5

But if I execute the bpgetconfig with the client name that failed with the error 24, I get this output: cannot connect on socket.

Can anyone help me here, please?

Thanks.

Regards,

Ricardo Vilhena

[RiaanBadenhorst]

Have you used the bptestbpcd and bptestnetconn commands to test communications between your client and master?

bpgetconfig will contact the client via its name (resolved IP) and retrieve the configuration. The error you're seeing shows you that it cannot connect to the client. This could be network related, could be that the bpcd port is not listening on the client. Aside from the commands listed above, try to telnet from the master to the client on the BPCD port, try to do the same in the opposite direction, and finally try to telnet localhost bpcd on the client.

[Marianne]

We need to troubleshoot comms problem between NBU server and client:

Create bpcd log on client.

Next, run this command on master:

bptestbpcd -client <client-name> -verbose

Please post output of command as well as bpcd log.

[vilhena]

@Riaan:

Thanks for the quick reply Riaan.

The bptestbpcd gives this output:

<16>bptestbpcd main: Function ConnectToBPCD(smtp) failed: 25
cannot connect on socket

I tried with another client from the same policy and it works just fine.

I don't have this command (running version 6.5.4).

Telnet from master to client on BPCD port: No

Telnet from client to master on BPCD port: Yes

Telnet from client to client on BPCD port: Yes

Do you have any clue?

Thanks

@Marianne:

Thanks as well for the quick Reply.

What do you mean by "Create bpcd log on client." ? Is there a specific command to do this?

Did what you said on the master:

[root@master ~]# bptestbpcd -client client_name -verbose
<16>bptestbpcd main: Function ConnectToBPCD(client_name) failed: 25
cannot connect on socket

Thank you both!

Regards,

Ricardo Vilhena

[RiaanBadenhorst]

Hi,

Ok, so BPCD is running and active on the client. That leaves name resolution or something else that might be blocking connections from the master.

Can you perform nslookups for the client name on the master, is the IP address correct?

Is there a firewall active on the client?

Does the client or master have 2 IP's configured?

[vilhena]

So, the nslookup gave different ip adresses for the same client name. 

The problem was that I wasn't writing the fully qualified address of client,

e.g.: client name is: blah.domain.com

and I was just writting blah. The resolv.conf file (on the master), before searching 'domain.com', it searchs 'yada.domain.com'. Now I know that there is a machine called blah.yada.domain.com, so when I wrote nslookup blah, implicitly I was writting blah.yada.domain.com but what I wanted was blah.domain.com.

Now the all the commands work fine, both bptestbpcd and telnet.

But the '(24) socket write failed' still persists.

Tonight we're gonna reboot the client, and maybe the error goes away.

Thank you for your attention.

Regards,

Ricardo Vilhena

[Marianne]

About bpcd log on client:

Create bpcd log dir =

# mkdir /usr/openv/netbackup/logs/bpcd

Seems you found the problem.... Good luck!

[Andy_Welburn]

was you just more specific in using the FQDN in your bptestbpcd to get the latter to work?

[vilhena]

Exactly ;)