I've suddenly (after adding some new partitons to backup to an exisitng
config), started getting data timeouts on machines that _were working. I'm
enclosing the endbackup debug file below to help in diagnoses.

Any sugestions?


sendbackup: debug 1 pid 12392 ruid 1001 euid 1001: start at Tue Feb 24 00:59:30 
2004
/usr/local/amanda/libexec/sendbackup: version 2.4.3b4
  parsed request as: program `GNUTAR'
                     disk `hda2'
                     device `hda2'
                     level 1
                     since 2004:2:13:5:57:8
                     options 
`|;auth=bsd;compress-best;index;exclude-list=/usr/local/lib/amanda/exclude.gtar;'
sendbackup: try_socksize: send buffer size is 65536
sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.36812
sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.36813
sendbackup: time 0.000: stream_server: waiting for connection: 0.0.0.0.36814
sendbackup: time 0.000: waiting for connect on 36812, then 36813, then 36814
sendbackup: time 0.004: stream_accept: connection from 205.159.77.224.4091
sendbackup: time 0.006: stream_accept: connection from 205.159.77.224.4092
sendbackup: time 0.007: stream_accept: connection from 205.159.77.224.4093
sendbackup: time 0.007: got all connections
sendbackup: time 0.007: spawning /bin/gzip in pipeline
sendbackup: argument list: /bin/gzip --best
sendbackup-gnutar: time 0.007: pid 12394: /bin/gzip --best
sendbackup-gnutar: time 0.655: doing level 1 dump as listed-incremental from 
/usr/local/amanda/var/amanda/gnutar-lists/smokeyhda2_0 to 
/usr/local/amanda/var/amanda/gnutar-lists/smokeyhda2_1.new
sendbackup-gnutar: time 0.681: doing level 1 dump from date: 2004-02-13  
5:57:09 GMT
sendbackup: time 0.684: started index creator: "/bin/tar -tf - 2>/dev/null | 
sed -e 's/^\.//'"
sendbackup: time 0.685: spawning /usr/local/amanda/libexec/runtar in pipeline
sendbackup: argument list: gtar --create --file - --directory / 
--one-file-system --listed-incremental 
/usr/local/amanda/var/amanda/gnutar-lists/smokeyhda2_1.new --sparse 
--ignore-failed-read --totals --exclude-from 
/tmp/amanda/sendbackup.hda2.20040224005931.exclude .
sendbackup-gnutar: time 0.685: /usr/local/amanda/libexec/runtar: pid 12397
sendbackup: time 782.610: index tee cannot write [Broken pipe]
sendbackup: time 782.674: pid 12395 finish time Tue Feb 24 01:12:33 2004
sendbackup: time 782.702: 124: strange(?): 
sendbackup: time 782.766: 124: strange(?): gzip: stdout: Connection reset by 
peer
sendbackup: time 782.766: 124: strange(?): sendbackup: index tee cannot write 
[Broken pipe]
sendbackup: time 782.866: error [/bin/tar got signal 13, compress returned 1]
sendbackup: time 782.866: pid 12392 finish time Tue Feb 24 01:12:33 2004

It seems as though something killed the tar process too soon, is this
possible?

-- 
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
                                                -- Benjamin Franklin