Video Screencast Help

Backup fails with status 58, connection refused msg

Created: 12 Dec 2012 • Updated: 02 Jan 2013 | 7 comments
This issue has been solved. See solution.

I have a UNIX client that is getting a status 58 error, but the job detail contains messages I have never run across before with a 58 regarding a refused connection (see bolded text below). Master and media servers are running 7.5.0.4 not sure about the client version at this time. Backups had been working fine, then just stopped one day.

12/11/2012 21:00:00 - Info nbjm (pid=1608) starting backup job (jobid=3564781) for client bkmisedig, policy MIS-FF-Edi, schedule DIfferential
12/11/2012 21:00:00 - Info nbjm (pid=1608) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=3564781, request id:{A2DA016E-43FF-11E2-88AA-1CC1DE1EF662})
12/11/2012 21:00:00 - requesting resource EDSSU-SHARED-FS
12/11/2012 21:00:00 - requesting resource bkferrari.NBU_CLIENT.MAXJOBS.bkmisedig
12/11/2012 21:00:00 - requesting resource bkferrari.NBU_POLICY.MAXJOBS.MIS-FF-Edi
12/11/2012 21:00:12 - granted resource  bkferrari.NBU_CLIENT.MAXJOBS.bkmisedig
12/11/2012 21:00:12 - granted resource  bkferrari.NBU_POLICY.MAXJOBS.MIS-FF-Edi
12/11/2012 21:00:12 - granted resource  MediaID=@aaabv;Path=/EDSSU/SHARED/FS;MediaServer=bkbugatti
12/11/2012 21:00:12 - granted resource  EDSSU-SHARED-FS
12/11/2012 21:00:14 - estimated 8864563 kbytes needed
12/11/2012 21:00:14 - Info nbjm (pid=1608) started backup (backupid=bkmisedig_1355277613) job for client bkmisedig, policy MIS-FF-Edi, schedule DIfferential on storage unit EDSSU-SHARED-FS
12/11/2012 21:00:19 - started process bpbrm (pid=11816)
12/11/2012 21:17:11 - end writing
12/11/2012 21:17:53 - Info bpbrm (pid=11816) connect failed STATUS (18) CONNECT_FAILED
12/11/2012 21:17:53 - Info bpbrm (pid=11816)  status: FAILED, (42) CONNECT_REFUSED; system: (145) Connection timed out; FROM 0.0.0.0 TO bkmisedig 10.87.17.156 bpcd VIA pbx
12/11/2012 21:17:53 - Info bpbrm (pid=11816)  status: FAILED, (42) CONNECT_REFUSED; system: (145) Connection timed out; FROM 0.0.0.0 TO bkmisedig 10.87.17.156 bpcd VIA vnetd
12/11/2012 21:17:53 - Info bpbrm (pid=11816)  status: FAILED, (42) CONNECT_REFUSED; system: (145) Connection timed out; FROM 0.0.0.0 TO bkmisedig 10.87.17.156 bpcd

12/11/2012 21:17:53 - Error bpbrm (pid=11816) Cannot connect to bkmisedig
12/11/2012 21:17:53 - Info bpbkar (pid=0) done. status: 58: can't connect to client
can't connect to client  (58)

I thought with it being a status 58, it was just a loss of connection, but what does the detail about the CONNECT_REFUSED mean, and how would I troubleshoot it? Is it more than just not having a network connection to the client?

Thanks,

Wayne

Discussion Filed Under:

Comments 7 CommentsJump to latest comment

Nagalla's picture

hi,

did you see if pbx (if client is 7.X) or bpcd ,vnetd are connecting from master and media servers?

telnet <clientname> 1556

telnet <clientname> 13782

telnet <clientname>13724

bptestbpcd -client <clientname> -verbose -debug

output please..

and also

did you see Connection timed out; FROM 0.0.0.0 TO bkmisedig 10.87.17.156 bpcd VIA pbx.

its showing IP as 0.0.0.0,  does it have good name resolutions

you can check with bpclntcmd command.. 

1) you need to check if those ports are open on client end or not

2) does client is resolving proper for master and media servers and also master and media servers for cllient

3)did client bp.conf have the correct entiries.

4)how about the route(if client have multiple interfaces)

 

Marianne's picture

Any chance Client's IP address has changed?

Or client software removed? 

Firewall between server and client?
Or 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

revaroo's picture

12/11/2012 21:17:53 - Info bpbrm (pid=11816)  status: FAILED, (42) CONNECT_REFUSED; system: (145) Connection timed out; FROM 0.0.0.0 TO bkmisedig 10.87.17.156 bpcd VIA pbx

Looks like the connection is coming from IP 0.0.0.0 on the media server - is that correct? Doesn't look right to me. What does your hosts file look like.

Basically a connection is not being made to the client. it times out  connecting to PVX, then vnetd then bpcd.

 

What does: bptestbpcd -client bkmisedig -verbose -debug  show?

On the media server: bpclntcmd -self    &     bpclntcmd -pn

 

 

Marianne's picture

The '0.0.0.0' is a red herring...

As a test, I have added hosts entry with incorrect IP address for my laptop on our lab server.

Result is the same as seen above:

 

.....
10:31:23.374 [31160] <16> connect_to_service: connect failed STATUS (18) CONNECT_FAILED
        status: FAILED, (44) CONNECT_TIMEOUT; system: (115) Operation now in progress; FROM 0.0.0.0 TO Marianne-Win7 10.1.1.110                       bpcd VIA pbx
        status: FAILED, (44) CONNECT_TIMEOUT; system: (115) Operation now in progress; FROM 0.0.0.0 TO Marianne-Win7 10.1.1.110                       bpcd VIA vnetd
        status: FAILED, (44) CONNECT_TIMEOUT; system: (115) Operation now in progress; FROM 0.0.0.0 TO Marianne-Win7 10.1.1.110                       bpcd
10:31:23.374 [31160] <8> vnet_connect_to_bpcd: [vnet_connect.c:279] connect_to_service() failed 18 0x12
10:31:23.374 [31160] <2> local_bpcr_connect: Can't connect to client Marianne-Win7
.....
 

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

WayneLackey's picture

Problem resolved - the network cable had come loose from the NIC.

SOLUTION
revaroo's picture

I guess a simple ping would've showed this up.

Marianne's picture

Seems my hunch was right that 'something' has changed on the Client! wink

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