Forum Discussion

cynthiapinto's avatar
cynthiapinto
Level 4
10 years ago

Cannot connect on socket

Hi,

 

I have a RHEL server with 7.6.1 NB version is installed . This is my master & media server .

 

I have a client with centos 6.6 32 bit with NB 6.0 version installed

 

When i try to connect the client from master server I get the error as cannot connect to client .

[root@exdbvbkp01 admincmd]# ./bptestbpcd -client hislnxciti001 -verbose -debug
18:22:35.292 [2428] <2> bptestbpcd: VERBOSE = 5
18:22:35.292 [2428] <2> ConnectToBPCD: db_getCLIENT(hislnxciti001) failed: 227
18:22:35.295 [2428] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 111 0x6f
18:22:35.296 [2428] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 111 0x6f
18:22:35.297 [2428] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 111 0x6f
18:22:36.298 [2428] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 111 0x6f
18:22:36.299 [2428] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 111 0x6f
18:22:36.300 [2428] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 111 0x6f
18:22:38.302 [2428] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 111 0x6f
18:22:38.302 [2428] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 111 0x6f
18:22:38.303 [2428] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 111 0x6f
18:22:42.306 [2428] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 111 0x6f
18:22:42.307 [2428] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 111 0x6f
18:22:42.307 [2428] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 111 0x6f
18:22:50.310 [2428] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 111 0x6f
18:22:50.311 [2428] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 111 0x6f
18:22:50.312 [2428] <8> async_connect: [vnet_connect.c:1700] getsockopt SO_ERROR returned 111 0x6f
18:22:50.313 [2428] <16> connect_to_service: connect failed STATUS (18) CONNECT_FAILED
        status: FAILED, (42) CONNECT_REFUSED; system: (111) Connection refused; FROM 0.0.0.0 TO hislnxciti001 172.27.167.67 bpcd VIA pbx
        status: FAILED, (42) CONNECT_REFUSED; system: (111) Connection refused; FROM 0.0.0.0 TO hislnxciti001 172.27.167.67 bpcd VIA vnetd
        status: FAILED, (42) CONNECT_REFUSED; system: (111) Connection refused; FROM 0.0.0.0 TO hislnxciti001 172.27.167.67 bpcd
18:22:50.313 [2428] <8> vnet_connect_to_bpcd: [vnet_connect.c:296] connect_to_service() failed 18 0x12
18:22:50.313 [2428] <2> local_bpcr_connect: Can't connect to client hislnxciti001
18:22:50.313 [2428] <2> ConnectToBPCD: bpcd_connect_and_verify(hislnxciti001, hislnxciti001) failed: 25
<16>bptestbpcd main: Function ConnectToBPCD(hislnxciti001) failed: 25
18:22:50.313 [2428] <16> bptestbpcd main: Function ConnectToBPCD(hislnxciti001) failed: 25
<16>bptestbpcd main: cannot connect on socket
18:22:50.327 [2428] <16> bptestbpcd main: cannot connect on socket
<2>bptestbpcd: cannot connect on socket
18:22:50.327 [2428] <2> bptestbpcd: cannot connect on socket
<2>bptestbpcd: EXIT status = 25
18:22:50.327 [2428] <2> bptestbpcd: EXIT status = 25
cannot connect on socket
 

 

 

Backup and Recovery
NetBackup
UNIX
  • Marianne's avatar
    Marianne
    10 years ago
    A client this old says to me that this has worked in the past, right? You can see that the client is refusing connection on pbx (expected ), but also on vnetd and bpcd. These 2 services should be listening on the client. Check with 'netstat -a' on the client. If vnetd and bpcd are not LISTENING, check inetd or xinetd on the client. Work with sysadmin on the client. He/she should know what has changed and why. Encourage sysadmin to upgrade /migrate to supported OS.

2 Replies

Sort By
  • Steve_Lussiaud's avatar
    Steve_Lussiaud
    Level 4
    10 years ago

    Hello,

     

    your problem is your netbackup client version i think. Netbackup 6.X is unsupported for a long time.

    But if you have old os with X86 32 bits architecture, you cannot use 7.X client.

    For my test, 6.5.X is unsupported but run correctly with 7.5 and 7.6.0.4 master server. NBU client 6.0 is too old. Try to use a 6.5.6.

     

    Steve

     

     

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago
    A client this old says to me that this has worked in the past, right? You can see that the client is refusing connection on pbx (expected ), but also on vnetd and bpcd. These 2 services should be listening on the client. Check with 'netstat -a' on the client. If vnetd and bpcd are not LISTENING, check inetd or xinetd on the client. Work with sysadmin on the client. He/she should know what has changed and why. Encourage sysadmin to upgrade /migrate to supported OS.