From: Villalovos, J. L <joh...@in...> - 2006-05-24 21:48:31
|
Thanks a lot for the info. I will try it out. John Craig Barratt <mailto:cba...@us...> wrote: > John writes: >=20 >> I am experiencing the problem of "fileListReceive failed" on my >> BackupPC server when connecting to one client that is running the >> 2.6.7 rsync server. Downgrading rsync on the client fixed the >> problem.=20 >>=20 >> It appears similar to this issue: >>=20 > http://sourceforge.net/mailarchive/forum.php?thread_id=3D1007687 > 9&forum_id >> =3D503 >>=20 >> Is anyone here aware of that issue and is anyone working on fixing >> it?=20 >>=20 >> I know that in my case if I used the rsync command line client I did >> not have any problems connecting to the newer rsync server, so it >> appears to be something with perlrsync. >=20 > It appears the file list wire format changed in some way > that I haven't yet investigated. >=20 > Here's a workaround: >=20 > ---------- Forwarded message ---------- > To: bac...@li... > From: Vincent Ho <vi...@fs...> > Date: Fri, 14 Apr 2006 23:18:45 +1000 > Subj: [BackupPC-users] Breakage with rsync 2.6.7 >=20 > Hi all, >=20 > Just a tip for anyone else... >=20 > rsync 2.6.7 has changed the meaning of the --devices option > to only mean > device nodes[1], not FIFOs/sockets (a new option --specials instructs > rsync to copy them). This caused filelistReceive failures for us on a > client machine running Debian testing, which has 2.6.7. For others it > seems to have caused segfaults when their backup hits a > FIFO/socket[2].=20 >=20 > The -D option to rsync does what we want though, it means --devices on > older rsyncs and --devices --specials on 2.6.7+. I've changed our > $Conf{RsyncArgs} to use -D rather than --devices and things > have worked > since, and suggest we do the same to the shipped version of the > config file.=20 >=20 >=20 > Vince >=20 > [1] http://rsync.samba.org/ftp/rsync/rsync-2.6.7-NEWS > [2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D358319 |