I am a new rsync user and it has been going fine as to nightly rsyncs. On one of the scripts I am getting two kind of errors: 1. @ERROR: chroot failed rsync: connection unexpectedly closed (34 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) and also on the same script to another server, I get no errors but the files are not being mirrored on the destination server. On my rsync log file it writes: building file list ... done wrote 6042 bytes read 100 bytes 12284.00 bytes/sec total size is 492329 speedup is 80.16 But the files are not being transffered. Any ideas? -Daniel
On Thu, Apr 15, 2004 at 07:14:47PM -0400, Daniel Teklu wrote:> 1. @ERROR: chroot failedThis probably means that the server isn't running as root. Either turn off chroot in the config file, or run rsync with more privs (and use the uid/gid options to bring them back down again).> building file list ... done > wrote 6042 bytes read 100 bytes 12284.00 bytes/sec > total size is 492329 speedup is 80.16This means the files are already up-to-date. Use at least 2 -v options to see them. ..wayne..
There are two things that bring that message. One is the inability to chroot. I think non-chrootable operating systems get their rsync configured so it never tries (and therefore, never fails). If you're on a real OS, you might be initiating the daemon as a non-root user (uid in the module doesn't matter). The more common cause, though, is an error in the "path = /whatever" entry for a module. You can't chroot to a place that doesn't exist. Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 conway@us.ibm.com 1. @ERROR: chroot failed rsync: connection unexpectedly closed (34 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165)> ...Any ideas?> ....