]
sendbackup: time 385969.818: pid 14193336 finish time Wed Mar 7
04:11:21 2007
sendbackup: time 385969.842: 117: strange(?): sendbackup: index tee
cannot write [Broken pipe]
sendbackup: time 403598.554: error [/usr/freeware/bin/tar got signal 9]
sendbackup: time 403598.615: pid 13900492 finish time
A few days ago I had some backup problems that turned out to be caused
by a hanging NFS mount, causing sendsize to lock up completely - see
a separate post on this. Now I have sorted out this problem, and it
seemed like amdump would once again start properly, but it turns out
that the backup
-- 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
Martinez, Michael wrote:
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.
-- John Grover wrote:
--
--? sendbackup: index tee cannot write
-- To: Martinez, Michael
-- Cc: [EMAIL PROTECTED]
-- Subject: Re: sendbackup: index tee cannot write [Broken pipe], Why?
--
--
-- Martinez, Michael wrote:
--
-- I had this problem and fixed it by specifying
-- holding-disk -1 local in
-- disklist for the partition holding ~amanda on the tape server
: start [MyClient.my.domain.name.here:/ level 0]
sendbackup: info BACKUP=/usr/bin/tar
sendbackup: info RECOVER_CMD=/usr/bin/tar -f... -
sendbackup: info end
? gtar: Cannot add file
./usr/local/blackboard/docs/lib/session/41394: No such file or
directory
? sendbackup: index tee cannot write
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
PROTECTED]
To: Ryan Williams [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, May 01, 2001 6:59 PM
Subject: Re: Strange Amanda Error: sendbackup: index tee cannot write
[Broken pipe]
It is a 100meg card set to autoselect between all of the 100 and 10 base
T.
Uh, huh. On Solaris, at least
- Original Message -
From: John R. Jackson [EMAIL PROTECTED]
To: Ryan Williams [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, April 30, 2001 7:20 PM
Subject: Re: Strange Amanda Error: sendbackup: index tee cannot write
[Broken pipe]
Below are the two pertinant parts (I think
It is a 100meg card set to autoselect between all of the 100 and 10 base T.
Uh, huh. On Solaris, at least, autoselect is death. No matter what
you try to do, it will pick wrong and really bad things start to happen.
We **always** force the issue with an explicit config file entry.
I don't
[web45.internal:ad0s1f level 0]
sendbackup: info BACKUP=/usr/bin/tar
sendbackup: info RECOVER_CMD=/usr/bin/tar -f... -
sendbackup: info end
? sendbackup: index tee cannot write [Broken pipe]
? index returned 1
sendbackup: error [/usr/bin/tar got signal 13]
\
Regards,
Ryan Williams
Below are the two pertinant parts (I think) of an error that is occuring on
an everyday basis on this server. ...
What version of Amanda? Same version on client and server?
... There are 11 other servers that are being backed up
just fine but this one just does not want to work. ...
So
12 matches
Mail list logo
