cancel
Showing results for 
Search instead for 
Did you mean: 

bptestbpcd socked failed 23

Dear All,

I find the existing client failed to access to get the directory information. I can click the client on the NBU console host properties. But bptestpcd to client to return the socked failed 23.  I can ping the client on the media server, ping the media server on the client, host table record exisitng for both server and client. I have no idea the next step to fix the issue.  May i know the problem ?

C:\Program Files\VERITAS\NetBackup\bin\Admincmd>bptestbpcd -client oemdevdbs11 -verbose -debug
16:38:33.148 [1212.6956] <2> bptestbpcd: VERBOSE = 5
16:38:33.148 [1212.6956] <2> ParseConfigExA: Unknown configuration option on line 68: RenameIfExists = 0
16:38:33.148 [1212.6956] <2> init_cache: vnet_hosts.c.1045: host_cache_size: 200 0x000000c8
16:38:33.148 [1212.6956] <2> init_cache: vnet_hosts.c.1046: cache_time: 3600 0x00000e10
16:38:33.148 [1212.6956] <2> init_cache: vnet_hosts.c.1060: host_failed_cache_size: 40 0x00000028
16:38:33.148 [1212.6956] <2> init_cache: vnet_hosts.c.1061: cache_time: 3600 0x00000e10
16:38:33.148 [1212.6956] <2> init_cache: vnet_hosts.c.1045: host_cache_size: 200 0x000000c8
16:38:33.148 [1212.6956] <2> init_cache: vnet_hosts.c.1046: cache_time: 3600 0x00000e10
16:38:33.148 [1212.6956] <2> init_cache: vnet_hosts.c.1060: host_failed_cache_size: 40 0x00000028
16:38:33.148 [1212.6956] <2> init_cache: vnet_hosts.c.1061: cache_time: 3600 0x00000e10
16:38:33.148 [1212.6956] <2> vnet_async_connect: vnet_vnetd.c.4039: connect in progress: 0 0x00000000
16:38:33.180 [1212.6956] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2048: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
16:38:33.180 [1212.6956] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2062: service: bpdbm
16:38:33.226 [1212.6956] <2> vnet_async_connect: vnet_vnetd.c.4225: in progress connect: 0 0x00000000
16:38:33.226 [1212.6956] <2> vnet_async_connect: vnet_vnetd.c.4228: connect: async CONNECT FROM 10.26.144.154.3062 TO 10.2
6.144.153.13724 fd = 1808
16:38:33.226 [1212.6956] <2> logconnections: BPDBM CONNECT FROM 10.26.144.154.3062 TO 10.26.144.153.13724
16:38:33.226 [1212.6956] <2> vauth_get_user_name: vauth_comm.c.695: user_name: :Administrator
16:38:33.242 [1212.6956] <2> vauth_authentication_required: vauth_comm.c.749: no methods for address: no authentication re
quired
16:38:33.242 [1212.6956] <2> vauth_connector: vauth_comm.c.182: no methods for address: no authentication required
16:38:33.242 [1212.6956] <2> check_authentication: no authentication required
16:38:33.242 [1212.6956] <2> vnet_check_vxss_client_magic_with_info: vnet_vxss_helper.c.770: Ignoring VxSS authentication:
2 0x00000002
16:38:33.242 [1212.6956] <2> vnet_check_vxss_client_magic_with_info: vnet_vxss_helper.c.926: Not using VxSS authentication
: 2 0x00000002
16:38:33.539 [1212.6956] <2> db_getCLIENT: db_CLIENTreceive: no entity was found 227
16:38:33.539 [1212.6956] <2> ConnectToBPCD: db_getCLIENT(oemdevdbs11) failed: 227
16:38:33.539 [1212.6956] <2> local_bpcr_connect: bpcr.c.276: connect_opts = 0x01000100 connect_opts2 = 0x01000100
16:38:33.539 [1212.6956] <2> local_bpcr_connect: bpcr.c.283: connect_opts = 0x01000100
16:38:33.539 [1212.6956] <2> local_bpcr_connect: bpcr.c.322: daemon_port_type = 0
16:38:33.539 [1212.6956] <2> vnet_async_connect: vnet_vnetd.c.4039: connect in progress: 0 0x00000000
16:38:38.586 [1212.6956] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2048: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
16:38:38.586 [1212.6956] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2062: service: bpcd
16:38:42.633 [1212.6956] <2> vnet_async_connect: vnet_vnetd.c.4225: in progress connect: 0 0x00000000
16:38:42.633 [1212.6956] <2> vnet_async_connect: vnet_vnetd.c.4228: connect: async CONNECT FROM 10.26.144.154.3063 TO 10.2
6.102.196.13724 fd = 1808
16:38:42.633 [1212.6956] <2> logconnections: BPCD CONNECT FROM 10.26.144.154.3063 TO 10.26.102.196.13724
16:38:42.633 [1212.6956] <2> vauth_authentication_required: vauth_comm.c.749: no methods for address: no authentication re
quired
16:38:42.633 [1212.6956] <2> vauth_connector: vauth_comm.c.182: no methods for address: no authentication required
16:38:42.633 [1212.6956] <2> bpcr_authenticate_connection: no authentication required
16:38:42.633 [1212.6956] <2> vnet_connect_to_vnetd_extra: vnet_vnetd.c.182: msg: VNETD CONNECT FROM 10.26.144.154.3064 TO
10.26.102.196.13724 fd = 1776
16:38:47.680 [1212.6956] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.535: VN_REQUEST_CONNECT_FORWARD_SOCKET:
10 0x0000000a
16:38:47.680 [1212.6956] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.552: ipc_string: /tmp/vnet-254926103547
60509433000000000-9SaGYX
16:38:47.820 [1212.6956] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.563: hash_str1: c66bb5e575502307c42046f
334e1a3fd
16:38:47.820 [1212.6956] <2> get_short: (2) premature end of file (byte 1)
16:38:47.820 [1212.6956] <2> bpcr_put_vnetd_forward_socket: get_short failed: 5
16:38:47.820 [1212.6956] <2> local_bpcr_connect: bpcr_put_vnetd_forward_socket failed: 23
16:38:47.820 [1212.6956] <2> ConnectToBPCD: bpcd_connect_and_verify(oemdevdbs11, oemdevdbs11) failed: 23
<16>bptestbpcd main: Function ConnectToBPCD(devuaedbs11) failed: 23
16:38:47.820 [1212.6956] <16> bptestbpcd main: Function ConnectToBPCD(oemdevdbs11) failed: 23
<2>bptestbpcd: socket read failed
16:38:47.820 [1212.6956] <2> bptestbpcd: socket read failed
<2>bptestbpcd: EXIT status = 23
16:38:47.820 [1212.6956] <2> bptestbpcd: EXIT status = 23
socket read failed

8 Replies

Re: bptestbpcd socked failed 23

Hi @Home_224

It looks to port communication problem. Rather than belive on Ping response always test connectivity using "telnet or CURL or nc" utilities.

Netbackup looks connections on port 1556, 13782 and 13724. Verify if you can telnet to client on these ports.

Re: bptestbpcd socked failed 23

@pats_729 

Yes I can telnet to host with these ports on the media server

Re: bptestbpcd socked failed 23

@Home_224 

thats very unlike when telnet connects but bptestbpcd fails.. check these commands

On Media Server

bpclntcmd -hn <client name>

On Client

bpclntcmd -hn <media name>

bpclntcmd -hn <master name>

bpclntcmd -pn -verbose       <--- This one should show a successful connection to master.

 

Re: bptestbpcd socked failed 23

@Home_224 

Is this the same environment where you have Solaris Master and Media server(s) ?

Your command shows bptestbpcd from a Windows machine.
What is the role of the Windows machine?

To browse a client's filesystem from the Policy window, you need to perform connectivity tests from the master server.
Be sure that you have bpcd log folder on the client before you run bptestbpcd.
Check bpcd log on the client for errors.

You can also use bpcoverage command on the master:

/usr/openv/netbackup/bin/admincmd/bpcoverage -c <client-name>

*** bpcoverage can be used to test or gather the following information from the client:

  • Check connectivity to a NetBackup client system
  • Check what mount points or drive letters are seen on a client
  • Check if the mount point or drive letter will be backed up by a policy on the master server
  • Check the client OS version and NetBackup version installed.  

Re: bptestbpcd socked failed 23

bpclntcmd -hn oemdevdbs11
host devuaedbs11: oemdevdbs11 at 10.26.102.196 (0xc4661a0a)
aliases:

On Client
cd /usr/openv/netbackup/bin/
bpclntcmd -hn oemdevmes41
host oemdevmes41: oemdevmes41 at 10.26.144.154 (0xa1a909a)
aliases:
bpclntcmd -hn oemdevmes41
host oemdevmes41: oemdevmes41 at 10.26.144.150 (0xa1a9096)
aliases:
# bpclntcmd -pn -verbose
expecting response from server oemdevbms

Thanks,

Re: bptestbpcd socked failed 23

@Marianne 

bpcoverage -c oemdevdbs11
File System Backup Coverage Report (UNIX and Windows only)
------------------------------------------------------------------------- --------

Key: * - Policy is not active
UNCOVERED - Mount Point not covered by an active policy
MULTIPLE - Mount Point covered by multiple active policies


CLIENT: oemdevdbs11

Mount Point Device Backed Up By Policy Notes
----------- ------ ------------------- -----
/ /dev/md/dsk/d0 *adhoc_SIT_Unix_OS UNCOVERED
/ /dev/md/dsk/d0 *SIT_Unix_OS UNCOVERED
/ /dev/md/dsk/d0 *SIT_Unix_DBS11_DMS1 1_APP11_WEB11 UNCOVERED
/crs /dev/vx/dsk/crs_dg/crs_vol *adhoc_SIT_Unix_OS UNCOVERED
/db2/a01 /dev/vx/dsk/db2_datadg/db2_a01_vol *adhoc_SIT_Unix_OS UNCOVERED
/db2/a01 /dev/vx/dsk/db2_datadg/db2_a01_vol *SIT_Unix_Data_DBS11 UNCOVERED
/db2/d01 /dev/vx/dsk/db2_datadg/db2_d01_vol *adhoc_SIT_Unix_OS UNCOVERED
/db2/d01 /dev/vx/dsk/db2_datadg/db2_d01_vol *SIT_Unix_Data_DBS11 UNCOVERED
/db2/d02 /dev/vx/dsk/db2_datadg/db2_d02_vol *adhoc_SIT_Unix_OS UNCOVERED
/db2/d02 /dev/vx/dsk/db2_datadg/db2_d02_vol *SIT_Unix_Data_DBS11 UNCOVERED
/db2/d03 /dev/vx/dsk/db2_datadg/db2_d03_vol *adhoc_SIT_Unix_OS UNCOVERED
/db2/d03 /dev/vx/dsk/db2_datadg/db2_d03_vol *SIT_Unix_Data_DBS11 UNCOVERED
/db2/r01 /dev/vx/dsk/db2_datadg/db2_r01_vol *adhoc_SIT_Unix_OS UNCOVERED
/db2/r01 /dev/vx/dsk/db2_datadg/db2_r01_vol *SIT_Unix_Data_DBS11 UNCOVERED
/db5/a01 /dev/vx/dsk/db5_datadg/db5_a01_vol *adhoc_SIT_Unix_OS UNCOVERED
/db5/a01 /dev/vx/dsk/db5_datadg/db5_a01_vol *SIT_Unix_Data_DBS11 UNCOVERED
/db5/d01 /dev/vx/dsk/db5_datadg/db5_d01_vol *adhoc_SIT_Unix_OS UNCOVERED
/db5/d01 /dev/vx/dsk/db5_datadg/db5_d01_vol *SIT_Unix_Data_DBS11 UNCOVERED
/db5/d02 /dev/vx/dsk/db5_datadg/db5_d02_vol *adhoc_SIT_Unix_OS UNCOVERED
/db5/d02 /dev/vx/dsk/db5_datadg/db5_d02_vol *SIT_Unix_Data_DBS11 UNCOVERED
/db5/d03 /dev/vx/dsk/db5_datadg/db5_d03_vol *adhoc_SIT_Unix_OS UNCOVERED
/db5/d03 /dev/vx/dsk/db5_datadg/db5_d03_vol *SIT_Unix_Data_DBS11 UNCOVERED
/db5/r01 /dev/vx/dsk/db5_datadg/db5_r01_vol *adhoc_SIT_Unix_OS UNCOVERED
/db5/r01 /dev/vx/dsk/db5_datadg/db5_r01_vol *SIT_Unix_Data_DBS11 UNCOVERED
/dev/odm /dev/odm *adhoc_SIT_Unix_OS UNCOVERED
/etc/mnttab mnttab *adhoc_SIT_Unix_OS UNCOVERED
/export/home /dev/md/dsk/d7 *adhoc_SIT_Unix_OS UNCOVERED
/export/home /dev/md/dsk/d7 *SIT_Unix_OS UNCOVERED
/opt /dev/md/dsk/d5 *adhoc_SIT_Unix_OS UNCOVERED
/opt /dev/md/dsk/d5 *SIT_Unix_OS UNCOVERED
/usr /dev/md/dsk/d6 *adhoc_SIT_Unix_OS UNCOVERED
/usr /dev/md/dsk/d6 *SIT_Unix_OS UNCOVERED
/var /dev/md/dsk/d4 *adhoc_SIT_Unix_OS UNCOVERED
/var /dev/md/dsk/d4 *SIT_Unix_OS UNCOVERED

Policy Hardware/OS Report
-------------------------

Key: * - Policy is not active
CLIENT - hostname (uname information)
VERSION - NetBackup version running on the client


CLIENT: oemdevdbs11 (sun4u/SunOS 5.9 Generic_122300-56)
VERSION: NetBackup-Solaris9 6.5.6

Policy Name Hardware/OS
----------- -----------
*SIT_Servers_DBS Solaris/Solaris9
*SIT_Unix_DBS11_DMS11_APP11_WEB11 Solaris/Solaris9
*SIT_Unix_Data_DBS11 Solaris/Solaris9
*SIT_Unix_OS Solaris/Solaris9
SITracdbs_ORA10g_TIAEEF_Offhost Solaris/Solaris9
*adhoc_SIT_Unix_OS Solaris/Solaris9

Re: bptestbpcd socked failed 23

@Marianne 

Is this the same environment where you have Solaris Master and Media server(s) ?
Ans: Master Cluster ( Solaris ) Media : Window
Your command shows bptestbpcd from a Windows machine.
What is the role of the Windows machine? Media

Re: bptestbpcd socked failed 23


@Home_224 wrote:

On Client
cd /usr/openv/netbackup/bin/
bpclntcmd -hn oemdevmes41
host oemdevmes41: oemdevmes41 at 10.26.144.154 (0xa1a909a)

bpclntcmd -hn oemdevmes41
host oemdevmes41: oemdevmes41 at 10.26.144.150 (0xa1a9096)


So, you issued the same command twice for the same hostname (media server), but it came back with 2 different IP addresses?

Please double-check which one is correct and check that only one entry is in /etc/hosts on the client.

We see in bptestbpcd output that the media server is using 10.26.144.154 as source IP.

There is also different IPs used for the client.

Here you show this IP for the client:


@Home_224 wrote:

bpclntcmd -hn oemdevdbs11
host devuaedbs11: oemdevdbs11 at 10.26.102.196 (0xc4661a0a)


But in bptestbpcd, the media server was using this IP address to attempt connection to the client: 10.26.144.153

CONNECT FROM 10.26.144.154.3062 TO 10.26.144.153.13724

So, the IP addresses seem to be mixed up.

Check that the same IP addresses are used everywhere - master, media, client.
Check all hosts files as well as DNS (if used in this environment).