On 01/10/2011 04:41 AM, mohammad tayebi wrote:
> *Hi Backuppc Users*
>
> i have problem ?
> my backupc server has Raid 5 And mounted /var/lib/backuppc
>
> ofcource my quesition is : This Log
>
> *" 2011-01-09 20:00:03 Got fatal error during xfer (aborted by signal=PIPE)"*
There are many reasons
On Mon, Jan 10, 2011 at 10:43:50AM -0600, Les Mikesell wrote:
> On 1/10/2011 10:26 AM, Robin Lee Powell wrote:
> > On Mon, Jan 10, 2011 at 01:11:50PM +0330, mohammad tayebi wrote:
> >> *Hi Backuppc Users*
> >>
> >> i have problem ? my backupc server has Raid 5 And mounted
> >> /var/lib/backuppc
> >
On 1/10/2011 10:26 AM, Robin Lee Powell wrote:
> On Mon, Jan 10, 2011 at 01:11:50PM +0330, mohammad tayebi wrote:
>> *Hi Backuppc Users*
>>
>> i have problem ?
>> my backupc server has Raid 5 And mounted /var/lib/backuppc
>>
>> ofcource my quesition is : This Log
>>
>> *" 2011-01-09 20:00:03 Got fa
On Mon, Jan 10, 2011 at 01:11:50PM +0330, mohammad tayebi wrote:
> *Hi Backuppc Users*
>
> i have problem ?
> my backupc server has Raid 5 And mounted /var/lib/backuppc
>
> ofcource my quesition is : This Log
>
> *" 2011-01-09 20:00:03 Got fatal error during xfer (aborted by signal=PIPE)"*
>
>
*Hi Backuppc Users*
i have problem ?
my backupc server has Raid 5 And mounted /var/lib/backuppc
ofcource my quesition is : This Log
*" 2011-01-09 20:00:03 Got fatal error during xfer (aborted by signal=PIPE)"*
backuppc serve stop every daily at 20 pm or (19:58 , 19:57 ) i backup
my fileserver (
On Thursday 17 July 2008 00:46, Les Mikesell wrote:
> Peter Nankivell wrote:
> > No problems. Thanks to everyone who contributed. There were plenty
> > who did so unwittingly through their posts to other lists.
> >
> > As a measure of how happy I feel about the solution, my first successful
> >
Peter Nankivell wrote:
> No problems. Thanks to everyone who contributed. There were plenty
> who did so unwittingly through their posts to other lists.
>
> As a measure of how happy I feel about the solution, my first successful full
> dump of this machine took 22 minutes compared to 137 minute
No problems. Thanks to everyone who contributed. There were plenty
who did so unwittingly through their posts to other lists.
As a measure of how happy I feel about the solution, my first successful full
dump of this machine took 22 minutes compared to 137 minutes when I
had to use the "--whole-
On 07/16 03:35 , Peter Nankivell wrote:
> For the client "tcp segmentation offload" was "on". Turning it off
> using
>
> # ethtool -K eth0 tso off
>
> worked! The test "rsync" now works wonderfully.
Thanks for the update Peter! This might be very useful troubleshooting
information in the f
rver tonight.
> Although I suspect the client as the server backs up other machines OK.
>
> Thanks, Peter.
>
> On Tuesday 15 July 2008 13:17:16 Adam Goryachev wrote:
> > Holger Parplies wrote:
> > > Hi,
> > >
> > > Peter Nankivell wrote on 2008-07-15 0
As a debugging step, any way you could change this client to use rsync
without "ssh". Not sure what your level of security concern is but
the PIPE error points to either SSH collapsing or RSYNC collapsing on
the client side. I believe this because your getting a PIPE error
rather than some sort o
hanks, Peter.
On Tuesday 15 July 2008 13:17:16 Adam Goryachev wrote:
> Holger Parplies wrote:
> > Hi,
> >
> > Peter Nankivell wrote on 2008-07-15 09:17:48 +1000 [Re: [BackupPC-users]
aborted by signal=PIPE errors.]:
> >> [...]
> >> If it is all due to ssh a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Holger Parplies wrote:
> Hi,
>
> Peter Nankivell wrote on 2008-07-15 09:17:48 +1000 [Re: [BackupPC-users]
> aborted by signal=PIPE errors.]:
>> [...]
>> If it is all due to ssh and hardware it makes me worry about
>>
Peter Nankivell wrote:
> Hello,
>
> Heaps of data goes over this link, apparently without error and it has been
> doing it for at least a year. Isn't it likely that I would have seen TCP
> errors throw up problems with other s/w by now?
TCP retries can cover up a lot of problems.
> If the data i
't it?
Cheers, Peter.
On Tuesday 15 July 2008 10:02:42 Holger Parplies wrote:
> Hi,
>
> Peter Nankivell wrote on 2008-07-15 09:17:48 +1000 [Re: [BackupPC-users]
aborted by signal=PIPE errors.]:
> > [...]
> > If it is all due to ssh and hardware it makes me worry about
> &g
Hi,
Peter Nankivell wrote on 2008-07-15 09:17:48 +1000 [Re: [BackupPC-users]
aborted by signal=PIPE errors.]:
> [...]
> If it is all due to ssh and hardware it makes me worry about
> the resilience of ssh. Surely its protocol should be able to
> retry on corrupted data?
You guys have been a great help! I've never gotten such useful and fast
replies before. Keep up the good work BackupPC community!
Now that you guys have mentioned about the problem maybe being with the host
itself, I checked the host to see if there were problems. Sure enough, there
is a problem w
Bruno,
I have been chasing this problem also, but I have additional
problems. One is that the backup occasionally hangs without
any error message, the other, more frequently, is that the backup
fails with an additional message "corrupted MAC on input".
The "MAC" is not the address of the NIC, but
Hi,
Bruno Faria wrote on 2008-07-14 13:11:45 -0500 [[BackupPC-users] aborted by
signal=PIPE errors.]:
> [...]
> I searched google about this error message, and it seems like many backuppc
> users have encountered this before, although I could not find any solutions.
> [...]
> Ple
Thanks Tony, with that command I was able to check the end of XferLog file.
Here's what the log file says:
Can't write 32780 bytes to socket
Read EOF: Connection reset by peer
Tried again: got 0 bytes
finish: removing in-process file
/path/to/some/directory/images/nat_logo-on.gif
Child is abortin
Bruno Faria wrote:
>
> As Bowie mentioned it could that BackupPC is chocking on some large
> file.
>
> I tried to find where the backup is stopping by checking the errors
> Xferr log, but the file was too big to view in a web browser, since it
> contained a list of everything that was backed up,
On Jul 14, 2008, at 3:27 PM, Bruno Faria wrote:
> As Bowie mentioned it could that BackupPC is chocking on some large
> file.
>
> I tried to find where the backup is stopping by checking the errors
> Xferr log, but the file was too big to view in a web browser, since
> it contained a list o
As Bowie mentioned it could that BackupPC is chocking on some large file.
I tried to find where the backup is stopping by checking the errors Xferr
log, but the file was too big to view in a web browser, since it contained a
list of everything that was backed up, up to the point that the backups
f
Hello Bruno,
> The size of backups varies. I have gotten the "aborted by signal=PIPE"
> error by 6GB backups while I have also gotten for 30-40GB backups.
>
> I have also increased the timeout period to a large number since I
> have some large backups.
I never saw your specific failure but I jus
Bruno Faria wrote:
> Hey guys,
>
> This is the third message that I'm posting about this problem, but so
> far I haven't gotten any solutions.
>
> I'm getting the error message: aborted by signal=PIPE in some of the
> hosts that I'm backing up. Some hosts get this error while doing
> incremental
Thanks for the reply Renke!
All of the hosts are linux machines that have static IP address, and they're
being backed up via rsync.
The size of backups varies. I have gotten the "aborted by signal=PIPE" error
by 6GB backups while I have also gotten for 30-40GB backups.
I have also increased the
Hi Bruno
> Please let me know if anyway knows of a solution to backups "aborted
> by signal=PIPE".
no solution but can you isolate the issue? eg transport method, size of
the backupped hosts, DHCP or static address, ...
(I'm not aware of your first mails so sorry if you explained all of the
stu
Hey guys,
This is the third message that I'm posting about this problem, but so far I
haven't gotten any solutions.
I'm getting the error message: aborted by signal=PIPE in some of the hosts
that I'm backing up. Some hosts get this error while doing incremental
backups, while other hosts get duri
I had set before at 172000 and it was still causing that error.
On Thu, May 1, 2008 at 2:18 PM, Ryan Manikowski <[EMAIL PROTECTED]> wrote:
> In the client configuration, go to Backup Settings and set ClientTimeout to
> 14400. If you're editing the hosts config file directly, the setting is
> $Conf
I have my logs outputting the following errors:
2008-04-30 10:43:13 Backup failed on myserver1 (aborted by signal=PIPE)
How can I troubleshoot this error?
-
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Jason Harrison wrote:
> Greetings,
>
> I have excluded the files that cause the backup to fail and done a successful
> full backup. However when I remove the files from the excludes and try
> another full backup the backup still fails on a file in the backup directory
> on the remote host.
>
Greetings,
I have excluded the files that cause the backup to fail and done a successful
full backup. However when I remove the files from the excludes and try
another full backup the backup still fails on a file in the backup directory
on the remote host.
Any ideas?
Regards,
Jason
On 09/21 08:23 , Jason Harrison wrote:
> I will try what you have suggested. Just for the record I have suspected
> there is one or two really large files that might be causing the problem. If
> that is the case is there anything that can be done about it so the backups
> work?
it seems odd,
On Thursday 20 September 2007 4:18:44 pm Carl Wilhelm Soderstrom wrote:
> On 09/20 04:05 , Jason Harrison wrote:
> > Yes I have tried regular rsync. Yes using cygwin-rsync but not rsyncd I
> > dont think. It usually runs about 15 minutes to an hour. It seems like
> > the time varies but its usua
On 09/20 04:05 , Jason Harrison wrote:
> Yes I have tried regular rsync. Yes using cygwin-rsync but not rsyncd I dont
> think. It usually runs about 15 minutes to an hour. It seems like the time
> varies but its usually within an hour that it fails.
I'd try excluding certain directories from
On Thursday 20 September 2007 4:02:36 pm Carl Wilhelm Soderstrom wrote:
> On 09/20 09:09 , Jason Harrison wrote:
> > The two hosts we are getting the aborted by signal=PIPE on are windows
> > machines. We get this consistently whether doing manual backups or
> > scheduled.
>
> have you tried runni
On 09/20 09:09 , Jason Harrison wrote:
> The two hosts we are getting the aborted by signal=PIPE on are windows
> machines. We get this consistently whether doing manual backups or
> scheduled.
have you tried running regular rsync against them? (presuming you're using
cygwin-rsyncd).
How long
Greetings,
We have a server doing backups. The hosts being backed up are a mix of linux
and windows systems. All use rsync although I have tried tar on the two
machines having issues backing up with the same kind of error. The backup
sizes are 3.6GB and 5.8GB.
We are using backuppc 3.0.0 on
Keith writes:
> Version 2.1.2 using rsync.
>
> I have a client that intermittently fails with "aborted by signal=PIPE",
> which I realise is a common error. I have $Conf{ClientTimeout} =
> 72000; the end of the log file (with $Conf{XferLogLevel} = 8;) looks like
> this:
>
> -
Version 2.1.2 using rsync.
I have a client that intermittently fails with "aborted by signal=PIPE",
which I realise is a common error. I have $Conf{ClientTimeout} =
72000; the end of the log file (with $Conf{XferLogLevel} = 8;) looks like
this:
hello to all
I have a problem when to try to do full backup.
The error that I have is aborted by signal=PIPE
I hope that they can help me
--
SAludos
JOse
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.
hello to all
I have a problem when to try to do full backup.
The error that I have is aborted by signal=PIPE
I hope that they can help me
--
SAludos
JOse
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.
Well BackupPC ran last night on the problem machine without any problems.
It did an incremental backup of the 2 40+Gb partitions including the
large 4.8Gb file. So I'll just monitor it for a while now and see what
happens. Gets stranger and stranger
Tony
--
Tony Molloy.
Dept. of Comp. Sci
On Wednesday 03 May 2006 15:35, Carl Wilhelm Soderstrom wrote:
> On 05/03 10:23 , Ken Long wrote:
> > In my case, I have been deploying rsyncd to a number of Windows boxes
> > over the past week and so far, all the rest are working, but not this
> > one machine. It runs for about an hourtransf
On Wednesday 03 May 2006 15:23, Ken Long wrote:
> I'm getting this same error on one of my Windows clients. I've been
> through google and the archives on this list and see where the question
> about this error message is often asked and virtually never answered.
> The only answers I saw to it tal
On Wed, 2006-05-03 at 09:35 -0500, Carl Wilhelm Soderstrom wrote:
> On 05/03 10:23 , Ken Long wrote:
> > In my case, I have been deploying rsyncd to a number of Windows boxes
> > over the past week and so far, all the rest are working, but not this
> > one machine. It runs for about an hourtra
On 05/03 10:23 , Ken Long wrote:
> In my case, I have been deploying rsyncd to a number of Windows boxes
> over the past week and so far, all the rest are working, but not this
> one machine. It runs for about an hourtransfers a couple
> gigs...then gets this error message every time.
what'
I'm getting this same error on one of my Windows clients. I've been
through google and the archives on this list and see where the question
about this error message is often asked and virtually never answered.
The only answers I saw to it talked about things that weren't relevant
in my case.
Doe
I'v been running backuppc on several Linux and Windows boxes for the last
few months without any problems. An excelent piece of software ;-)
Over the holiday weekend one backup failed. Why does it always happen over
a holiday!! BackupPC was running on a Centos-4.3 box using rsync
(rsync-2.6.3
Hello,
I started an incremental backup which stopped very quickly.
The log file says "2006-04-12 15:58:01 Backup failed on mymachine
(aborted by signal=PIPE)".
What does it mean ?
I alreary done several incremental backup before without problem.
Thank You.
---
50 matches
Mail list logo
