Veritas-bu

[Veritas-bu] network errors

2000-11-03 20:18:24
Subject: [Veritas-bu] network errors
From: Ravi Channavajhala ravi.channavajhala AT csfb DOT com
Date: Fri, 3 Nov 2000 20:18:24 -0500 (EST)
Hi All,

I am seeing a bunch of 41/54/57/59 errors from some of my NT clients
backing up to a Solaris Netbackup (3.2 GA) server.  Often times, I
see the backup start and while in the middle of backup it times out
with error 54.  I have upped teh CLIENT_CONNECT_TIMEOUT and
CLIENT_READ_TIMEOUT values in bp.conf to 1800 and extensively
trouble shooted the network.

My setup is one media server, with several NICs, and each NIC
was defined in the bp.conf eg.,

SERVER = bkup02
SERVER = bkup02-e0
SERVER = bkup02-f0

Enabled verbose (99) for logging.  Looking thru client's bpcd
shows that it connected to bkup02-f0, which is an interface
on the machine bkup02 and tries connecting to privilged ports
in the range of 600-900 and gives up after 20 tries with

09:22:11 [258] <2> bpcd main: connection refused for port 882, try again 
09:22:14 [258] <2> bpcd main: connection refused for port 883, try again
and so on...it tries a range of ports and gives up.  Before this stage,
it acutually tells me that

09:04:28 [258] <2> bpcd main: new fork cmd = <whatever>
               <2> bpcd main: got socket for input 224
                ....
                <2> bpcd main: got socket for output 204, lport=883 and so
on..

I upped the TCP timeout paramaters on the NT clients in the registry
and so on.  Ran snoop and etc., without any luck.  What is interesting
is sometimes the backup for the same client succeeds, and some times it
just plain and simple errors out with one of 41/54/57/59.  

Can someone give pointers to take the debugging and diagnosing this
to next level, beyond running 'bpclntcmd' from the client, verifying
the host name resolution, bp.conf etc.,  Thanks.

-ravi




<Prev in Thread] Current Thread [Next in Thread>