Forum Discussion

nbu123's avatar
nbu123
Level 5
7 years ago

Error Code 25 - Cannot connect on socket

Hello All,

 

I am having issue with one of the client that i am adding it first time in Backup.

 

Master :- Win 2008 R2 ,NBU - 7.7.3

Client :- win 2012 R2 , NBU - 7.7.3

Bptestbpcd is failing from Master to client.

Below are the list of troubleshooting that i did already.

From Client:-

bpclntcmd -clear_host_cache, blclntcmd -pn is giving master server name, bplclntcmd -hn <master> is working fine, bpclntcmd -ip <master ip> is working fine.

Telnet to master server on bpcd ,pbx and vnetd is working fine.

Telnet to client server on bpcd ,pbx and vnetd is working fine.

Below is output of bptestbpcd from master to client

 

C:\Program Files\Veritas\NetBackup\bin\admincmd>bptestbpcd -client <client name> -ver
bose -debug
20:51:18.452 [10220.9276] <2> bptestbpcd: VERBOSE = 0
20:51:18.452 [10220.9276] <2> read_client: dname=., offline=0, online_at=0 offli
ne_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
20:51:18.452 [10220.9276] <2> read_client: dname=.., offline=0, online_at=0 offl
ine_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
20:51:18.452 [10220.9276] <2> read_client: dname=COA_0, offline=0, online_at=0 o
ffline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
20:51:18.468 [10220.9276] <2> read_client: dname=CO_0, offline=0, online_at=0 of
fline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
20:51:18.468 [10220.9276] <2> read_client: dname=host_info, offline=0, online_at
=0 offline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
20:51:18.468 [10220.9276] <2> read_client: dname=OAA_0, offline=0, online_at=0 o
ffline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
20:51:18.468 [10220.9276] <2> read_client: dname=OA_0, offline=0, online_at=0 of
fline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
20:51:28.499 [10220.9276] <2> vnet_pbxConnect: ../../libvlibs/vnet_pbx.c.654: pb
xSetAddrEx/pbxConnectEx return error 0:The operation completed successfully.
20:51:28.499 [10220.9276] <8> do_pbx_service: [vnet_connect.c:2231] vnet_pbxConn
ect() failed, status=18, errno=0, use_vnetd=0, cr->vcr_service=bpcd
20:51:28.514 [10220.9276] <8> async_connect: [vnet_connect.c:1823] do_service fa
iled 18 0x12
20:51:47.453 [10220.9276] <8> vnet_pop_byte: [vnet.c:197] errno 10053 0x2745
20:51:47.453 [10220.9276] <2> vnet_pop_byte: vnet.c.199: 0: Function failed: 9 0
x00000009
20:51:47.453 [10220.9276] <2> vnet_pop_string: vnet.c.279: 0: Function failed: 9
0x00000009
20:51:47.453 [10220.9276] <2> vnet_pop_signed: vnet.c.322: 0: Function failed: 9
0x00000009
20:51:47.453 [10220.9276] <2> vnet_version_connect: vnet_vnetd.c.1700: 0: Functi
on failed: 9 0x00000009
20:51:47.453 [10220.9276] <8> do_vnetd_service: [vnet_connect.c:2097] vnet_versi
on_connect failed 9 0x9
20:51:47.453 [10220.9276] <8> async_connect: [vnet_connect.c:1823] do_service fa
iled 9 0x9
20:51:47.469 [10220.9276] <2> logconnections: BPCD CONNECT FROM 10.20.30.247.579
TO 10.99.16.8.13782 fd = 484
20:51:47.469 [10220.9276] <8> vnet_vnetd_push_ipaddr: [vnet_vnetd.c:1857] bptr[i
] 10 0xa
20:51:47.469 [10220.9276] <8> vnet_vnetd_push_ipaddr: [vnet_vnetd.c:1857] bptr[i
] 20 0x14
20:51:47.469 [10220.9276] <8> vnet_vnetd_push_ipaddr: [vnet_vnetd.c:1857] bptr[i
] 30 0x1e
20:51:47.469 [10220.9276] <8> vnet_vnetd_push_ipaddr: [vnet_vnetd.c:1857] bptr[i
] 247 0xf7
20:52:06.407 [10220.9276] <8> vnet_pop_byte: [vnet.c:197] errno 10053 0x2745
20:52:06.407 [10220.9276] <2> vnet_pop_byte: vnet.c.199: 0: Function failed: 9 0
x00000009
20:52:06.407 [10220.9276] <2> vnet_pop_string: vnet.c.279: 0: Function failed: 9
0x00000009
20:52:06.423 [10220.9276] <2> vnet_pop_signed: vnet.c.322: 0: Function failed: 9
0x00000009
20:52:06.423 [10220.9276] <2> vnet_pop_status: vnet.c.400: 0: Function failed: 9
0x00000009
20:52:06.423 [10220.9276] <8> vnet_begin_connect_back: [vnet_vnetd.c:631] status
9 0x9
20:52:06.439 [10220.9276] <2> ConnectToBPCD: bpcd_connect_and_verify(client name) failed: 25
<16>bptestbpcd main: Function ConnectToBPCD(client name) failed: 25
20:52:06.439 [10220.9276] <16> bptestbpcd main: Function ConnectToBPCD(client name)
failed: 25
<16>bptestbpcd main: cannot connect on socket
20:52:06.470 [10220.9276] <16> bptestbpcd main: cannot connect on socket
<2>bptestbpcd: cannot connect on socket
20:52:06.548 [10220.9276] <2> bptestbpcd: cannot connect on socket
<2>bptestbpcd: EXIT status = 25
20:52:06.563 [10220.9276] <2> bptestbpcd: EXIT status = 25
cannot connect on socket

 

  • Have you also tried bplclntcmd -hn <client-name> and bpclntcmd -ip <client-ip> on the master?

    Can you ping the client hostname?

    Can you show us output of 'telnet client-name 1556' on the master? 

    • nbu123's avatar
      nbu123
      Level 5

      Thanks for your response Marianne.

      bpclntcmd -hn <client name> and bpclntcmd -ip is working finr from master server.

      I am able to ping the client from master server.

      when i do the telnet <client name> 1556 from master in cmd prompt it didn't return any error message.

      Its just give me a blinking cursor.

      • Marianne's avatar
        Marianne
        Level 6

        nbu123 wrote:

         

        when i do the telnet <client name> 1556 from master in cmd prompt it didn't return any error message.

        Its just give me a blinking cursor.


        So.... telnet did not connect, right?

        Have you checked if Windows firewall is disabled on the client?

  • Try Restart Netbackup clients services and check if the issue occurs with  

    bptestbpcd -client < client name > in master server 

    • NBU35's avatar
      NBU35
      Level 6

      Please check if client name in policy is being resolved by master and media both.

      Also try restarting NBU client services on client.

      Also add rules on client for ports 13782, 13724, 1556 for inbound and outbound direction from server manager.

      • Marianne's avatar
        Marianne
        Level 6

        There is no need for 13782 and 13724 since NBU 7.0.1.

        We have not seen any feedback from nbu123 in the last 2 weeks.
        I wonder why....