Video Screencast Help

Status 58 = can't connect to client.

Created: 26 Aug 2013 • Updated: 16 Oct 2013 | 24 comments
This issue has been solved. See solution.

I'm getting the below error

Status = can't connect to client.

Client host properties shows cannot connect to socket.

How can we resolve?

 

Operating Systems:

Comments 24 CommentsJump to latest comment

revaroo's picture

Enable the bpcd log directory on the client under netbackup\logs\

 

Retry connecting, see if the log is populated, if it is post it up.

If it's not there could be a firewall blocking connectivity - check this out.

 

Also on the Master can you run:

bptestbpcd -client <clientname>

 

does that fail too?

SOLUTION
nesel's picture

Hi Sathisp83,

 

> Try ping test from your master/media server to client

> add client IP address to your master/media host file

 

Hope this will help, please let us know the result

 

Thanks

Nate.D's picture

Is this a local device on the domain/network or is it a remote/satellite location? Are you backing up other client's properly or are you having issues across the board?

If I was helpful in solving your issue please mark my post with a thumbs up or a solution!  Have a great day :)

Marianne's picture

Please tell us all relevant info?

NBU version on master, media server and client

OS on master, media server and client

Hostname lookup in your environment - DNS or hosts files?
If DNS - is reverse lookup enabled?

Can client resolve master and/or media server IP address to hostname that corresponds with SERVER entry on the client?

Is there a firewall between client and master and/or media server?

Is there any firewall software on the client?

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Will Restore's picture

NetBackup Client software installed? 

Yes, just had one of those "oh, we forget to tell you ..."  indecision

Will Restore -- where there is a Will there is a way

Sathisp83@yahoo.com's picture

I'm sorry for tle late reply, back from my vacation.

Still facing issues for few clients with status 58.

Client software already installed and even i restarted the services, again its failing.

NBU version is 7.1.01

OS is Unix

Hostname lookup - hosts files

Connection to 172.24.129.47 13782 port [tcp/bpcd] succeeded!

Logs are below.

09/11/2013 22:20:36 - granted resource  CA5548
09/11/2013 22:20:36 - granted resource  HP.ULTRIUM3-SCSI.000
09/11/2013 22:20:36 - granted resource  kek3bkvnnp01-hcart3-robot-tld-0
09/11/2013 22:20:36 - estimated 0 kbytes needed
09/11/2013 22:20:36 - begin Parent Job
09/11/2013 22:20:36 - begin Snapshot: Start Notify Script
09/11/2013 22:20:36 - Info RUNCMD (pid=2808) started
09/11/2013 22:20:36 - Info RUNCMD (pid=2808) exiting with status: 0
Operation Status: 0
09/11/2013 22:20:36 - end Snapshot: Start Notify Script; elapsed time 0:00:00
09/11/2013 22:20:36 - begin Snapshot: Step By Condition
Operation Status: 0
09/11/2013 22:20:36 - end Snapshot: Step By Condition; elapsed time 0:00:00
09/11/2013 22:20:36 - begin Snapshot: Stream Discovery
Operation Status: 0
09/11/2013 22:20:36 - end Snapshot: Stream Discovery; elapsed time 0:00:00
09/11/2013 22:20:36 - begin Snapshot: Read File List
Operation Status: 0
09/11/2013 22:20:36 - end Snapshot: Read File List; elapsed time 0:00:00
09/11/2013 22:20:36 - begin Snapshot: Create Snapshot
09/11/2013 22:20:37 - started process bpbrm (pid=924)
09/11/2013 22:24:13 - Error bpbrm (pid=924) Cannot connect to 172.24.131.244
09/11/2013 22:24:13 - end writing
Operation Status: 58
09/11/2013 22:24:13 - end Snapshot: Create Snapshot; elapsed time 0:03:37
09/11/2013 22:24:13 - begin Snapshot: Stop On Error
Operation Status: 0
09/11/2013 22:24:13 - end Snapshot: Stop On Error; elapsed time 0:00:00
09/11/2013 22:24:13 - begin Snapshot: Delete Snapshot On Exit
Operation Status: 0
09/11/2013 22:24:13 - end Snapshot: Delete Snapshot On Exit; elapsed time 0:00:00
09/11/2013 22:24:13 - begin Snapshot: End Notify Script
09/11/2013 22:24:13 - Info RUNCMD (pid=9284) started
09/11/2013 22:24:13 - Info RUNCMD (pid=9284) exiting with status: 0
Operation Status: 0
09/11/2013 22:24:13 - end Snapshot: End Notify Script; elapsed time 0:00:00
Operation Status: 58
09/11/2013 22:24:13 - end Parent Job; elapsed time 0:03:37
09/11/2013 22:24:18 - Info bpbkar32 (pid=0) done. status: 58: can't connect to client
can't connect to client  (58)
 

Marianne's picture

NBU version is 7.1.0.1 will first attempt connection on port 1556, then 13724. Client needs to connect back on same port.

Please do the following test:

Create bpcd log folder on the client. 

Use hostnames to test - not IP addresses (Your policy seems to be using IP address 172.24.131.244 and not client hostname). 
If you are using hosts files, you should have entries in /etc/hosts for clients on the server, and hosts entries on the client for master and media server(s).

On server kek3bkvnnp01, do the following:

ping <client-name>

bptestbpcd -client <client-name> -verbose -debug

Please post output of above 2 commands as well as bpcd log file on the client.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Sathisp83@yahoo.com's picture

Pinging DAVXAPNGNU01.ascorp.com [172.26.146.39] with 32 bytes of data:

Reply from 172.26.146.39: bytes=32 time=41ms TTL=57
Reply from 172.26.146.39: bytes=32 time=41ms TTL=57
Reply from 172.26.146.39: bytes=32 time=41ms TTL=57
Reply from 172.26.146.39: bytes=32 time=40ms TTL=57

06:19:56.065 [9884.12232] <2> bptestbpcd: VERBOSE = 0
06:20:26.097 [9884.12232] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.
1376: 0: getsockopt SO_ERROR returned: 10054 0x00002746
06:20:27.065 [9884.12232] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.
1376: 0: getsockopt SO_ERROR returned: 10054 0x00002746
06:20:37.019 [9884.12232] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.
1376: 0: getsockopt SO_ERROR returned: 10054 0x00002746
06:21:08.019 [9884.12232] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.
1376: 0: getsockopt SO_ERROR returned: 10054 0x00002746
06:21:08.957 [9884.12232] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.
1376: 0: getsockopt SO_ERROR returned: 10054 0x00002746
06:21:38.958 [9884.12232] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.
1376: 0: getsockopt SO_ERROR returned: 10054 0x00002746
06:21:40.958 [9884.12232] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.
1376: 0: getsockopt SO_ERROR returned: 10054 0x00002746
06:21:50.083 [9884.12232] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.
1376: 0: getsockopt SO_ERROR returned: 10054 0x00002746

Marianne's picture

Is that ALL of the bptestbpcd output? I was expecting to see the port number and IP address that is used  to connect to the client.

Did you remember to create bpcd folder on the client?
Was any log created in bpcd folder?

If so, please post.

If not, check that firewall software on client is disabled.
On Linux client, stop and disable iptables.
On Windows client, disable Windows firewall.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Marianne's picture

On vacation again? indecision

About 4 weeks have passed with no backups for this client? 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

rino19ny's picture

LOL maybe on vacation again...

make simple test. from client ping your server, then from server ping your client. use ip addresses first for both. if that succeeds, use hostnames to ping to. now if THAT fails, you know where the problem is.

 

rk1074's picture

chk  for the correct entry of the media server in the bp.conf file of the client as well

Jaime_Vazquez's picture

On the client:

bpclntcmd -self

This should display who the client 'sees' as hist Master ("expecting response from ...") followed by the client information, as known by the Master itself.  Odds are this fails if all else in this thread is correct.

For me, it was almost always a firewall setting on the client. Disable the firewall on the client and retry to verify.

rino19ny's picture
"getsockopt SO_ERROR returned: 10054"
 
 
WSAECONNRESET
10054
 
"Connection reset by peer.

An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close.."

 

something is dropping the established connection. we can rule out the firewall. see if your antivirus/IDS is getting in the way.

ontherocks's picture

Hi Sathisp83,

Follow this :-

from the Administration Console:
1. Launch the NetBackup Administration Console, connecting to the master server
2. Expand Host Properties in the left pane
3. Select Master Server in the left pane
4. Click the name of the master server in the right pane
5. Select the Client Attributes section
6. Add the name of the client in question if it isn't listed
7. In the Connect Options tab for the client, make the following changes:
BPCD connect back -> "Random port"
Ports ->  "Reserved port"
Daemon connection port -> "Daemon port only"

Note: You DO NOT have to stop and restart when making changes to the master server client attribute tab. Just simply click apply and okay to commit those changes.

 

Let us know the results.....

OTR

Sathisp83@yahoo.com's picture

Ontherocks,

Pls find the below logs after making that port changes.

10/12/2013 08:27:07 - Info nbjm (pid=8748) starting backup job (jobid=487590) for client 172.26.146.39, policy DAVXAPNGNU01-APPDYNM-PROD-H, schedule WEEKLY-FULL
10/12/2013 08:27:08 - estimated 0 kbytes needed
10/12/2013 08:27:08 - Info nbjm (pid=8748) started backup job for client 172.26.146.39, policy DAVXAPNGNU01-APPDYNM-PROD-H, schedule WEEKLY-FULL on storage unit dak8bkasnp01-hcart-robot-tld-4
10/12/2013 08:27:09 - Info bpbrm (pid=5232) starting bptm
10/12/2013 08:27:09 - started process bpbrm (pid=5232)
10/12/2013 08:27:10 - Info bpbrm (pid=5232) Started media manager using bpcd successfully
10/12/2013 08:27:11 - Info bpbrm (pid=5232) 172.26.146.39 is the host to backup data from
10/12/2013 08:27:11 - Info bpbrm (pid=5232) telling media manager to start backup on client
10/12/2013 08:27:11 - Info bptm (pid=5784) using 65536 data buffer size
10/12/2013 08:27:12 - Info bptm (pid=5784) using 12 data buffers
10/12/2013 08:27:13 - Info bptm (pid=5784) start backup
10/12/2013 08:27:13 - Info bptm (pid=5784) Waiting for mount of media id DA0024 (copy 1) on server dak8bkasnp01.ascorp.com.
10/12/2013 08:27:13 - mounting DA0024
10/12/2013 08:28:03 - Info bptm (pid=5784) media id DA0024 mounted on drive index 9, drivepath {3,0,4,0}, drivename HP.ULTRIUM5-SCSI.009, copy 1
10/12/2013 08:28:03 - mounted DA0024; mount time: 0:00:50
10/12/2013 08:28:11 - positioning DA0024 to file 1
10/12/2013 08:32:21 - Error bpbrm (pid=6644) cannot connect to 172.26.146.39, status = 25
10/12/2013 08:32:21 - Info bpbrm (pid=6644) sending bpsched msg: CONNECTING TO CLIENT FOR 172.26.146.39_1381580828
10/12/2013 08:32:22 - connecting
10/12/2013 08:33:18 - Error bptm (pid=6204) cannot create data socket, 0
10/12/2013 08:37:28 - Error bpbrm (pid=6644) Cannot connect to 172.26.146.39
10/12/2013 08:37:28 - Info bpbrm (pid=5232) child done, status 58
10/12/2013 08:37:28 - Info bpbrm (pid=5232) sending media manager msg: STOP BACKUP 172.26.146.39_1381580828
10/12/2013 08:37:42 - Info bpbrm (pid=5232) media manager for backup id 172.26.146.39_1381580828 exited with status 150: termination requested by administrator
10/12/2013 08:37:42 - end writing
10/12/2013 08:37:44 - Info bpbrm (pid=5232) sending media manager msg: TERMINATE
can't connect to client  (58)
 

Sathisp83@yahoo.com's picture

ontherocks,

 

Chnaged the settings.  but failed again.

10/12/2013 08:32:22 - connecting
10/12/2013 08:33:18 - Error bptm (pid=6204) cannot create data socket, 0
10/12/2013 08:37:28 - Error bpbrm (pid=6644) Cannot connect to 172.26.146.39
10/12/2013 08:37:28 - Info bpbrm (pid=5232) child done, status 58
10/12/2013 08:37:28 - Info bpbrm (pid=5232) sending media manager msg: STOP BACKUP 172.26.146.39_1381580828
10/12/2013 08:37:42 - Info bpbrm (pid=5232) media manager for backup id 172.26.146.39_1381580828 exited with status 150: termination requested by administrator
10/12/2013 08:37:42 - end writing
10/12/2013 08:37:44 - Info bpbrm (pid=5232) sending media manager msg: TERMINATE
can't connect to client  (58)

Marianne's picture

Please go through my previous post (12 Sept) again:

https://www-secure.symantec.com/connect/forums/status-58-cant-connect-client-0#comment-9217181

I have also listed steps to take in this post:

https://www-secure.symantec.com/connect/forums/status-58-cant-connect-client-0#comment-9216821

Why are you using IP address and not hostname?

NBU works with hostnames. 

If you are not using DNS in your environment, add hosts entries for the client on the master and media server.
On the client, add hosts entries for the master and media servers.
These hosts entries must match the SERVER entries on the client.

PLEASE test as per my previous 2 posts.

Post bpcd log on client.
If nothing is logged, you have a firewall problem. Either company firewall or OS firewall on the client.

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Sathisp83@yahoo.com's picture

Marianne,

changed the ip to host name, failed again.

Checked for Master and Media server entry in client side, it was wrong. changed but again failed with same error.

restarted the client services, again failed.

Now waiting for an answer from my SOC team about the below port status. Whether it is enabled or not. 

bpcd 13782/tcp bpcd

vnetd 13724/tcp vnetd

Will keeep you posted. Thanks for your direction.

FYI. I couldn't get the bpcd logs.

Marianne's picture

Please help me understand what this means:

FYI. I couldn't get the bpcd logs.

Does bpcd log folder exist on the client?

If it does and no log is created, there is a firewall problem (as per my previous post).

NBU 6.x up to NBU 7.0 only needs vnetd (13724) to be open bi-directional between server and client.

As from NBU 7.0.1, NBU will first try port 1556 (pbx). If that fails, it will try 13724 (vnetd).

See NetBackup 6.x and 7.x firewall port requirements: http://www.symantec.com/docs/TECH136090

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Sathisp83@yahoo.com's picture

Marianne,

Yes. It was a firewall problem. Now the port has been opened and backup started running. Thanks for your support. 

Marianne's picture

Glad issue is resolved.

revaroo was first to mention firewall - please mark his post as Solution.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links