On Wed, 2002-08-14 at 08:23, Joshua Baker-LePain wrote:
> On 14 Aug 2002 at 8:09am, Jim Summers wrote
> 
> > I am running Amanda 2.4.2p2 on a Redhat Linux 7.3 as my Amanda server. 
> > The clients are mostly Solaris.  I have been been backing up the server
> > and adding clients one at a time.  Everything was working well, one
> > server and two clients, then I added a third client.  Now I getting data
> > timeouts and index tee broken messages in my Amanda reports and in the
> > system log files.
> 
> >From which systems?  The actual error messages would be most helpful.
>From one of the working systems a Sun E250 Solaris 8 and from the newly
added system Sun Ultra10 Solaris 8.  I will send the amanda report when
I get the next one.
> 
> > I have perused the docs, FAQ, and the various log files that Amanda
> > generates and I not finding the clue to point me to the problem.  All I
> > keep seeing are the index tee messages, but not what is causing the
> > index tee messages to be generated.
> 
> Also send along the contents of /tmp/amanda/sendbackup*debug from the 
> failing clients.
The next snip is from a sendbackup on a failing client:
=============
sendbackup: debug 1 pid 6604 ruid 2 euid 2 start time Wed Aug 14
00:50:57 2002
/usr/local/libexec/sendbackup: version 2.4.2p2
sendbackup: got input request: GNUTAR /opt 0 1970:1:1:0:0:0 OPTIONS
|;bsd-auth;c
ompress-fast;index;
  parsed request as: program `GNUTAR'
                     disk `/opt'
                     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.32761
sendbackup: stream_server: waiting for connection: 0.0.0.0.32762
sendbackup: stream_server: waiting for connection: 0.0.0.0.32763
  waiting for connect on 32761, then 32762, then 32763
sendbackup: stream_accept: connection from 129.15.78.240.32729
sendbackup: stream_accept: connection from 129.15.78.240.32730
sendbackup: stream_accept: connection from 129.15.78.240.32731
  got all connections
sendbackup: spawning /usr/local/bin/gzip in pipeline
sendbackup: argument list: /usr/local/bin/gzip --fast
sendbackup-gnutar: pid 6605: /usr/local/bin/gzip --fast
sendbackup-gnutar: doing level 0 dump as listed-incremental to
/usr/local/var/am
anda/gnutar-lists/tarjan_opt_0.new
sendbackup-gnutar: doing level 0 dump from date: 1970-01-01  0:00:00 GMT
sendbackup: started index creator: "/usr/local/bin/tar -tf - 2>/dev/null
| sed -
e 's/^\.//'"
sendbackup: spawning /usr/local/libexec/runtar in pipeline
sendbackup: argument list: gtar --create --file - --directory /opt
--one-file-sy
stem --listed-incremental
/usr/local/var/amanda/gnutar-lists/tarjan_opt_0.new --
sparse --ignore-failed-read --totals .
sendbackup-gnutar: /usr/local/libexec/runtar: pid 6610
index tee cannot write [Broken pipe]
sendbackup: pid 6606 finish time Wed Aug 14 01:14:12 2002
error [/usr/local/bin/tar got signal 13, compress returned 1]
sendbackup: pid 6604 finish time Wed Aug 14 01:14:12 2002
~

=============

The following is from the runtar for that sendbackup:
====
runtar: debug 1 pid 6610 ruid 2 euid 0 start time Wed Aug 14 00:50:57
2002
gtar: version 2.4.2p2
running: /usr/local/bin/tar: gtar --create --file - --directory /opt
--one-file-
system --listed-incremental
/usr/local/var/amanda/gnutar-lists/tarjan_opt_0.new
--sparse --ignore-failed-read --totals .
~
=========

Next is an ls from the location where tarjan_opt_0.new file is located.
=============
root@turing:/usr/local/var/amanda/gnutar-lists> ls -al tarjan*
-rw-------   1 bin      bin        115202 Aug 13 01:14 tarjan_dbfiles_0
-rw-------   1 bin      bin        115202 Aug 14 02:57 tarjan_dbfiles_1
-rw-------   1 bin      bin           998 Aug 10 00:57 tarjan_dblogs_0
-rw-------   1 bin      bin           998 Aug 14 01:55 tarjan_dblogs_1
-rw-------   1 bin      bin          2095 Aug 13 00:57 tarjan_etc_0
-rw-------   1 bin      bin          2095 Aug 14 00:50 tarjan_etc_1
-rw-------   1 bin      bin        245708 Aug  9 01:08 tarjan_opt_0
-rw-------   1 bin      bin             0 Aug 14 00:50 tarjan_opt_0.new
-rw-------   1 bin      bin        245708 Aug 13 00:58 tarjan_opt_1
-rw-------   1 bin      bin             0 Aug 13 01:14
tarjan_usr_oracle_0.new
=============
Interestingly, the files with zero bytes are also the ones that are
failing.  I am not sure where in the process the files are generated and
especially why they are zero bytes.

My tar version is:
=====================
root@tarjan:/tmp/amanda> tar --version
tar (GNU tar) 1.13.19
Copyright 2001 Free Software Foundation, Inc.
This program comes with NO WARRANTY, to the extent permitted by law.
You may redistribute it under the terms of the GNU General Public
License;
see the file named COPYING for details.
Written by John Gilmore and Jay Fenlason.
root@tarjan:/tmp/amanda>
================================

> 
> -- 
> Joshua Baker-LePain
> Department of Biomedical Engineering
> Duke University
>