I found the following in a sendbackup.debug logfile:
=============================================
sendbackup: debug 1 pid 10171 ruid 2 euid 2 start time Wed Jul 17
23:41:15 2002
/usr/local/libexec/sendbackup: version 2.4.2p2
sendbackup: got input request: GNUTAR /cs/turing/facstaff1 0
1970:1:1:0:0:0 OPTIONS |;bsd-auth;compress-fast;index;
parsed request as: program `GNUTAR'
disk `/cs/turing/facstaff1'
lev 0
since 1970:1:1:0:0:0
opt `|;bsd-auth;compress-fast;index;'
sendbackup: try_socksize: send buffer size is 65536
sendbackup: stream_server: waiting for connection: 0.0.0.0.32746
sendbackup: stream_server: waiting for connection: 0.0.0.0.32747
sendbackup: stream_server: waiting for connection: 0.0.0.0.32748
waiting for connect on 32746, then 32747, then 32748
sendbackup: stream_accept: connection from 129.15.78.240.32703
sendbackup: stream_accept: connection from 129.15.78.240.32704
sendbackup: stream_accept: connection from 129.15.78.240.32705
got all connections
sendbackup: spawning /usr/local/bin/gzip in pipeline
sendbackup: argument list: /usr/local/bin/gzip --fast
sendbackup-gnutar: pid 10172: /usr/local/bin/gzip --fast
sendbackup-gnutar: doing level 0 dump as listed-incremental to
/usr/local/var/amanda/gnutar-lists/turing_cs_turing_facstaff1_0
.new
sendbackup-gnutar: doing level 0 dump from date: 1970-01-01 0:00:00 GMT
sendbackup: spawning /usr/local/libexec/runtar in pipeline
sendbackup: argument list: gtar --create --file - --directory
/cs/turing/facstaff1 --one-file-system --listed-incremental /usr
/local/var/amanda/gnutar-lists/turing_cs_turing_facstaff1_0.new --sparse
--ignore-failed-read --totals .
sendbackup-gnutar: /usr/local/libexec/runtar: pid 10174
sendbackup: started index creator: "/usr/local/bin/tar -tf - 2>/dev/null
| sed -e 's/^\.//'"
index tee cannot write [Broken pipe]
sendbackup: pid 10173 finish time Thu Jul 18 00:47:48 2002
error [compress returned 1, /usr/local/bin/tar got signal 13]
sendbackup: pid 10171 finish time Thu Jul 18 00:47:48 2002
=============================================
I am not sure about the index tee. Is this just breaking because it has
exceeded the dtimeout value?
Any ideas would be greatly appreciated.
Thanks in advance,
Jim
Amanda version: 2.4.2p3
Tape Server: RH Linux 7.3
Client with problem: Solaris 8
Tape Drive: Sony TSL-9000 DDS3
During an amdump I am having one of my filesystems fail with the
infamous [data timeout] [dump to tape failed]. It has worked before.
I am at a loss on this one since other fs's from this client work
perfectly. One error was spotted in amdump.1 logfile, but I am unable
to diagnose:
driver: result time 11582.043 from dumper0: FAILED 01-00024 [data
timeout] taper: reader-side: got label daily01 filenum
12 driver: result time 11582.043 from
taper: DONE 00-00023 daily01 12 [sec 5848.423 kb 2566272 kps 438.8 {wr:
writers 80196 rdwait 3347.984 wrwait 2497.376 filemark
2.070}] driver:
error time 11582.075 serial gen mismatch driver: state
time 11582.075 free kps: 76400 space: 2048000 taper: idle idle-dumpers: 16 qlen tapeq:
0 runq: 0 roomq: 0 wakeup: 86400 driver-idle: not-idle driver: interface-state
time 11582.075 if : free 75000 if LE0: free 400 if LOCAL: free 1000
driver: hdisk-state time 11582.075
hdisk 0: free 2048000 dumpers 0 driver: QUITTING time 11582.075 telling
children to quit
And a snip from the mail report:
FAILED AND STRANGE DUMP DETAILS:
/-- turing /cs/turing/facstaff1 lev 0 FAILED [data timeout]
sendbackup: start [turing:/cs/turing/facstaff1 level 0]
sendbackup: info BACKUP=/usr/local/bin/tar
sendbackup: info RECOVER_CMD=/usr/local/bin/gzip -dc |/usr/local/bin/tar
-f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
?
? gzip: stdout: Broken pipe
? sendbackup: index tee cannot write [Broken pipe]
? index returned 1
sendbackup: error [compress returned 1, /usr/local/bin/tar got signal
13]
\--------
Thanks,
Jim
