st0 top localhost
> > /data_/mica1 20170219 " | tar -xpGf -
> >
> > returns 'Error writing to fd 7: Broken pipe'. The logfile shows:
> Assuming fd 7 is the pipe to tar, it means that tar exited before
> amfetchdump send all the data, do you get any error from tar?
>
On 20/02/17 11:47 AM, Jean-Francois Malouin wrote:
> Hi,
>
> Attempting to restore a DLE with amfetchdump with:
>
> su amanda -c "~amanda/sbin/amfetchdump -p -d tape:/dev/nst0 top localhost
> /data_/mica1 20170219 " | tar -xpGf -
>
> returns 'Error writing to fd
/data_/mica1 20170219 " | tar -xpGf -
>
> returns 'Error writing to fd 7: Broken pipe'. The logfile shows:
>
> Mon Feb 20 11:26:03.128402078 2017: pid 14583: thd-0x2e49c00: amfetchdump:
> xfer_cancel_with_error: Error writing to fd 7: Broken pipe
> Mon Feb 20 11:26:03.1
Hi,
Attempting to restore a DLE with amfetchdump with:
su amanda -c "~amanda/sbin/amfetchdump -p -d tape:/dev/nst0 top localhost
/data_/mica1 20170219 " | tar -xpGf -
returns 'Error writing to fd 7: Broken pipe'. The logfile shows:
Mon Feb 20 11:26:03.128402078 2017: pid 14583: thd
Hi,
Le vendredi 21 janvier 2011 17:55:50, vous avez écrit :
I am finding that amcheckdump (3.2.0) gets sporadic failures with messages
like
Reading volume AMB009L4 file 9
Validation errors:
Error writing to fd 9: Broken pipe
/bin/gzip exited with status 1
maybe you should check the logs
I am finding that amcheckdump (3.2.0) gets sporadic failures with messages
like
Reading volume AMB009L4 file 9
Validation errors:
Error writing to fd 9: Broken pipe
/bin/gzip exited with status 1
A similar problem was reported in
http://www.mail-archive.com/amanda-users@amanda.org/msg44288
Additional information about this problem.
An additional external USB hard drive has been added to this host about
one month ago. The filesystem on this hard drive is not backed up with
Amanda. But the observation is that the Broken Pipe problem seems to
disappear when the filesystem
: Broken pipe]
backup_client_host /vol/vol1/home lev 0 FAILED [input: Can't read data: :
Connection reset by peer]
backup_client_host /vol/vol1/home lev 0 FAILED [dump to tape failed]
The same error was observed about a month ago. I had browsed through the wiki,
in which I couldn't find
Any suggestions ? My backup has failed for 3 days now.
Yogesh Hasabnis wrote:
gzip: stdout: Connection timed out
This is weird, do your system automaticaly close connection after some time?
After how many it happens? is it always the same?
Jean-Louis
Post the complete amdump.? file
Yogesh Hasabnis wrote:
--- On *Thu, 6/18/09, Jean-Louis Martineau /martin...@zmanda.com/*
wrote:
No it doesn't. The backup system with amanda was working fine all
these days. The problem has cropped up since last 4 days. All of
the last 4 daily
--- On Thu, 6/18/09, Jean-Louis Martineau martin...@zmanda.com wrote:
From: Jean-Louis Martineau martin...@zmanda.com
Subject: Re: FAILED [data write: Broken pipe]
To: Yogesh Hasabnis yhmai...@yahoo.co.in
Cc: amanda-users@amanda.org
Date: Thursday, June 18, 2009, 6:02 PM
Yogesh Hasabnis
days. The error message that I
get in the email message is as follows:
FAILURE AND STRANGE DUMP SUMMARY:
hostname /vol/vol1/home lev 2 FAILED [data write: Broken pipe]
hostname /vol/vol1/home lev 2 FAILED [data write: Broken pipe
I see the following text in the /var/log/amanda
creator: /bin/tar -tf - 2/dev/null |
sed -e 's/^\.//'
sendbackup-gnutar: time 0.082: /usr/lib/amanda/runtar: pid 14729
sendbackup: time 0.083: started backup
sendbackup: time 2996.696: index tee cannot write [Broken pipe]
sendbackup: time 2996.718: pid 14728 finish time Fri Nov 21 23:35:57 2008
lev
3 FAILED [data write: Broken pipe]driver: FATAL Don't know how to send
ABORT command to chunkerchunker: FATAL error [bad command after
RQ-MORE-DISK: QUIT]
Also, after running the ps -ef command I observe that the amdump process is
still running. The ouput of
ps -ef | grep
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 joy. Could
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 aspects I can
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 message. I have looked at all
-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
aspects I can think of but still
.
sendbackup: time 385956.603: started index creator:
/usr/freeware/bin/tar -tf - 2/dev/null | sed -e 's/^\.//'
sendbackup-gnutar: time 385956.605: /usr/freeware/libexec/runtar: pid
14323097
sendbackup: time 385956.606: started backup
sendbackup: time 385969.818: index tee cannot write [Broken pipe
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
, then there was a broken pipe message in
syslog (but
not in Amanda report), then the DLE was restarted directly to tape and got
backed up
successfully.
It seems that now, once the holdingdisk fills up, the DLE is not restarted
directly
to tape, it just fails.
I think I might set holdingdisk no for this DLE since
would not be ideal).
Well, Changing the etimeout/estimate-method in amanda.conf definitely
helped, but now I'm getting a broken-pipe error. Here's the excerpt
from this morning's e-mail:
aspapp2.tonservices.com /opt/webapp/images lev 0 FAILED [data
timeout]
aspapp2.tonservices.com /opt
Cameron Matheson schreef:
Well, Changing the etimeout/estimate-method in amanda.conf definitely
helped, but now I'm getting a broken-pipe error. Here's the excerpt
from this morning's e-mail:
aspapp2.tonservices.com /opt/webapp/images lev 0 FAILED [data
timeout]
aspapp2
Smith [EMAIL PROTECTED]
To: Reidar Nordin [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Monday, August 30, 2004 2:33 AM
Subject: Re: [out of tape] [dump to tape failed] [data write: Broken pipe]
--On Sunday, August 29, 2004 15:17:50 +0200 Reidar Nordin [EMAIL PROTECTED] wrote:
Your 'tape
[[writing file: short write]]
FAIL driver awe /home 20040828 0 [dump to tape failed]
FAIL dumper awe /home 20040828 0 [data write: Broken pipe]
sendbackup: start [awe:/home level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/usr/bin/gzip -dc |/bin/tar -f... -
sendbackup: info
file: short write
FAIL taper awe /home 20040828 0 [out of tape]
ERROR taper no-tape [[writing file: short write]]
FAIL driver awe /home 20040828 0 [dump to tape failed]
FAIL dumper awe /home 20040828 0 [data write: Broken pipe]
sendbackup: start [awe:/home level 0]
sendbackup: info BACKUP
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
[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
host.domain /home comp-user-tar -1 local
And with comp
-- 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
client
backs up fine using the same configuration.
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
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
Hi!
I get Broken pipe all the time when backing up using tar. The backup client
is at a different site, so backup is performed over a 2 Mbit/s line. While
the 2Mb line is not top quality, using netstat -i 1 reveals that after a
number of hours, almost no backup data is sent at all. Finally
Palle Girgensohn wrote:
I get Broken pipe all the time when backing up using tar. The backup
client is at a different site, so backup is performed over a 2 Mbit/s
line. While the 2Mb line is not top quality, using netstat -i 1 reveals
that after a number of hours, almost no backup data is sent
write [Broken pipe]
? index returned 1
sendbackup: error [/usr/bin/tar got signal 13]
\
Another machine is configured identically but has no problem... Any
ideas?
Thanks
John Grover
John W Grover, Systems and Database Administrator
Lake Michigan College
| sed -e
's/^\.//'
index tee cannot write [Broken pipe]
sendbackup: pid 28683 finish time Thu Sep 18 00:18:14 2003
error [/bin/tar got signal 13, compress returned 1]
Any ideas ?
What does taper: FATAL syncpipe_put: Broken pipe mean? I've tried
twice to flush a 26 GB dump image to tape, and got this message both
times.
--
Kurt Yoder
Sport Health network administrator
Paul Bijnens said:
Kurt Yoder wrote:
What does taper: FATAL syncpipe_put: Broken pipe mean? I've
tried
twice to flush a 26 GB dump image to tape, and got this message
both
times.
Any other messages in the file amdump.* and the LOG.datestamp.lvl.
file?
There are two tapers, a reader
Paul Bijnens said:
Kurt Yoder wrote:
My amdump log file is quite long, so here's the part that seems
most
relevant:
...
It seems it is the taper writer that is somehow crashing, without
telling anybody. Do you find a core file in the amanda home dir
or in /tmp/amanda ?
Nope
[EMAIL
On Thu, Sep 11, 2003 at 12:09:24PM -0400, Kurt Yoder wrote:
So what would be
wrong with the dump image? Should I try manually uncompressing that
image and seeing what's on it?
I doubt you'd learn anything. As far as taper is concerned, I
believe the image is just an opaque stream of bytes.
Kurt Yoder said:
What does taper: FATAL syncpipe_put: Broken pipe mean? I've tried
twice to flush a 26 GB dump image to tape, and got this message both
times.
It was a hardware problem. Something about the motherboard and Linux
didn't get along. Switching to previous motherboard seems to have
dump returns Broken pipe with I turn sencrypt
to on, if I don't use sencrypt it works pefectly. Here is the output of the
sendbackup logfile on the client:
sendbackup: debug 1 pid 21255 ruid 104 euid 104: start at Sun Feb 9
19:44:14 2003
/opt/amanda/libexec/sendbackup: version 2.4.3
parsed
I'm trying to restore a backup of a client from tape I'd like to first
read archive file off tape onto amanda server, then move the file onto
the amanda client and run it through restore
I typed:
amrestore /dev/nst1 samba /dev/hdc1
after a few minutes of restoring I get:
Error 32 (Broken
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
I recently added a new machine to my backups, and seem to be having a
problem with a couple of file systems with index tee cannot write [Broken
pipe] errors.
Client is Solaris 7
Server is Solaris 7
amanda version 2.4.2p2
gnutar 1.13.19
firewall between the two servers, but no security
-Original Message-
From: John R. Jackson [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 17, 2001 3:30 PM
To: Chris Noon
Cc: [EMAIL PROTECTED]
Subject: Re: broken pipe?!
... Unfortunately, another dump ran on
that client since this error, so sendbackup.debug doesn't refer
: 93.48% done, finished in 0:09
| DUMP: 10816190 blocks (5281.34MB) on 1 volume at 598 KB/sec
| DUMP: DUMP IS DONE
| DUMP: Level 0 dump on Wed Sep 12 09:37:15 2001
? Broken Pipe
sendbackup: size 5408095
sendbackup: end
\
I keep getting the following error whenever I run a Level 0 on this one
disk. ...
| DUMP: DUMP IS DONE
| DUMP: Level 0 dump on Wed Sep 12 09:37:15 2001
? Broken Pipe
I take it the client is Solaris? What version of Amanda? What's in
/tmp/amanda/sendbackup*debug on the client?
John R
PROTECTED]
Subject: Re: broken pipe?!
I keep getting the following error whenever I run a Level 0 on this one
disk. ...
| DUMP: DUMP IS DONE
| DUMP: Level 0 dump on Wed Sep 12 09:37:15 2001
? Broken Pipe
I take it the client is Solaris? What version of Amanda? What's in
/tmp/amanda
... Unfortunately, another dump ran on
that client since this error, so sendbackup.debug doesn't refer to this
dump.
Sigh. FYI, if you upgrade that client to 2.4.2p2 (you would not have
to do everything), the debug files will be kept separate. Or you could
rebuild that client using
I'm getting a weird error on one of my amanda clients (2.4.1p1 on
freebsd 4.2 using gnu tar v 1.13) ...
I hope you don't really mean 1.13 for tar. If it's not 1.13.19 or later
(from alpha.gnu.org), you're not getting good index files.
? sendbackup: index tee cannot write [Broken pipe
: info BACKUP=/usr/bin/tar
sendbackup: info RECOVER_CMD=/usr/bin/tar -f... -
sendbackup: info end
? sendbackup: index tee cannot write [Broken pipe]
sendbackup: error [/usr/bin/tar got signal 13, index returned 1]
\
/tmp/amanda/sendbackup.debug says:
sendbackup: debug 1 pid 25453 ruid 1000
: Label: none
| DUMP: mapping (Pass I) [regular files]
| DUMP: mapping (Pass II) [directories]
| DUMP: estimated 431729 tape blocks.
| DUMP: Volume 1 started at: Thu Aug 2 00:53:17 2001
? sendbackup: index tee cannot write [Broken pipe]
| DUMP: Broken pipe
| DUMP: The ENTIRE dump
On Thu, 2 Aug 2001, John R. Jackson wrote:
... I haven't touched something since weeks.
Yeah, yeah, yeah. We've all heard that story before :-).
He hereally! :-)))
Here is, what amanda report says:
? sendbackup: index tee cannot write [Broken pipe]
What else was in the Amanda
On Thu, 2 Aug 2001, John R. Jackson wrote:
... I haven't touched something since weeks.
Yeah, yeah, yeah. We've all heard that story before :-).
OK., I'm catched. :-))
I touched something on sunday: my firewall. :-(
Seems to be a firewall problem now, packets were dropped
since I installed
... I haven't touched something since weeks.
Yeah, yeah, yeah. We've all heard that story before :-).
Here is, what amanda report says:
? sendbackup: index tee cannot write [Broken pipe]
What else was in the Amanda report, in particular about this disk or
from taper?
This typically means
You don't, by any chance, have both hardware and software compression
turned on, do you?
How do I tell, exactly? I have a dumptype line reading
compress client fast
But that just seems like which CPU it uses to compute the compression
algorithm.
This line says you are using software
A DDS-3 tape should hold 12GB, compressed, right? It looks like taper
dies after 10GB. Does the TAPE-ERROR/short write mean the tape is bad? If
the tape was more full, I wouldn't be suspicious; but it seems like I
should be getting more space out of 125m.
Amanda consider only the
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
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 just a symptom of
the server giving up on the client. The server
that it helps:
Begin complete mail fom Amanda
These dumps were to tapes Daily01, Daily02.
Tonight's dumps should go onto 2 tapes: Daily03, Daily04.
FAILURE AND STRANGE DUMP SUMMARY:
fileserver sdc1 lev 0 FAILED ["data write: Broken pipe"]
fileserver sdc1 lev 0 FAILED [dump to t
On Feb 15, 2001, Juergen Knott [EMAIL PROTECTED] wrote:
fileserver sdb10 1319558413195584 -- 40:525380.8 40:555375.7
fileserver sdc10 1313555213135552 -- 45:114844.5 45:134840.9
fileserver sdd10 92850889285088 -- 30:535009.9 30:555005.7
king
Am Donnerstag, 15. Februar 2001 09:50 schrieben Sie:
See? No failures. You can use amtoc or amadmin info to find out in
which tape the filesystem was stored.
OK, no failure. Amadmin tell me that the backup is ok.
I thank you for your help and Infos.
Bye Juergen
--
Dies ist eine Microsoft
DUMP SUMMARY:
fileserver sdc1 lev 0 FAILED ["data write: Broken pipe"]
fileserver sdc1 lev 0 FAILED [dump to tape failed]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:10
Run Tim
On Feb 15, 2001, Juergen Knott [EMAIL PROTECTED] wrote:
fileserver sdc1 lev 0 FAILED ["data write: Broken pipe"]
fileserver sdc1 lev 0 FAILED [dump to tape failed]
[snip]
taper: tape Daily01 kb 44245472 fm 4 writing file: No space left on device
Looks like tape full.
t
Am Donnerstag, 15. Februar 2001 08:40 schrieben Sie:
On Feb 15, 2001, Juergen Knott [EMAIL PROTECTED] wrote:
fileserver sdc1 lev 0 FAILED ["data write: Broken pipe"]
fileserver sdc1 lev 0 FAILED [dump to tape failed]
[snip]
taper: tape Daily01 kb 44245472 fm 4 wr
On Feb 15, 2001, Juergen Knott [EMAIL PROTECTED] wrote:
Also the backup is finnished correctly?
I'd guess so, but you didn't post the part of the report that says
which dumps made to which tape, so I can't tell for sure.
--
Alexandre Oliva Enjoy Guarana', see
70 matches
Mail list logo
