bptestbpcd: EXIT status = 25 cannot connect on socket

[alisdad]

Hi

I'm getting EXIT status = 25 cannot connect on socket error when I use the following command from the master server (Linux) to the client (Linux)

 /opt/openv/netbackup/bin/admincmd/bptestbpcd  -verbose -debug  -client   s56upapp620-bak

DNS resolves both ways on both boxes, I can ping both ways with host name and ip, traceroute works from either box.

The client is listening for  forvnetd and bpcd ok

tcp        0      0 *:vnetd                     *:*                         LISTEN
unix  2      [ ACC ]     STREAM     LISTENING     128287610 /usr/openv/var/vnetd/terminate_vnetd.uds
unix  2      [ ACC ]     STREAM     LISTENING     128287644 /usr/openv/var/vnetd/terminate_bpcd.uds
unix  2      [ ACC ]     STREAM     LISTENING     128287661 /usr/openv/var/vnetd/bpcd.uds
unix  3      [ ]         STREAM     CONNECTED     128287623 /tmp/PBXPIPEvnetd

tcp        0      0 *:bpcd                      *:*                         LISTEN
unix  2      [ ACC ]     STREAM     LISTENING     128287644 /usr/openv/var/vnetd/terminate_bpcd.uds
unix  2      [ ACC ]     STREAM     LISTENING     128287661 /usr/openv/var/vnetd/bpcd.uds
unix  3      [ ]         STREAM     CONNECTED     128287677 /tmp/PBXPIPEbpcd

there is no firewall between these 2 boxes nor do either of them have a local firewall running.

The output from the bptestbpcd command from the master server is as follows:

root@upnma02b# /opt/openv/netbackup/bin/admincmd/bptestbpcd  -verbose -debug  -client   s56upapp620-bak
10:49:29.828 [4106] <2> bptestbpcd: VERBOSE = 0
10:49:29.830 [4106] <2> copy_preferred_network_list: ../../libvlibs/nbconf.c.1796: pseudo PN for : chiapp510
10:49:29.830 [4106] <2> copy_preferred_network_list: ../../libvlibs/nbconf.c.1796: pseudo PN for : wtclu020
10:49:29.830 [4106] <2> copy_preferred_network_list: ../../libvlibs/nbconf.c.1796: pseudo PN for : chiapp510
10:49:29.830 [4106] <2> copy_preferred_network_list: ../../libvlibs/nbconf.c.1796: pseudo PN for : wtclu020
10:49:29.830 [4106] <2> copy_preferred_network_list: ../../libvlibs/nbconf.c.1796: pseudo PN for : chiapp510
10:49:29.830 [4106] <2> copy_preferred_network_list: ../../libvlibs/nbconf.c.1796: pseudo PN for : wtclu020
10:49:29.831 [4106] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 113 0x71
10:49:29.831 [4106] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 113 0x71
10:49:29.832 [4106] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 113 0x71
10:49:29.832 [4106] <16> connect_to_service: connect failed STATUS (18) CONNECT_FAILED
        status: FAILED, (10) SOCKET_FAILED; system: (113) No route to host; FROM 10.28.112.9 TO s56upapp620-bak 10.28.1.236 bpcd VIA pbx
        status: FAILED, (10) SOCKET_FAILED; system: (113) No route to host; FROM 10.28.112.9 TO s56upapp620-bak 10.28.1.236 bpcd VIA vnetd
        status: FAILED, (10) SOCKET_FAILED; system: (113) No route to host; FROM 10.28.112.9 TO s56upapp620-bak 10.28.1.236 bpcd
10:49:29.832 [4106] <8> vnet_connect_to_bpcd: [vnet_connect.c:296] connect_to_service() failed 18 0x12
10:49:29.832 [4106] <2> local_bpcr_connect: Can't connect to client s56upapp620-bak
10:49:29.832 [4106] <2> ConnectToBPCD: bpcd_connect_and_verify(s56upapp620-bak, s56upapp620-bak) failed: 25
<16>bptestbpcd main: Function ConnectToBPCD(s56upapp620-bak) failed: 25
10:49:29.832 [4106] <16> bptestbpcd main: Function ConnectToBPCD(s56upapp620-bak) failed: 25
<16>bptestbpcd main: cannot connect on socket
10:49:29.842 [4106] <16> bptestbpcd main: cannot connect on socket
<2>bptestbpcd: cannot connect on socket
10:49:29.842 [4106] <2> bptestbpcd: cannot connect on socket
<2>bptestbpcd: EXIT status = 25
10:49:29.842 [4106] <2> bptestbpcd: EXIT status = 25
cannot connect on socketAs you can see it reports a
root@upnma02b#

As you can see it reports

status: FAILED, (10) SOCKET_FAILED; system: (113) No route to host; FROM 10.28.112.9 TO s56upapp620-bak 10.28.1.236 bpcd VIA vnet, but as previously mentioned both ping and traceroute work in both directions. However see below telnet to vnetd or bpcd on the client from the master does not work either:

root@upnma02b# telnet s56upapp620-bak bpcd
s56upapp620-bak/bpcd: Servname not supported for ai_socktype

root@upnma02b# telnet s56upapp620-bak 13782
Trying 10.28.1.236...
telnet: connect to address 10.28.1.236: No route to host
telnet: Unable to connect to remote host: No route to host

root@upnma02b# telnet s56upapp620-bak vnetd
s56upapp620-bak/vnetd: Servname not supported for ai_socktype

root@upnma02b# telnet s56upapp620-bak 13724
Trying 10.28.1.236...
telnet: connect to address 10.28.1.236: No route to host
telnet: Unable to connect to remote host: No route to host

Any help or suggestions would be appreciated

Thanks

[RiaanBadenhorst]

run bpclntcmd -clear_host_cache on both master and client and the try bptestbpcd again.

[Elango_G1]

You can refer the following technote and make sure everything is ok.

https://www.veritas.com/support/en_US/article.TECH27430

there is a basic troubleshooting that i can find from the following links:

https://www-secure.symantec.com/connect/forums/25-cannot-connect-socket-0

https://www-secure.symantec.com/connect/forums/25-cannot-connect-socket

[Marianne · Accepted solution]

Why would telnet fail with this error? " telnet: Unable to connect to remote host: No route to host". Can you show us output of traceroute? Sure iptables is disabled on both hosts?

[mph999]

RC=25:  Server A tried to sent IP packet to invalid server B.   No connection made so Server A sets rc=25

Or in plain English ...

The source server may have the wrong target server name in its environment or an invalid/wrong IP address for the target server.

[alisdad]

Thanks everybody for your suggestions, although I was convinced I had checked whether riptables was running or not, with a very red face I must admit it was running and was the cause of the fasilure, sorry to have wasted your time!!

[Marianne]

We all need a second pair of eyes sometimes - that is what we are here for!