Forum Discussion

Jain_Thomas's avatar
Jain_Thomas
Level 3
11 years ago

socket read failed - status 23

Hi All

Status 23 - socket read failed 

 

Created a new policy 

Added the Master Server IP and hostname to /etc/hosts on master server

Added the Client Ip and hostname to /etc/hosts on client 

Installed the client Software

 

root @Master [/opt/openv/netbackup/bin/admincmd]#./bptestbpcd -client Aries-DC -verbose -debug

12:57:35.792 [5425] <2> bptestbpcd: VERBOSE = 5
12:57:35.792 [5425] <2> read_client: ?
12:57:35.793 [5425] <2> read_client: opendir() failed: Aries-DC: No such file or directory (2)
12:57:35.793 [5425] <2> ConnectToBPCD: db_getCLIENT(Aries-DC) failed: 227
12:57:35.793 [5425] <2> ParseConfigExA: Option (CLIENT_NAME) redefined on line 12, discarding definition on line 11.
12:57:35.793 [5425] <2> vauth_get_user_name: vauth_comm.c.687: cached_user_name: root
12:57:35.793 [5425] <2> vauth_get_user_name: vauth_comm.c.689: cached_user_name: :root
12:57:35.793 [5425] <2> vauth_get_user_name: vauth_comm.c.695: user_name: :root
12:57:35.794 [5425] <2> local_bpcr_connect: bpcr.c.276: connect_opts = 0x01000100 connect_opts2 = 0x01000100
12:57:35.794 [5425] <2> local_bpcr_connect: bpcr.c.283: connect_opts = 0x01000100
12:57:35.794 [5425] <2> local_bpcr_connect: bpcr.c.322: daemon_port_type = 0
12:57:35.794 [5425] <2> init_cache: vnet_hosts.c.1045: host_cache_size: 200 0x000000c8
12:57:35.794 [5425] <2> init_cache: vnet_hosts.c.1046: cache_time: 3600 0x00000e10
12:57:35.794 [5425] <2> init_cache: vnet_hosts.c.1060: host_failed_cache_size: 40 0x00000028
12:57:35.794 [5425] <2> init_cache: vnet_hosts.c.1061: cache_time: 3600 0x00000e10
12:57:35.794 [5425] <2> init_cache: vnet_hosts.c.1045: host_cache_size: 200 0x000000c8
12:57:35.794 [5425] <2> init_cache: vnet_hosts.c.1046: cache_time: 3600 0x00000e10
12:57:35.794 [5425] <2> init_cache: vnet_hosts.c.1060: host_failed_cache_size: 40 0x00000028
12:57:35.794 [5425] <2> init_cache: vnet_hosts.c.1061: cache_time: 3600 0x00000e10
12:57:35.795 [5425] <2> vnet_async_connect: vnet_vnetd.c.4033: connect in progress: 0 0x00000000
12:57:35.877 [5425] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2046: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
12:57:35.877 [5425] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2060: service: bpcd
12:57:35.879 [5425] <2> vnet_async_connect: vnet_vnetd.c.4219: in progress connect: 0 0x00000000
12:57:35.879 [5425] <2> vnet_async_connect: vnet_vnetd.c.4222: connect: async CONNECT FROM 10.244.0.90.59049 TO 10.244.0.60.13724 fd = 4
12:57:35.879 [5425] <2> logconnections: BPCD CONNECT FROM 10.244.0.90.59049 TO 10.244.0.60.13724
12:57:35.879 [5425] <2> vauth_authentication_required: vauth_comm.c.749: no methods for address: no authentication required
12:57:35.879 [5425] <2> vauth_connector: vauth_comm.c.182: no methods for address: no authentication required
12:57:35.879 [5425] <2> bpcr_authenticate_connection: no authentication required
12:57:35.880 [5425] <2> vnet_connect_to_vnetd_extra: vnet_vnetd.c.180: msg: VNETD CONNECT FROM 10.244.0.90.59050 TO 10.244.0.60.13724 fd = 5
12:57:35.958 [5425] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.533: VN_REQUEST_CONNECT_FORWARD_SOCKET: 10 0x0000000a
12:57:35.960 [5425] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.550: ipc_string: /tmp/vnet-02974375860741941061000000000-1CaWZf
12:57:35.960 [5425] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.561: hash_str1: 1c5c16c74f07cf3aa172fe594561aef1
12:57:35.960 [5425] <2> get_short: (2) premature end of file (byte 1)
12:57:35.960 [5425] <2> bpcr_put_vnetd_forward_socket: get_short failed: 5
12:57:35.960 [5425] <2> local_bpcr_connect: bpcr_put_vnetd_forward_socket failed: 23
12:57:35.961 [5425] <2> ConnectToBPCD: bpcd_connect_and_verify(Aries-DC, Aries-DC) failed: 23
<16>bptestbpcd main: Function ConnectToBPCD(Aries-DC) failed: 23
12:57:35.961 [5425] <16> bptestbpcd main: Function ConnectToBPCD(Aries-DC) failed: 23
<2>bptestbpcd: socket read failed
12:57:35.961 [5425] <2> bptestbpcd: socket read failed
<2>bptestbpcd: EXIT status = 23
12:57:35.961 [5425] <2> bptestbpcd: EXIT status = 23
socket read failed
root @Master [/opt/openv/netbackup/bin/admincmd]#
 
root @Master [/opt/openv/netbackup/bin]#./bpclntcmd -hn Aries-DC
host Aries-DC: Aries-DC at x.x.x.x (0xaf4003c)
aliases:
root @Master [/opt/openv/netbackup/bin]#
 
 
 
Also able to rsh to the client from master without password.
 
Using Natbackup 6.5
 
What can be the possible casue for this error?
 
 
 
 

 

7.1.x and Earlier
Backup and Recovery
NetBackup
Solaris
  • Marianne's avatar
    Marianne
    11 years ago

    What OS is the client?

    Is there a firewall on the client? Or a firewall between master and client?

    You can see that the server is trying to connect to the client on port 13724 (vnetd):

    BPCD CONNECT FROM 10.244.0.90.59049 TO 10.244.0.60.13724

    Can you telnet to the client on port 13724?

    Have you created bpcd log on the client before trying bptestbpcd?

    Was anything logged in bpcd?

    Have you added master's IP address and hostname (that corresponds with SERVER entry in client's bp.conf) to client's hosts file?

    Can you resolve master's hostname and IP address from the client?

    Check as follows on client:

    bpclntcmd -hn <master>
    bpclntcmd -ip <master-IP>
    bpclntcmd -pn

    As per revaroo's post: Any reason why you are using NBU 6.5?

4 Replies

Sort By
  • revarooo's avatar
    revarooo
    Level 6
    11 years ago

    6.5 is no longer supported.

    Do you have the master servers Ip/host in the clients /etc/hosts file and the clients in the masters hosts file?

     

    Can you: telnet <client> 13782

     

    Is connection successful?

     

    Enable the bpcd log on the client by creating the directory %install_path%\netbackup\logs\bpcd\  (/usr/openv/netbackup/logs/bpcd/ if unix)

    Try the bptestbpcd command again. Anything being logged in the bpcd log?

  • Marianne's avatar
    Marianne
    Level 6
    11 years ago

    What OS is the client?

    Is there a firewall on the client? Or a firewall between master and client?

    You can see that the server is trying to connect to the client on port 13724 (vnetd):

    BPCD CONNECT FROM 10.244.0.90.59049 TO 10.244.0.60.13724

    Can you telnet to the client on port 13724?

    Have you created bpcd log on the client before trying bptestbpcd?

    Was anything logged in bpcd?

    Have you added master's IP address and hostname (that corresponds with SERVER entry in client's bp.conf) to client's hosts file?

    Can you resolve master's hostname and IP address from the client?

    Check as follows on client:

    bpclntcmd -hn <master>
    bpclntcmd -ip <master-IP>
    bpclntcmd -pn

    As per revaroo's post: Any reason why you are using NBU 6.5?

  • Jain_Thomas's avatar
    Jain_Thomas
    Level 3
    11 years ago

    Hi All

     

    OS = Solaris 10

    There is no Firewall btwn Master and Client

    Able to telnet to port 13724
     
    root @Master [/]#telnet 10.244.0.60 13724
    Trying 10.244.0.60...
    Connected to 10.244.0.60.
    Escape character is '^]'.
     
     
    Yes, Master Server IP/hostname is in the clients /etc/hosts file and clinets in the master servers file.
     
     
     
    Telnet is not possible to Port 13782
     
     
     
    Tried bptestbpcd ... Nothin is logged in the bpcd log 
     
     
     
    root @Master [/opt/openv/netbackup/bin/admincmd]#./bptestbpcd -client Aries-DC -verbose
    <16>bptestbpcd main: Function ConnectToBPCD(Aries-DC) failed: 23
    socket read failed
    root @Master [/opt/openv/netbackup/bin/admincmd]#
     
     
    Guys Thanks for the support :) 
     
    Was not resolving the IP.
     
    Its resolved Now.
     
    About NBU 6.5 .. We are upgrading to the latest version by this month end.
     
    Thanks a Lot
     
    Jain Thomas
     
     
     
     
  • Marianne's avatar
    Marianne
    Level 6
    11 years ago

    Use hostnames when you test connectivity - not IP addresses.

    Please select a post that helped you and 'Mark as solution'. 

    This will help other users with similar issues.