From: Craig B. <cba...@us...> - 2004-08-30 05:44:32
|
MR writes: > Started receiving the errors below without any intentional changes. Any > ideas of how to resolve? > > Connected to 192.168.1.101:873, remote version 28 > > [snip] > > Remote[1]: rsync: Error parsing options: option may be supported on client but not on server? I would guess the client rsync was upgraded to 2.6.3pre1. See the email below. Unfortunately this version changed its argument parsing, rendering it incompatible with the way BackupPC passes the exclude options. Rsync has been fixed in CVS, but I don't know when the next release will be. Assuming my hypothesis is correct, the best option is to downgrade the client to rsync 2.6.2. Craig ---------- Forwarded message ---------- To: Kevin Currie <kc...@ci...> From: Craig Barratt <cba...@us...> Cc: bac...@li... Date: Sun, 29 Aug 2004 13:52:51 -0700 Subj: Re: (solved, sort of) was: Re: [BackupPC-users] Excludes causes all backups to fail... > Craig Barratt wrote: > > | I'm surprised rsync would change in a manner that would not be > | backward compatible. I follow the rsync mail list, but maybe > | not closely enough. > I am too! > > | Does this bug happen with CVS rsync talking to CVS rsync? If so, that's > | something we should take up on the rsync mail list. Perhaps I need to > | delve into the CVS code a little to understand what has changed. > Yes, it happens with CVS->CVS, as well as release->CVS I believe too. This issue should now be resolved. File::RsyncP passes the exclude arguments to the server/sender via ARGV, rather than via the socket interface. ARGV support for server/sender exclude arguments was removed in rsync CVS, since it wasn't a supported feature. But the rsync developers recently re-added support at our request. 2.6.3pre1 does not include the fix, but the next release should have excludes that work correctly. See: https://bugzilla.samba.org/show_bug.cgi?id=1660 I'm also updating File::RsyncP to implement excludes in the correct way, via the socket interface, rather than exploiting a non-supported feature in rsync. Craig |
From: Craig B. <cba...@us...> - 2004-08-31 02:52:40
|
MR writes: > I am using rsync 2.6.2 protocol version 28 and backuppc 2.1.0. Any > other thoughts? This is a great product and I'm anxious to get this > working again. Sorry to ask again, but are you really sure you have checked the rsync version running on the client (not the BackupPC server)? I don't know how that error can happen with rsync 2.6.2, but it will happen with slightly older rsync CVS or rsync 2.6.3pre1 on the client. Craig |
From: MR <rud...@co...> - 2004-08-31 03:03:10
|
My apologies...I had 2 versions of rsync loaded. The one I checked was 2.6.2 and the one referenced in my config file was 2.6.3pre1. When I downgraded, everything was working again. Thanks for the help and a great product. On Mon, 2004-08-30 at 21:52, Craig Barratt wrote: > MR writes: > > > I am using rsync 2.6.2 protocol version 28 and backuppc 2.1.0. Any > > other thoughts? This is a great product and I'm anxious to get this > > working again. > > Sorry to ask again, but are you really sure you have checked the > rsync version running on the client (not the BackupPC server)? > > I don't know how that error can happen with rsync 2.6.2, but > it will happen with slightly older rsync CVS or rsync 2.6.3pre1 > on the client. > > Craig -- MR <rud...@co...> |
From: MR <rud...@co...> - 2004-08-30 23:44:44
|
I am using rsync 2.6.2 protocol version 28 and backuppc 2.1.0. Any other thoughts? This is a great product and I'm anxious to get this working again. On Mon, 2004-08-30 at 00:44, Craig Barratt wrote: > MR writes: > > > Started receiving the errors below without any intentional changes. Any > > ideas of how to resolve? > > > > Connected to 192.168.1.101:873, remote version 28 > > > > [snip] > > > > Remote[1]: rsync: Error parsing options: option may be supported on client but not on server? > > I would guess the client rsync was upgraded to 2.6.3pre1. See the > email below. > > Unfortunately this version changed its argument parsing, rendering > it incompatible with the way BackupPC passes the exclude options. > > Rsync has been fixed in CVS, but I don't know when the next release > will be. > > Assuming my hypothesis is correct, the best option is to downgrade the > client to rsync 2.6.2. > > Craig > > ---------- Forwarded message ---------- > To: Kevin Currie <kc...@ci...> > From: Craig Barratt <cba...@us...> > Cc: bac...@li... > Date: Sun, 29 Aug 2004 13:52:51 -0700 > Subj: Re: (solved, sort of) was: Re: [BackupPC-users] Excludes causes all backups to fail... > > > Craig Barratt wrote: > > > > | I'm surprised rsync would change in a manner that would not be > > | backward compatible. I follow the rsync mail list, but maybe > > | not closely enough. > > I am too! > > > > | Does this bug happen with CVS rsync talking to CVS rsync? If so, that's > > | something we should take up on the rsync mail list. Perhaps I need to > > | delve into the CVS code a little to understand what has changed. > > Yes, it happens with CVS->CVS, as well as release->CVS I believe too. > > This issue should now be resolved. File::RsyncP passes the exclude > arguments to the server/sender via ARGV, rather than via the socket > interface. ARGV support for server/sender exclude arguments was > removed in rsync CVS, since it wasn't a supported feature. But the > rsync developers recently re-added support at our request. 2.6.3pre1 > does not include the fix, but the next release should have excludes > that work correctly. See: > > https://bugzilla.samba.org/show_bug.cgi?id=1660 > > I'm also updating File::RsyncP to implement excludes in the correct > way, via the socket interface, rather than exploiting a non-supported > feature in rsync. > > Craig -- MR <rud...@co...> |