RE: sendbackup: index tee cannot write [Broken pipe], Why?

I had this problem and fixed it by specifying "holding-disk -1 local" in
disklist for the partition holding ~amanda on the tape server, and
specifying "-1 local" for the rest of the tape server partitions.

Regards,
 
Michael Martinez
ISTM/CSREES
United States Department of Agriculture
---
This email is signed with my digital signature so that you may verify
the authenticity of the sender.

--> -----Original Message-----
--> From: Paul Bijnens [mailto:paul.bijnens AT xplanation DOT com] 
--> Sent: Monday, November 03, 2003 11:17 AM
--> To: John Grover
--> Cc: amanda-users AT amanda DOT org
--> Subject: Re: sendbackup: index tee cannot write [Broken pipe], Why?
--> 
--> 
--> John Grover wrote:
--> 
--> > I'm guessing that the timeout is caused by the failure of 
--> tar to write
--> > to the broken pipe, but the logs don't give me much to go on. I've
--> > scoured every lat resource I can find and still get these 
--> results. I'd
--> > be happy to send logs to anyone who would care to help me out with
--> > this.
--> 
--> 
--> >   ? sendbackup: index tee cannot write [Broken pipe]
--> >   ? index returned 1
--> >   sendbackup: error [/usr/bin/tar got signal 13]
--> 
--> This problem is signalled now and then on this list. People 
--> give lots of
--> tips to help/investigate/fix, but nobody ever came back and 
--> told what
--> he/she did to solve it.  If it ever got solved at all.
--> 
--> It seems it is the index-pipe on the server that is failing with
--> an (unknown) error.  This triggers a broken index pipe on 
--> the client.
--> We're not sure about that either.  That's why I suggested to
--> (temporarily) run without index for this DLE, and see if it gets any
--> better.
--> 
--> If this works fine, they you could try to create the index manually,
--> and see what's wrong, using commands on the server:
-->     amrestore -p ... | gtar -tf -  > /tmp/the_index
--> Then with "gtar" running on the client:
-->     ssh -l amanda amanda_server amrestore -p ... | gtar -tf 
--> - > /tmp/x
--> 
--> If you gzip the resulting index file and put in the correct 
--> place, with
--> the correct name, you have an index for amrecover too.
--> 
--> 
--> Also verify the gnutar version (on the client!);  best is 1.13.25 
--> (1.13.19 is probably ok too, but if you have it, I advice 
--> to upgrade 
--> anyway).  All other versions are suspicious.
--> Maybe the problem is with gzip (index files are ALWAYS compressed 
--> --best).  Verify that version too.
--> 
--> 
--> -- 
--> Paul Bijnens, Xplanation                            Tel  
--> +32 16 397.511
--> Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM    Fax  
--> +32 16 397.512
--> http://www.xplanation.com/          email:  
--> Paul.Bijnens AT xplanation DOT com
--> ************************************************************
--> ***********
--> * I think I've got the hang of it now:  exit, ^D, ^C, ^\, 
--> ^Z, ^Q, F6, *
--> * quit,  ZZ, :q, :q!,  M-Z, ^X^C,  logoff, logout, close, 
--> bye,  /bye, *
--> * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,  
--> abort,  hangup, *
--> * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e,  kill -1 $$,  
--> shutdown, *
--> * kill -9 1,  Alt-F4,  Ctrl-Alt-Del,  AltGr-NumLock,  
--> Stop-A,  ...    *
--> * ...  "Are you sure?"  ...   YES   ...   Phew ...   I'm 
--> out          *
--> ************************************************************
--> ***********
--> 
--> 
-->
smime.p7s
Description: S/MIME cryptographic signature