Veritas-bu

Re: [Veritas-bu] backup failing with status code 54 without vnetd orstatus code 58 with vnetd

2009-02-02 07:06:21
Subject: Re: [Veritas-bu] backup failing with status code 54 without vnetd orstatus code 58 with vnetd
From: Kenneth Hansen <Kenneth.Hansen AT atea DOT no>
To: "Jenner, Steven" <Steven.Jenner AT Intl.Telstra DOT com>, Marianne Van Den Berg <mvdberg AT stortech.co DOT za>, "Veritas-bu AT mailman.eng.auburn DOT edu" <Veritas-bu AT mailman.eng.auburn DOT edu>
Date: Mon, 2 Feb 2009 12:40:20 +0100

Hi,

 

Netbackup user DNS names for resolving Ip adresses.

Can you ping server and telent using DNS names?

 

Kennneth

 

 

From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Jenner, Steven
Sent: 1. februar 2009 21:13
To: Marianne Van Den Berg; Veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] backup failing with status code 54 without vnetd orstatus code 58 with vnetd

 

Hi Marianne,

 

The backup servers are running 5.1MP7 whilst the client is on 5.1.

 

The bpcd log output is as below with vnetd and without vnetd.

 

06:27:43.374 [2832.2608] <2> bpcd main: offset to GMT 0

06:27:43.374 [2832.2608] <2> bpcd main: Got socket for input 1052

06:27:43.452 [2832.2608] <2> logconnections: getsockname(1052) failed: 10038

06:27:43.468 [2832.2608] <16> bpcd setup_sockopts: setsockopt 1 failed: h_errno 10038

06:27:43.468 [2832.2608] <2> bpcd main: setup_sockopts complete

06:27:43.483 [2832.2608] <2> vauth_acceptor: ..\libvlibs\vauth_comm.c.326: Function failed: 17 0x00000011

06:27:43.483 [2832.2608] <16> bpcd main: authentication failed: 17

 

Yes using telnet via the media servers with the vnetd port works (see below)

 

root@sn251180 [/opt/openv/netbackup/bin]# telnet 172.17.60.18 vnetd

Trying 172.17.60.18...

Connected to 172.17.60.18.

Escape character is '^]'.

^]

 

Running the bpclntcmd from the client to both media servers is also successful.

 

As mentioned everything looks ok but the backup will not complete successfully.


From: Marianne Van Den Berg [mailto:mvdberg AT stortech.co DOT za]
Sent: 30 January 2009 21:35
To: Jenner, Steven
Subject: RE: [Veritas-bu] backup failing with status code 54 without vnetd orstatus code 58 with vnetd

 

Which NBU version?

What's in bpcd log on the client?

Have you tried to telnet from client to vnetd on media server(s)?
Have you tried bpclntcmd from client to media servers using -hn and -ip?

Regards

Marianne



-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu on behalf of Jenner, Steven
Sent: Fri 1/30/2009 7:48 PM
To: Veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] backup failing with status code 54 without vnetd orstatus code 58 with vnetd

Hi All,



I have added a new client server to my backup schedule and its backups
are failing with status code 54 (timed out connecting to client). I can
confirm the following on the client:



1.      The client can ping the master server and both media servers and
vice versa 



2.      Both client daemons are listening on the server (vnetd and bpcd)




3.      I can successfully telnet to the client from the master server
and both media servers via the bpcd port (though if I try unreserved
ports the connection fails) 



4. I get the expected results running the bpclntcmd command (see below)



bash-2.05# ./bpclntcmd -hn hachiman1.cust.mgmt.internal  host
hach1.cust.mgmt.internal: hach1.cust.mgmt.internal at  172.x.x.x
(0xac113c12)

      checkhname: aliases:



       C:\Program Files\VERITAS\NetBackup\bin>bpclntcmd -pn  expecting
response from server snxxxx.mgmt.internal  hach1.cust.mgmt.internal
hach1.cust.mgmt.internal 172.x.x.x.18 2339



 I have tried changing the client's config to use vnetd at which point
the backup still fails but with a status code 58 error instead.



 The customer's server is running a firewall (WatchGuard x750e core
running fireware 10) but they have confirmed that there is a rule
allowing all ports between the backups servers and the client server.



Any ideas what the issue could be?



Thanks in advance,



Steve.




______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
<Prev in Thread] Current Thread [Next in Thread>