"Joe Casadonte" <[EMAIL PROTECTED]> wrote on 01/29/2007 02:39:52 PM:
> On Mon, 29 Jan 2007, Timothy J. Massey wrote: > > > So this should not be an issue. Am I missing something? > > Can you run rsync from the command line from the backuppc server > hitting the client machine? Something like: > > rsync --list-only [EMAIL PROTECTED]::[module-name] > rsync --list-only [EMAIL PROTECTED]::home No, for a couple of reasons: 1) The BackupPC server is running on CentOS (RHEL) 3.8. The latest version of rsync is 2.5.7, which does not support --list-only. I'll update to test and see, but... 2) I'm not sure that it's very conclusive. BackupPC doesn't use the rsync binary on the server. It uses File::RsyncP, a version of rsync rewritten in perl. It seems to me that the problem is between rsync and File:RsyncP. However, I'll try to update. Some people may not like it, though: I'll have to use a non-Red-Hat rsync! :) OK, here goes, from the BackupPC server: : # rsync --version rsync version 2.6.9 protocol version 29 Copyright (C) 1996-2006 by Andrew Tridgell, Wayne Davison, and others. <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, inplace, IPv6, 64-bit system inums, 64-bit internal inums # rsync --list-only [EMAIL PROTECTED]::ROOT Password: rsync: on remote machine: --list-only: unknown option rsync error: requested action not supported (code 4) at clientserver.c(473) rsync: read error: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(604) [receiver=2.6.9] So, it looks like --list-only is not supported by Red Hat's RHEL4 version of rsync, either. On the host side: # rsync --version rsync version 2.6.3 protocol version 28 Copyright (C) 1996-2004 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, inplace, IPv6, 64-bit system inums, 64-bit internal inums # rpm -ivh rsync-2.6.9-1.el3.rf.i386.rpm --force warning: rsync-2.6.9-1.el3.rf.i386.rpm: V3 DSA signature: NOKEY, key ID 6b8d79e6 Preparing... ########################################### [100%] 1:rsync ########################################### [100%] # rsync --version rsync version 2.6.9 protocol version 29 Copyright (C) 1996-2006 by Andrew Tridgell, Wayne Davison, and others. <http://rsync.samba.org/> Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, inplace, IPv6, 64-bit system inums, 64-bit internal inums Now, when I run rsync --list-only [EMAIL PROTECTED]::ROOT from the BackupPC server, it runs fine. For the record, I have always been able to do a transfer using the normal rsync binaries just fine, no matter what version of rsync or OS, without error. Again, I think that's because the problem is an issue between File::RsyncP and the remote rsync binary. Therefore, doing tests from the command-line won't help... But I've used multiple versions of the rsync binary (2.5.x, 2.6.3 RHEL and 2.6.9 generic) on the host side, and I've used different distros (Knoppix 3.7 and CentOS 3.8, fully updated), and different versions of File::RsyncP (0.52 and 0.68, the latest). I get the exact same error every time. Timothy J. Massey ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
