09:56:12AM -0400, Mike Gallant wrote:
I have an amanda (2.5.1p3) server (solaris10) with seven amanda
clients (2.4.4) and a new amanda (2.5.2) client on new hardware.
I have been getting a "index tee cannot write
[Broken pipe]" error message. I have looked at all the various
aspect
On Thu, Aug 02, 2007 at 09:56:12AM -0400, Mike Gallant wrote:
> I have an amanda (2.5.1p3) server (solaris10) with seven amanda clients
> (2.4.4) and a new amanda (2.5.2) client on new hardware. I have been getting
> a "index tee cannot write
> [Broken pipe]" error mess
On 2007-08-02 15:56, Mike Gallant wrote:
I have an amanda (2.5.1p3) server (solaris10) with seven amanda clients
(2.4.4) and a new amanda (2.5.2) client on new hardware. I have been
getting a "index tee cannot write [Broken pipe]" error message. I have
looked at all the various asp
I have an amanda (2.5.1p3) server (solaris10) with seven amanda
clients (2.4.4) and a new amanda (2.5.2) client on new hardware. I
have been getting a "index tee cannot write [Broken pipe]" error
message. I have looked at all the various aspects I can think of but
still no j
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 backu
956.606: started backup
sendbackup: time 385969.818: index tee cannot write [Broken pipe]
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: e
05, 2003 10:19 AM
--> 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 lo
> > ? sendbackup: index tee cannot write [Broken pipe]
--> > ? index returned 1
--> > sendbackup: error [/usr/bin/tar got signal 13]
Clarifying -- I guess you had DLE's like:
host.domain /amandaholding-disk -1 local
host.domain / comp-user-tar -1 local
TECTED]
--> 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
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
fo end
? sendbackup: index tee cannot write [Broken pipe]
? index returned 1
sendbackup: error [/usr/bin/tar got signal 13]
\
Log excerpt:
...
WARNING planner Last full dump of MyClient.my.domain.name.here:/ on
tape overwritten in 1 run.
...
FAIL dumper MyClient.my.domain.name.here / 20031101
index creator: "/bin/gtar -tf - 2>/dev/null | sed -e
's/^\.//'"
index tee cannot write [Broken pipe]
sendbackup: pid 28448 finish time Tue Feb 26 17:49:17 2002
Backup is fail.
I can not understand this error.
Please help me.
Best regards,
Masafumi Hikawa
t; <[EMAIL 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
>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 kno
- 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]
an hour to wait on data is a long time.
I suspect it means something else is wrong.
It would also be useful to go to the client and look at sendbackup*debug
in /tmp/amanda, in particular the start and stop time (first and last
lines).
The "index tee cannot write [Broken pipe]" stuff is
start [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
17 matches
Mail list logo
