Timothy J. Massey wrote:
I have had a bug with BackupPC, rsync and RHEL4 for some time now. I
blindly assumed that this bug had been fixed in the last year or so. It
turns out it has not.
BackupPC Configuration:
BackupPC 3.0beta3 running on CentOS 3.8 with latest updates
Host
Les Mikesell [EMAIL PROTECTED] wrote on 01/29/2007 12:35:29 PM:
Timothy J. Massey wrote:
I have had a bug with BackupPC, rsync and RHEL4 for some time now. I
blindly assumed that this bug had been fixed in the last year or
so. It
turns out it has not.
BackupPC
[EMAIL PROTECTED] wrote on 01/29/2007
01:25:06 PM:
Les Mikesell [EMAIL PROTECTED] wrote on 01/29/2007 12:35:29 PM:
That's not the stock rsync package for RHEL4. The changed behavior of
rsync has been discussed on the list before in the context of distros
that include it:
[EMAIL PROTECTED] wrote on 01/29/2007
01:40:56 PM:
Or, you could put the stock package back - the RHEL guys get
some of
this stuff right...
Well, the rsync package for RHEL4 didn't work, and *then* I
upgraded to
a standard rsync package. It's not like I randomly go
Timothy J. Massey wrote:
Another failure. And here's the log:
2007-01-29 13:41:49 full backup started for directory ROOT
2007-01-29 14:19:55 Got fatal error during xfer (Child exited prematurely)
2007-01-29 14:20:00 Backup aborted (Child exited prematurely)
2007-01-29 14:20:00 Saved
Les Mikesell [EMAIL PROTECTED] wrote on 01/29/2007 04:21:51 PM:
Timothy J. Massey wrote:
Another failure. And here's the log:
2007-01-29 13:41:49 full backup started for directory ROOT
2007-01-29 14:19:55 Got fatal error during xfer (Child exited
prematurely)
2007-01-29
Timothy J. Massey wrote:
Remember, this happens on *3* different servers, with 3 different
BackupPC servers. This is *not* related to a unique property of the
individual server. This is *very* related to RHEL4, instead of RHEL3.
Like I said, we upgraded a server from 3 to 4: used to
[EMAIL PROTECTED] wrote on 01/29/2007
04:52:15 PM:
Timothy J. Massey wrote:
Remember, this happens on *3* different servers, with 3 different
BackupPC servers. This is *not* related to a unique property of the
individual server. This is *very* related to RHEL4, instead of RHEL3.
Maybe I shouldn't chime in, because I've only been half following this
thread, but I can't help wondering if you've looked into all the
firewall/timeout possibilities? Sometimes those settings get hosed during
an upgrade too.
ck
Les Mikesell wrote:
Timothy J. Massey wrote:
Remember, this
Timothy J. Massey wrote:
lib/modules/2.6.9-5.EL/kernel/drivers/parport/parport_cs.ko
Read EOF: No route to host
That's an odd network error. What's between these boxes?
--
Les Mikesell
[EMAIL PROTECTED]
-
Take
[EMAIL PROTECTED] wrote:
Maybe I shouldn't chime in, because I've only been half following this
thread, but I can't help wondering if you've looked into all the
firewall/timeout possibilities? Sometimes those settings get hosed during
an upgrade too.
Not a bad thing to look into. I
[EMAIL PROTECTED] wrote on 01/29/2007
07:01:03 PM:
Also, you might crank up the timeout settings for just the failing hosts
and see if it allows your backups to run longer before failing. Your
failures are right about 20 minutes into them, which is a suspiciously
round number.
Timothy J. Massey wrote:
Les Mikesell [EMAIL PROTECTED] wrote on 01/29/2007 06:31:03 PM:
Timothy J. Massey wrote:
lib/modules/2.6.9-5.EL/kernel/drivers/parport/parport_cs.ko
Read EOF: No route to host
That's an odd network error. What's between these boxes?
A switch and a
BackupPC XferLog.0:
# tail XferLog.0
create 744 0/0 47604
lib/modules/2.6.9-5.EL/kernel/drivers/parport/parport.ko
create 744 0/08716
lib/modules/2.6.9-5.EL/kernel/drivers/parport/parport_cs.ko
Read EOF: No route to host
No route to host indicates
Joe Casadonte [EMAIL PROTECTED] wrote on 01/29/2007
10:42:32 PM:
On Mon, 29 Jan 2007, Timothy J. Massey wrote:
[EMAIL PROTECTED] wrote on 01/29/2007
07:01:03 PM:
Also, you might crank up the timeout settings for just the
failing hosts and see if it allows your backups to
15 matches
Mail list logo
