cancel
Showing results for 
Search instead for 
Did you mean: 

error code 54

rookie11
Moderator
Moderator
   VIP   

master NBU 6.5.3.1 OS solaris 10

media NBU 6.5.3.1 OS solaris 10

client NBU 6.5 OS win 2003

master to NBU client connectivity is fine

telnet cni 13782
Trying 135.193.241.31...
Connected to cni
Escape character is '^]'.

 

 

Connection to cni
traceroute cni  drop packets after 9 hops
ping -s cni fine
 
but connectivity to media server to NBU client have issue
 
ping -s cni fine
 
traceroute cni packet drop after 10 hops
 
telnet cniweb-ebr 13782  no response for 5 minutes generally we get ip address and connected
Trying 135.193.241.31...
^C
 
please suggest something
16 REPLIES 16

marekkedzierski
Level 6
Partner

Read this article:

http://www.symantec.com/business/support/index?page=content&id=TECH43129

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Create bpcd log on client, then do the following from master and media server:

bptestbpcd -client <client-name> -verbose

 

Please check bpcd log on client.

If client is behind a firewall, ensure that port 13724 (vnetd) is open in both directions between master & client a well as media server & client. Since 6.0, all connections to bpcd is channelled via vnetd.

 

(The advanced troubleshooting doc for status 54 (link provided by Marek) probably contains the same info - just unable to download it right now (not sure if the problem is on our side or Symantec's..))

Andy_Welburn
Level 6

Failed for me first time - just goes to KB search page - but worked second time around.

rookie11
Moderator
Moderator
   VIP   

hi guys i will write my problem in simplfied way

 

1 from master and media i m able to ping client name and ip address.

but telnet clientname 13782 -- works gud from master

telnet clientname 13724 -- works gud from master

telnet clientname 13782 --- no response from media server

telnet clientname 13724 --- no response from media server

2 bpclntcmd -hn , bpclntcmd -ip works fine from client server

3 ac@asp: bpcoverage -c 135.193.241.31


CLIENT: 135.193.241.31
Exit status 24: socket write failed

 

no response from media server of command bpcoverage.

please suggest something

rookie11
Moderator
Moderator
   VIP   

no response from media server of bptestbpcd command

bptestbpcd on master server

ac@asp: bptestbpcd -client 135.193.241.31 -verbose
1 1 1
135.53.28.53:41057 -> 135.193.241.31:13724
135.53.28.53:41080 -> 135.193.241.31:13724
PEER_NAME = asp <master server>
HOST_NAME = cni clientname
CLIENT_NAME = cni clientname
VERSION = 0x06500000
PLATFORM = nt
PATCH_VERSION =
SERVER_PATCH_VERSION =
 

Zahid_Haseeb
Moderator
Moderator
Partner    VIP    Accredited

Rockie 11 i faced the problem ""socket write failed 24"" and i followed some steps which resolved my problem. I also like to share this with you. It may help you.

https://www-secure.symantec.com/connect/blogs/socket-write-failed24#comment-4726111

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

PLEASE don't use IP adresses when communicating with clients - use hostnames...

Are you using DNS in your environment or local hosts files?

If DNS, you HAVE TO ensure that reverse lookup is working. The client needs to resolve IP address to hostname. It uses this 'resolved hostname' to compare with SERVER entries. Only when this comparison succeeds will the 'handshake' complete. It is a security measure that ensures backup across the network to 'trusted' server only.

If your Solaris servers do not have DNS entries, then add hosts entries everywhere - master server, media server, client.
You will need to ensure that the client has hosts entries for master and media servers. The host names in ....\system32\drivers\etc\hosts for master and media needs to correspond with the SERVER entries in the clients Registry.

Don't try telnet to 13782 - as from NBU 6.0, comms to client is made on port 13724 (vnetd) as you can see from bptestbpcd output. The difference between telnet and bptestbpcd is that telnet test comms in one direction. bptestbpcd test comms with client as well as response from cllient back to server.

Did you create bpcd log directory on the client?
Can you see in the log that media server connection attempt was received by client?
See in bpcd log directory how the media server's incoming IP is resolved and compared with SERVER entries.

If no evidence of connection attempt - is there perhaps a firewall between media server and client?

Zahid_Haseeb
Moderator
Moderator
Partner    VIP    Accredited

Sorry all, i posted wrong

rookie11
Moderator
Moderator
   VIP   

bptestbpcd from media server :

a@media server: bptestbpcd -client 135.193.241.31 -debug -verbose
10:12:29.105 [8349] <2> bptestbpcd: VERBOSE = 5
10:12:29.107 [8349] <2> init_cache: vnet_hosts.c.990: host_cache_size: 200 0x000000c8
10:12:29.107 [8349] <2> init_cache: vnet_hosts.c.991: cache_time: 3600 0x00000e10
10:12:29.108 [8349] <2> init_cache: vnet_hosts.c.1003: host_failed_cache_size: 40 0x00000028
10:12:29.108 [8349] <2> init_cache: vnet_hosts.c.1004: cache_time: 3600 0x00000e10
10:12:29.159 [8349] <2> init_cache: vnet_hosts.c.990: host_cache_size: 200 0x000000c8
10:12:29.159 [8349] <2> init_cache: vnet_hosts.c.991: cache_time: 3600 0x00000e10
10:12:29.159 [8349] <2> init_cache: vnet_hosts.c.1003: host_failed_cache_size: 40 0x00000028
10:12:29.159 [8349] <2> init_cache: vnet_hosts.c.1004: cache_time: 3600 0x00000e10
10:12:29.160 [8349] <2> vnet_async_connect: vnet_vnetd.c.4019: connect in progress: 0 0x00000000
10:12:29.320 [8349] <2> vnet_pop_byte: vnet.c.184: errno: 150 0x00000096
10:12:29.320 [8349] <2> vnet_pop_byte: vnet.c.186: Function failed: 9 0x00000009
10:12:29.320 [8349] <2> vnet_pop_string: vnet.c.266: Function failed: 9 0x00000009
10:12:29.320 [8349] <2> vnet_pop_signed: vnet.c.310: Function failed: 9 0x00000009
10:12:29.320 [8349] <2> version_connect: vnet_vnetd.c.1812: Function failed: 9 0x00000009
10:12:29.320 [8349] <2> do_vnetd_service: vnet_vnetd.c.4393: version_connect failed: 9 0x00000009
10:12:29.321 [8349] <2> vnet_async_connect: vnet_vnetd.c.4193: do_vnetd_service failed: 9 0x00000009
10:12:29.321 [8349] <2> vnet_async_connect: vnet_vnetd.c.4019: connect in progress: 1 0x00000001
10:12:29.396 [8349] <2> vnet_async_connect: vnet_vnetd.c.4205: in progress connect: 1 0x00000001
10:12:29.396 [8349] <2> vnet_async_connect: vnet_vnetd.c.4208: connect: async CONNECT FROM 135.33.138.27.51198 TO 135.53.28.53.13721 fd = 4
10:12:29.397 [8349] <2> logconnections: BPDBM CONNECT FROM 135.33.138.27.51198 TO 135.53.28.53.13721
10:12:29.397 [8349] <2> vauth_get_user_name: vauth_comm.c.687: cached_user_name: root
10:12:29.397 [8349] <2> vauth_get_user_name: vauth_comm.c.689: cached_user_name: :root
10:12:29.397 [8349] <2> vauth_get_user_name: vauth_comm.c.695: user_name: :root
10:12:29.398 [8349] <2> vauth_authentication_required: vauth_comm.c.749: no methods for address: no authentication required
10:12:29.398 [8349] <2> vauth_connector: vauth_comm.c.182: no methods for address: no authentication required
10:12:29.398 [8349] <2> check_authentication: no authentication required
10:12:29.398 [8349] <2> vnet_check_vxss_client_magic_with_info: vnet_vxss_helper.c.770: Ignoring VxSS authentication: 2 0x00000002
10:12:29.398 [8349] <2> vnet_check_vxss_client_magic_with_info: vnet_vxss_helper.c.926: Not using VxSS authentication: 2 0x00000002
10:12:29.857 [8349] <2> db_getCLIENT: db_CLIENTreceive: no entity was found 227
10:12:29.857 [8349] <2> get_long: (2) premature end of file (byte 1)
10:12:29.858 [8349] <2> ConnectToBPCD: db_getCLIENT(135.193.241.31) failed: 227
10:12:29.860 [8349] <2> local_bpcr_connect: bpcr.c.276: connect_opts = 0x01000100 connect_opts2 = 0x01000100
10:12:29.860 [8349] <2> local_bpcr_connect: bpcr.c.283: connect_opts = 0x01000100
10:12:29.860 [8349] <2> local_bpcr_connect: bpcr.c.322: daemon_port_type = 0
10:12:29.861 [8349] <2> vnet_async_connect: vnet_vnetd.c.4019: connect in progress: 0 0x00000000
10:12:39.869 [8349] <2> vnet_async_connect: vnet_vnetd.c.4019: connect in progress: 1 0x00000001
10:16:14.554 [8349] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 145 0x00000091
10:16:24.565 [8349] <2> vnet_async_connect: vnet_vnetd.c.4019: connect in progress: 0 0x00000000
10:16:34.575 [8349] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 145 0x00000091
10:16:45.595 [8349] <2> vnet_async_connect: vnet_vnetd.c.4019: connect in progress: 1 0x00000001
10:20:09.530 [8349] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 145 0x00000091
10:20:19.541 [8349] <2> vnet_async_connect: vnet_vnetd.c.4019: connect in progress: 0 0x00000000
10:20:30.291 [8349] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 145 0x00000091
10:20:42.311 [8349] <2> vnet_async_connect: vnet_vnetd.c.4019: connect in progress: 1 0x00000001
10:24:04.237 [8349] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 145 0x00000091
10:24:14.247 [8349] <2> vnet_async_connect: vnet_vnetd.c.4019: connect in progress: 0 0x00000000
10:24:27.007 [8349] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 145 0x00000091
10:24:41.028 [8349] <2> vnet_async_connect: vnet_vnetd.c.4019: connect in progress: 1 0x00000001
10:27:58.943 [8349] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 145 0x00000091
10:28:08.953 [8349] <2> vnet_async_connect: vnet_vnetd.c.4019: connect in progress: 0 0x00000000
10:28:25.723 [8349] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 145 0x00000091
10:28:43.744 [8349] <2> vnet_async_connect: vnet_vnetd.c.4019: connect in progress: 1 0x00000001
10:31:53.649 [8349] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 145 0x00000091
10:32:28.440 [8349] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 145 0x00000091
10:32:28.440 [8349] <2> vnet_connect_to_service_or_vnetd: vnet_vnetd.c.3570: vnet_async_connect failed: 18 0x00000012
10:32:28.440 [8349] <2> nb_connect_to_vnetd_or_legacy: comm.c.2030: vnet_connect_to_vnetd_or_service failed: 18
10:32:28.440 [8349] <2> local_bpcr_connect: nb_connect_to_vnetd_service(135.193.241.31) failed: 25
10:32:28.440 [8349] <2> local_bpcr_connect: Can't connect to client 135.193.241.31
10:32:28.440 [8349] <2> ConnectToBPCD: bpcd_connect_and_verify(135.193.241.31, 135.193.241.31) failed: 25
<16>bptestbpcd main: Function ConnectToBPCD(135.193.241.31) failed: 25
10:32:28.441 [8349] <16> bptestbpcd main: Function ConnectToBPCD(135.193.241.31) failed: 25
<2>bptestbpcd: cannot connect on socket
10:32:28.441 [8349] <2> bptestbpcd: cannot connect on socket
<2>bptestbpcd: EXIT status = 25
10:32:28.441 [8349] <2> bptestbpcd: EXIT status = 25
cannot connect on socket

rookie11
Moderator
Moderator
   VIP   

bptestbpcd from master server

ac8970@master server : bptestbpcd -client 135.193.241.31 -debug -verbose
12:12:43.790 [29149] <2> bptestbpcd: VERBOSE = 1
12:16:28.461 [29149] <2> vnet_async_connect: vnet_vnetd.c.4217: getsockopt SO_ERROR returned: 145 0x00000091
12:16:38.630 [29149] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2043: VN_REQUEST_SERVICE_SOCKET: 6 0x00000006
12:16:38.630 [29149] <2> vnet_vnetd_service_socket: vnet_vnetd.c.2057: service: bpcd
12:16:38.777 [29149] <2> logconnections: BPCD CONNECT FROM 135.53.28.53.59635 TO 135.193.241.31.13724
12:16:38.852 [29149] <2> vnet_connect_to_vnetd_extra: vnet_vnetd.c.179: msg: VNETD CONNECT FROM 135.53.28.53.59655 TO 135.193.241.31.13724 fd = 5
12:16:38.939 [29149] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.532: VN_REQUEST_CONNECT_FORWARD_SOCKET: 10 0x0000000a
12:16:39.089 [29149] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.549: ipc_string: 2751
1 1 1
135.53.28.53:59635 -> 135.193.241.31:13724
135.53.28.53:59655 -> 135.193.241.31:13724
12:16:39.508 [29149] <2> bpcr_get_peername_rqst: Server peername length = 21
12:16:39.682 [29149] <2> bpcr_get_hostname_rqst: Server hostname length = 22
12:16:39.862 [29149] <2> bpcr_get_clientname_rqst: Server client name length = 22
12:16:40.042 [29149] <2> bpcr_get_version_rqst: bpcd version: 06500000
12:16:40.218 [29149] <2> bpcr_get_platform_rqst: Server client platform length = 2
12:16:40.392 [29149] <2> bpcr_get_version_rqst: bpcd version: 06500000
12:16:40.392 [29149] <2> bpcr_patch_version_rqst: bpcd version 0x06500000 is too old for the BPCD_PATCH_VERSION_RQST
12:16:40.392 [29149] <2> bpcr_patch_version_rqst: bpcd returned failure: 16
12:16:40.392 [29149] <16> bpcr_patch_version_rqst() failed, status = 16,  errno = 0: get_patch_version
12:16:40.571 [29149] <2> bpcr_get_version_rqst: bpcd version: 06500000
12:16:40.571 [29149] <2> bpcr_patch_version_rqst: bpcd version 0x06500000 is too old for the BPCD_PATCH_VERSION_RQST
12:16:40.571 [29149] <2> bpcr_patch_version_rqst: bpcd returned failure: 16
12:16:40.571 [29149] <16> bpcr_patch_version_rqst() failed, status = 16,  errno = 0: get_patch_version
PEER_NAME = asp.com
HOST_NAME = cni.com
CLIENT_NAME = cni.com
VERSION = 0x06500000
PLATFORM = nt
PATCH_VERSION =
SERVER_PATCH_VERSION =
12:20:25.237 [29149] <2> vnet_bind_and_connect_extra: vnet_bind.c.222: save_errno: 145 0x00000091
12:24:10.917 [29149] <2> vnet_bind_and_connect_extra: vnet_bind.c.222: save_errno: 145 0x00000091
12:24:13.000 [29149] <2> vnet_connect_to_vnetd_extra: vnet_vnetd.c.179: msg: VNETD CONNECT FROM 135.53.28.53.33849 TO 135.193.241.31.13724 fd = 6
12:24:13.091 [29149] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.532: VN_REQUEST_CONNECT_FORWARD_SOCKET: 10 0x0000000a
12:24:13.242 [29149] <2> vnet_vnetd_connect_forward_socket_begin: vnet_vnetd.c.549: ipc_string: 2761
12:24:13.321 [29149] <2> put_long: (11) network write() error: Broken pipe (32); socket = 4
12:24:13.321 [29149] <2> bpcr_put_vnetd_forward_socket: put_string 2761 failed: 32
12:24:13.321 [29149] <2> bpcr_new_standard_socket_rqst: bpcr_get_vnetd_socket_rqst failed: 24
<16>bptestbpcd main: Function bpcr_new_standard_socket_rqst(135.193.241.31) failed: 24
12:24:13.322 [29149] <16> bptestbpcd main: Function bpcr_new_standard_socket_rqst(135.193.241.31) failed: 24
12:24:13.322 [29149] <2> put_short: (10) network write() error: Bad file number (9); socket = 4
12:24:13.322 [29149] <2> bpcr_disconnect_rqst: bpcr protocol error - couldn't send request type
<16>bptestbpcd main: Function bpcr_new_standard_socket_rqst(135.193.241.31) failed: 24
12:24:13.322 [29149] <16> bptestbpcd main: Function bpcr_new_standard_socket_rqst(135.193.241.31) failed: 24
<2>bptestbpcd: socket close failed
12:24:13.322 [29149] <2> bptestbpcd: socket close failed
<2>bptestbpcd: EXIT status = 22
12:24:13.322 [29149] <2> bptestbpcd: EXIT status = 22
socket close failed
 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I'm going to repeat my previous post:

PLEASE don't use IP adresses when communicating with clients - use hostnames...

Are you using DNS in your environment or local hosts files?

If DNS, you HAVE TO ensure that reverse lookup is working. The client needs to resolve IP address to hostname.

It uses this 'resolved hostname' to compare with SERVER entries. Only when this comparison succeeds will the 'handshake' complete. It is a security measure that ensures backup across the network to 'trusted' server only.

If your Solaris servers do not have DNS entries, then add hosts entries everywhere - master server, media server, client.
You will need to ensure that the client has hosts entries for master and media servers. The host names in ....\system32\drivers\etc\hosts for master and media needs to correspond with the SERVER entries in the clients Registry.

 

Please post client's bpcd log file that contains connection requests from master and media.

Zahid_Haseeb
Moderator
Moderator
Partner    VIP    Accredited

Rookie as marianne said dont use IP in the below command. Use the hostname(computername) at the place where you are using IP  and share the result

bptestbpcd -client 135.193.241.31 -debug -verbose

rookie11
Moderator
Moderator
   VIP   

hosts file entires are present in client , master , media server

bpclntcmd aalso works fine from client , master , media server

bptestbpcd from media server

a@rsp: bptestbpcd -client cniweb.gfiprod.att.com -verbose
<16>bptestbpcd main: Function ConnectToBPCD(cniweb.gfiprod.att.com) failed: 25
cannot connect on socket
 

bptestbpcd from master server

a@asp: bptestbpcd -client cni.com -verbose
1 1 1
135.53.28.53:57771 -> 135.193.241.31:13724
135.53.28.53:57772 -> 135.193.241.31:13724
PEER_NAME = aspr.com
HOST_NAME = cni.com
CLIENT_NAME = cni.com
VERSION = 0x06500000
PLATFORM = nt
PATCH_VERSION =
SERVER_PATCH_VERSION =
135.53.28.53:64729 -> 135.193.241.31:13724

Zahid_Haseeb
Moderator
Moderator
Partner    VIP    Accredited

""""""  ConnectToBPCD(cniweb.gfiprod.att.com) failed: 25
cannot connect on socket  """"""

 

Ensure your commuication with bpcd

 
Status Code: 25
Cannot connect on socket
This error occurs when a Netbackup process times out while attempting to connect to another
Netbackup process. A Status 25 can occur when a NetBackup process tries to connect to the
NetBackup Request daemon (bprd) or NetBackup Database Manager daemon (bpdbm) on the
Master Server and that daemon is not running. This error can also occur if a network or server
has slow response time or resource issues. The initial goal of troubleshooting this issue should
be to identify which machines are involved with the failure. For example, if the failure always
involves the same Client or Media Server, this is where to concentrate efforts. Once this failure
point is identified, then further troubleshooting can be done to identify the specific cause. The
most common causes are discussed in this document.
 
Command syntax:
telnet <server name or IP address> bpcd
 
Successful telnet output example from UNIX:
# telnet <server name> bpcd
Trying 10.10.100.20...
Connected to <server name>.
Escape character is '^]'.
Hit the “Ctrl” ] and then type quit to end
 
Unsuccessful telnet output example from UNIX:
# telnet <server name> bpcd
Trying 10.10.100.20...
telnet: Unable to connect to remote host: Connection refused
 
Firewall
If a firewall is present in the configuration, it will be necessary to open port ranges for
proper communication, or utilize the NetBackup vnetd daemon to lessen the amount of
ports being used. See the NetBackup System Administrator’s Guide for more details on
this.
 
Name Resolution
UNIX command location: /usr/openv/netbackup/bin
Switches and variations:
bpclntcmd -pn
bpclntcmd -self
bpclntcmd -hn <hostname_of_master server, media server, or client>
bpclntcmd -ip <ip_of_master server, media server, or client>
 
The goal of these commands is to make sure the hostname is seen the same way after
each command with no errors.
 
 
The above are the extracts of some more important checks from below Symantec document. See the below Symantec document for status code 25 for more details.
This may help you hopefully
 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Please post client's bpcd log file. We need to see what happened on the client's side.

Deepshikha_Koth
Level 2

Hi RooKie,

12:24:13.322 [29149] <16> bptestbpcd main: Function bpcr_new_standard_socket_rqst(135.193.241.31) failed: 24

MEDIA SERVER LOGS:

 

10:32:28.440 [8349] <2> ConnectToBPCD: bpcd_connect_and_verify(135.193.241.31, 135.193.241.31) failed: 25
<16>bptestbpcd main: Function ConnectToBPCD(135.193.241.31) failed: 25
10:32:28.441 [8349] <16> bptestbpcd main: Function ConnectToBPCD(135.193.241.31) failed: 25
<2>bptestbpcd: cannot connect on socket
10:32:28.441 [8349] <2> bptestbpcd: cannot connect on socket
<2>bptestbpcd: EXIT status = 25
10:32:28.441 [8349] <2> bptestbpcd: EXIT status = 25
cannot connect on socket

 

Clearly indicates that there is a problem with the Network connectivity between Media to Client.

To Confirm you can on the master/media server :

Go to Netbackup Admin Console>Host properties> clients and try to connect the client from there and check what error you get over there.

You can few steps :

1> Into the C:\Windows\System32\Drivers\Etc\Hosts

Open this Hosts into a notepad\wordpad and edit it.

Enter the IP Address of the master server hostname of the master server FQDN of the master server

Also add the same entries into the same format of the Media server.

Save and close the file.

Restart the Netbackup Client Service on the Client.

Check still if the issue persists.

Hope this helpsss..!!

Deepshikha