Brian Bruns wrote:
Here is, I think, the relevant log file from the client machine:
[EMAIL PROTECTED] DailySet1]# tail sendbackup.20080808140957.debug
sendbackup-gnutar: time 0.001: pid 8298: /bin/gzip --fast
sendbackup-gnutar: time 0.002: doing level 0 dump as
listed-incremental to '/var/lib/amanda/gnutar-lists/web3_etc_0.new'
sendbackup-gnutar: time 0.003: doing level 0 dump from date:
1970-01-01 0:00:00 GMT
sendbackup: time 0.006: spawning /usr/lib/amanda/runtar in pipeline
sendbackup: time 0.006: argument list: runtar DailySet1 gtar --create
--file - --directory /etc --one-file-system --listed-incremental
/var/lib/amanda/gnutar-lists/web3_etc_0.new --sparse --xattrs
--ignore-failed-read --totals .
sendbackup: time 0.006: started index creator: "/bin/tar -tf -
2>/dev/null | sed -e 's/^\.//'"
sendbackup-gnutar: time 0.006: /usr/lib/amanda/runtar: pid 8301
sendbackup: time 0.006: started backup
sendbackup: time 90.005: index tee cannot write [Broken pipe]
sendbackup: time 90.005: pid 8299 finish time Fri Aug 8 14:11:27 2008
It's been a while since I had to debug an amanda problem and I have no
experience with Fedora...
Corresponding to sendbackup.debug file on the client, there should be a
dumper.debug file on the server, describing the server side view of
backing up this particular DLE. Maybe more clues can be found there.
90 seconds looks suspiciously like some kind of network timeout. Maybe a
firewall on the server (or between server and client) preventing packets
sent from the client reaching the server?
--
Toomas
... If you leave me, can i come too?
