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
23 matches
Mail list logo
