Socket write failed

[Ramkumar_S]

Getting Socket write failed for some clients. But Telnet is successful from master to client and vice versa also bpclntcmd commands are successful.

D:\Program Files\Veritas\NetBackup\bin\admincmd>bptestbpcd -client client1 -debug
17:41:59.832 [17332.19096] <2> bptestbpcd: VERBOSE = 0
17:41:59.832 [17332.19096] <2> read_client: dname=., offline=0, online_at=0 offl
ine_at=0
17:41:59.832 [17332.19096] <2> read_client: dname=.., offline=0, online_at=0 off
line_at=0
17:41:59.832 [17332.19096] <2> read_client: dname=CO_0, offline=0, online_at=0 o
ffline_at=0
17:41:59.832 [17332.19096] <2> read_client: dname=host_info, offline=0, online_a
t=0 offline_at=0
17:41:59.832 [17332.19096] <2> read_client: dname=OA_2147483647, offline=0, onli
ne_at=2147483647 offline_at=0
17:41:59.832 [17332.19096] <2> db_freeEXDB_INFO: ?
17:41:59.848 [17332.19096] <2> copy_preferred_network_list: ../../libvlibs/nbcon
f.c.1801: pseudo PN for : server1
17:41:59.848 [17332.19096] <8> async_connect: [vnet_connect.c:1700] getsockopt S
O_ERROR returned 10049 0x2741
17:41:59.848 [17332.19096] <8> async_connect: [vnet_connect.c:1700] getsockopt S
O_ERROR returned 10049 0x2741
17:41:59.848 [17332.19096] <8> async_connect: [vnet_connect.c:1700] getsockopt S
O_ERROR returned 10049 0x2741
17:41:59.848 [17332.19096] <8> async_connect: [vnet_connect.c:1700] getsockopt S
O_ERROR returned 10049 0x2741
17:41:59.848 [17332.19096] <8> async_connect: [vnet_connect.c:1700] getsockopt S
O_ERROR returned 10049 0x2741
17:41:59.864 [17332.19096] <8> async_connect: [vnet_connect.c:1700] getsockopt S
O_ERROR returned 10049 0x2741
17:41:59.879 [17332.19096] <8> async_connect: [vnet_connect.c:1700] getsockopt S
O_ERROR returned 10049 0x2741
17:41:59.895 [17332.19096] <8> async_connect: [vnet_connect.c:1700] getsockopt S
O_ERROR returned 10049 0x2741
17:41:59.910 [17332.19096] <8> async_connect: [vnet_connect.c:1700] getsockopt S
O_ERROR returned 10049 0x2741
17:41:59.926 [17332.19096] <8> async_connect: [vnet_connect.c:1700] getsockopt S
O_ERROR returned 10049 0x2741
17:41:59.926 [17332.19096] <16> connect_to_service: connect failed STATUS (18) CONNECT_FAILED
        status: FAILED, (41) ADDR_IN_USE; system: (10049) The requested address
is not valid in its context. ; FROM 10.242.251.115 TO client110.242.19.42 bpcd VIA nbrntd
17:41:59.926 [17332.19096] <8> vnet_connect_to_bpcd: [vnet_connect.c:297] connect_to_service() failed 18 0x12
17:41:59.926 [17332.19096] <2> local_bpcr_connect: Can't connect to client Client1
17:41:59.926 [17332.19096] <2> ConnectToBPCD: bpcd_connect_and_verify(Client1, Client1) failed: 25
<16>bptestbpcd main: Function ConnectToBPCD(client1) failed: 25
17:41:59.926 [17332.19096] <16> bptestbpcd main: Function ConnectToBPCD(Client1) failed: 25
<16>bptestbpcd main: cannot connect on socket
17:41:59.957 [17332.19096] <16> bptestbpcd main: cannot connect on socket
<2>bptestbpcd: cannot connect on socket
17:41:59.957 [17332.19096] <2> bptestbpcd: cannot connect on socket
<2>bptestbpcd: EXIT status = 25
17:41:59.973 [17332.19096] <2> bptestbpcd: EXIT status = 25
cannot connect on socket

D:\Program Files\Veritas\NetBackup\bin\admincmd>

[Marianne · Accepted solution]

Which port number did you use when trying telnet?

Have you checked if any firewalls are in place?
Is OS firewall disabled on a client?

Please create bpcd log folder on the client, then repeat bptestbpcd as follows:

bptestbpcd -client <client-name> -debug -verbose

Post output of command as well as client's bpcd log.
Please copy bpcd log to bpcd.txt and upload as File attachment.

PS:

I see reference to nbrntd in bptestbpcd output.

Have you enabled ' Resilient Network' in your environment?

This feature needs port 13724 (vnetd) to be open in both directions.

[mph999]

Does netstat -a show a log of connections in state LAST_ACK ?

It is a windows OS error that you have :

10049

Cannot assign requested address.

The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local computer. This can also result from connect,sendto, WSAConnect, WSAJoinLeaf, or WSASendTo when the remote address or port is not valid for a remote computer (for example, address or port 0).

You'll probabaly find a reboot of the client will resolve, though if it comes back again is another matter.

[Michael_G_Ander]

17:41:59.926 [17332.19096] <16> connect_to_service: connect failed STATUS (18) CONNECT_FAILED
        status: FAILED, (41) ADDR_IN_USE; system: (10049) The requested address
is not valid in its context. ; FROM 10.242.251.115 TO client110.242.19.42 bpcd VIA nbrntd

Could indicate that either the client or more likely the master or media server has run out available ports

What does the bpcd & vnet logs on the client show in regards to

async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 10049 0x2741

entries ?

[Ramkumar_S]

It's working fine After removed ' Resilient Network' 

[Marianne]

Glad I could point you in the right direction over here:

https://www-secure.symantec.com/connect/forums/socket-write-failed-1#comment-10656341

[sksujeet]

To rephrase can you please mark Marianne post as solution instead of your own.