Forum Discussion

philalbert's avatar
philalbert
Level 4
8 years ago

Error Status 112

Hi,

I'm having an issue with backing up a server, which was working before.

I'm getting the error status 112.

I found this in the bpcd.log

vnet_pbxAcceptSocket: invalid socket passed to getpeername 10022:An invalid argument was supplied.

The windows firewall is disabled and there's nothing in the McAfee logs.

The client is a Windows 2008 R2, running version 7.6.1 of NetBackup.

Anyone have an idea as of what I should be looking for?

Thanks

4 Replies

  • run bptestbpcd -client client_name -debug -verbose from master./media server and paste logs.

    make sure:

    1) every interface of client must be reachable and name resolved from Master & media server and vice versa.

    2) Add exception for ports 13782/13724/1556 in server , these port should be opened bi-directionally.

    • philalbert's avatar
      philalbert
      Level 4

      There's only 1 interface on the client, the name can be resolved from the master/media and the client.

      Running the bptestnetconn.exe on the client works fine.

      Here's the log from the bptestbpcd:

      E:\Veritas\NetBackup\bin\admincmd>bptestbpcd -client libqcd8 -debug -verbose
      10:47:36.253 [17280.23992] <2> bptestbpcd: VERBOSE = 0
      10:47:36.253 [17280.23992] <2> ConnectionCache::connectAndCache: Acquiring new c
      onnection for host liaqc68.ia.iafg.net, query type 223
      10:47:36.268 [17280.23992] <2> vnet_pbxConnect: pbxConnectEx Succeeded
      10:47:36.268 [17280.23992] <2> logconnections: BPDBM CONNECT FROM 10.1.1.224.531
      26 TO 10.1.1.68.1556 fd = 552
      10:47:36.440 [17280.23992] <2> db_CLIENTsend: reset client protocol version from
      0 to 9
      10:47:36.674 [17280.23992] <2> db_getCLIENT: db_CLIENTreceive: no entity was fou
      nd 227
      10:47:36.674 [17280.23992] <2> vnet_pbxConnect: pbxConnectEx Succeeded
      10:47:36.674 [17280.23992] <2> logconnections: BPCD CONNECT FROM 10.1.1.224.5312
      7 TO 10.1.0.138.1556 fd = 552
      10:47:36.674 [17280.23992] <2> vnet_pbxConnect: pbxConnectEx Succeeded
      10:52:36.697 [17280.23992] <2> vnet_pop_byte: vnet.c.184: 0: Function failed: 11
      0x0000000b
      10:52:36.697 [17280.23992] <2> vnet_pop_string: vnet.c.279: 0: Function failed:
      11 0x0000000b
      10:52:36.697 [17280.23992] <2> vnet_pop_signed: vnet.c.322: 0: Function failed:
      11 0x0000000b
      10:52:36.697 [17280.23992] <2> vnet_version_connect: vnet_vnetd.c.1700: 0: Funct
      ion failed: 11 0x0000000b
      10:52:36.697 [17280.23992] <8> do_pbx_service: [vnet_connect.c:2282] vnet_versio
      n_connect failed 11 0xb
      10:52:36.697 [17280.23992] <8> async_connect: [vnet_connect.c:1823] do_service f
      ailed 11 0xb
      10:52:36.697 [17280.23992] <2> vnet_pop_byte: vnet.c.184: 0: Function failed: 11
      0x0000000b
      10:52:36.697 [17280.23992] <2> vnet_pop_string: vnet.c.279: 0: Function failed:
      11 0x0000000b
      10:52:36.697 [17280.23992] <2> vnet_pop_signed: vnet.c.322: 0: Function failed:
      11 0x0000000b
      10:52:36.697 [17280.23992] <2> vnet_version_connect: vnet_vnetd.c.1700: 0: Funct
      ion failed: 11 0x0000000b
      10:52:36.697 [17280.23992] <8> do_vnetd_service: [vnet_connect.c:2097] vnet_vers
      ion_connect failed 11 0xb
      10:52:36.697 [17280.23992] <8> async_connect: [vnet_connect.c:1823] do_service f
      ailed 11 0xb
      10:52:36.697 [17280.23992] <16> connect_to_service: connect failed STATUS (18) C
      ONNECT_FAILED status: FAILED, (11) TIMEOUT; system: (10036) A blocking operation
      is currently executing. ; FROM 0.0.0.0 TO 10.1.0.138 10.1.0.138 vnetd VIA pbx s
      tatus: FAILED, (11) TIMEOUT; system: (10036) A blocking operation is currently e
      xecuting. ; FROM 0.0.0.0 TO 10.1.0.138 10.1.0.138 vnetd VIA vnetd
      10:52:36.697 [17280.23992] <16> vnet_connect_to_vnetd_ipi: connect_to_service()
      failed: 18
      10:52:36.697 [17280.23992] <16> bpcr_vnetd_connect_forward_socket_begin_ex: vnet
      _connect_to_vnetd_ipi(10.1.0.138) failed: 18
      10:52:36.697 [17280.23992] <2> local_bpcr_connect: bpcr_vnetd_connect_forward_so
      cket_begin failed: 25
      10:52:36.697 [17280.23992] <2> ConnectToBPCD: bpcd_connect_and_verify(libqcd8, l
      ibqcd8) failed: 25
      <16>bptestbpcd main: Function ConnectToBPCD(libqcd8) failed: 25
      10:52:36.697 [17280.23992] <16> bptestbpcd main: Function ConnectToBPCD(libqcd8)
      failed: 25
      <16>bptestbpcd main: cannot connect on socket
      10:52:36.728 [17280.23992] <16> bptestbpcd main: cannot connect on socket
      <2>bptestbpcd: cannot connect on socket
      10:52:36.728 [17280.23992] <2> bptestbpcd: cannot connect on socket
      <2>bptestbpcd: EXIT status = 25
      10:52:36.744 [17280.23992] <2> bptestbpcd: EXIT status = 25
      cannot connect on socket

      • eduncan's avatar
        eduncan
        Level 5

        I suspect you have corruption or something in your TCP stack that is causing the issue.  Have you tried resetting the TCP stack?

        # netsh winsock reset