Amanda-Users

Re: Timeout waiting for ack after adding dle

2009-03-01 03:50:52
Subject: Re: Timeout waiting for ack after adding dle
From: Toomas Aas <toomas.aas AT raad.tartu DOT ee>
To: amanda-users AT amanda DOT org
Date: Sun, 1 Mar 2009 10:13:26 +0200
Sunday 01 March 2009 04:59:54 kirjutasid sa:

> Toomas Aas wrote at 11:04 +0200 on Feb 28, 2009:

>  > I have a single-machine (client==server) setup which has been working
>  > well for quite a long time. It's running Amanda 2.5.1p3 on FreeBSD 6.4.
>  >
>  > Yesterday I added a new disk to the machine, mounted it under /db and
>  > added corresponding entry to the disklist. On tonights backup run,
>  > Amanda backed up  first two small DLEs but all the rest (including the
>  > newly added one) failed with:
>  >
>  > host.domain.ee  /usr lev 1  FAILED [cannot read header: got 0 instead
>  > of 32768]
>  > host.domain.ee  /usr lev 1  FAILED [cannot read header: got 0 instead
>  > of 32768]
>  > host.domain.ee  /usr lev 1  FAILED [too many dumper retry: "[request
>  > failed: timeout waiting for ACK]"]

>
> sendbackup is dying early - possible your timeouts are set too low
> in amanda.conf.
>
> Is this new DLE big?  Lots of files?

The new DLE is not that big. Its 'raw capacity' is 21 GB, ca 25000 files, but 
most of it are MySQL and PostgreSQL database files which are excluded from 
the DLE.

> It's also possible you're hitting a udp datagram size limit.  This can
> be improved with a sysctl tweak, or a source patch or using tcp
> (sorry - don't recall if amanda 2.5.1 supports the latter).

Thanks for the idea, I'll increase the net.inet.udp.maxdgram sysctl. 

I also looked at sendbackup debug files on the client, but the only error 
there is the same 'index tee cannot write [Broken pipe]':

sendbackup: debug 1 pid 11508 ruid 3951 euid 3951: start at Sat Feb 28 
04:06:23 2009
sendbackup: version 2.5.1p3
Could not open conf file "/usr/local/etc/amanda/amanda-client.conf": No such 
file or directory
Reading conf file "/usr/local/etc/amanda/BACKUP/amanda-client.conf".
sendbackup: debug 1 pid 11508 ruid 3951 euid 3951: rename at Sat Feb 28 
04:06:23 2009
  sendbackup req: <GNUTAR /db  0 1970:1:1:0:0:0 
OPTIONS 
|;auth=BSD;compress-fast;index;exclude-file=./mysql;exclude-file=./pgsql/base;>
  parsed request as: program `GNUTAR'
                     disk `/db'
                     device `/db'
                     level 0
                     since 1970:1:1:0:0:0
                     options 
`|;auth=BSD;compress-fast;index;exclude-file=./mysql;exclude-file=./pgsql/base;'
sendbackup: start: host.domain.ee:/db lev 0
sendbackup: time 0.000: spawning /usr/bin/gzip in pipeline
sendbackup: argument list: /usr/bin/gzip --fast
sendbackup-gnutar: time 0.000: pid 11510: /usr/bin/gzip --fast
sendbackup-gnutar: time 0.001: doing level 0 dump as listed-incremental 
to '/var/amanda/gnutar-lists/host.domain.ee_db_0.new'
sendbackup-gnutar: time 0.011: doing level 0 dump from date: 1970-01-01  
0:00:00 GMT
sendbackup: time 0.012: spawning /usr/local/libexec/amanda/runtar in pipeline
sendbackup: argument list: runtar BACKUP 
GNUTAR --create --file - --directory /db --one-file-system --listed-incremental 
/var/amanda/gnutar-lists/host.domain.ee_db_0.new --sparse --ignore-failed-read 
--totals --exclude-from /tmp/amanda/sendbackup._db.20090228040623.exclude .
sendbackup-gnutar: time 0.012: /usr/local/libexec/amanda/runtar: pid 11512
sendbackup: time 0.012: started backup
sendbackup: time 0.014: started index creator: "/usr/local/bin/gtar -tf - 
2>/dev/null | sed -e 's/^\.//'"
sendbackup: time 469.114: index tee cannot write [Broken pipe]
sendbackup: time 469.114: pid 11511 finish time Sat Feb 28 04:14:12 2009

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