Jukka Salmi --> amanda-users (2008-09-05 14:51:31 +0200):
> Hello,
> 
> I'm trying to add a NetBSD system running Amanda 2.5.2p1 as a backup
> client to an existing backup server running Amanda 2.4.4p3 on Linux.
> 
> Running amcheck(8) shows no problems, and both the `noop' and `sendsize'
> stages during an amdump(8) run seem to be fine. But then, during the
> `sendbackup' stage, some strange connection problem occurs: running
> amstatus(8) on the server shows lines like
> 
>   myclient:/  0  27800k wait for dumping driver: (aborted:[request timeout])
> 
> for all disk from that new client, and the Amanda mail report contains
> lines like
> 
>   myclient / lev 0 FAILED 20080904[could not connect to myclient]
> 
> for all of those. On the client system, syslogd receives several
> messages about
> 
>   sendbackup[n]: index tee cannot write [Broken pipe]
> 
> during the amdump run.
> 
> Both hosts involved are connected to the same IP subnet, without any
> packet filtering done in between.
> 
> 
> Any hint about what could be the problem here?

Sniffing network traffic between the Amanda server and client shows
this (s:n is server port n, c:n is client port n):

s:851 -> c:10080 udp Amanda 2.4 REQ HANDLE ... SERVICE noop ...
c:10080 -> s:851 udp Amanda 2.5 ACK HANDLE ...
s:851 -> c:10080 udp Amanda 2.4 REP HANDLE ...
c:10080 -> s:851 udp Amanda 2.5 ACK HANDLE ...
s:851 -> c:10080 udp Amanda 2.4 REQ HANDLE ... SERVICE selfcheck ...
c:10080 -> s:851 udp Amanda 2.5 ACK HANDLE ...
c:10080 -> s:851 udp Amanda 2.5 REP HANDLE ...
s:851 -> c:10080 udp Amanda 2.4 ACK HANDLE ...

s:846 -> c:10080 udp Amanda 2.4 REQ HANDLE ... SERVICE noop ...
c:10080 -> s:846 udp Amanda 2.5 ACK HANDLE ...
c:10080 -> s:846 udp Amanda 2.5 REP HANDLE ...
s:846 -> c:10080 udp Amanda 2.4 ACK HANDLE ...
s:846 -> c:10080 udp Amanda 2.4 REQ HANDLE ... SERVICE sendsize ...
c:10080 -> s:846 udp Amanda 2.5 ACK HANDLE ...
c:10080 -> s:846 udp Amanda 2.5 REP HANDLE ...
s:846 -> c:10080 udp Amanda 2.4 ACK HANDLE ...
s:846 -> c:10080 udp Amanda 2.4 REQ HANDLE ... SERVICE sendbackup ...
c:10080 -> s:846 udp Amanda 2.5 ACK HANDLE ...
c:10080 -> s:846 udp Amanda 2.5 REP HANDLE ... CONNECT DATA 56639 MESG 56638 
INDEX 56637 ...
s:846 -> c:10080 udp Amanda 2.4 ACK HANDLE ...

s:50029 -> c:56639 tcp SYN
c:56639 -> s:50029 tcp SYN,RST

Oops. IIUC this TCP connection is supposd to transfer the actual data
to back up. Hmm, why could it be reset by the client?

TIA, Jukka

-- 
bashian roulette:
$ ((RANDOM%6)) || rm -rf ~