Rsync error on client end: unexpected tag 3 [sender] rsyncerror: error in rsync protocol data stream (code 12) atio.c(843) [sender]

[Anthony Sadler]

Hi Wayne:

Just letting you know, you were right about that patch; it wasn't installed correctly. 

What we had tried was to get it compiled inside of a RPM and install from the RPM. Something went wrong there, we don't know what. After you told us that it had gone wrong, we went and download the nightly build from CVS and compiled that and installed it.

After that, it all worked. Our backups all went through with no problems. 

Thank you very much for your effort and for the very short time with which you came back to me with a fix. We had all been a bit uncomfortable with our backups not working :P

Anthony Sadler
Far Edge Technology
w: (02) 8425 1400
 
-----Original Message-----
From: rsync-bounces+anthonys-rsync=faredge.com.au at lists.samba.org [mailto:rsync-bounces+anthonys-rsync=faredge.com.au at lists.samba.org] On Behalf Of Wayne Davison
Sent: Wednesday, 3 May 2006 16:15 
To: Anthony Sadler
Cc: rsync at lists.samba.org
Subject: Re: Rsync error on client end: unexpected tag 3 [sender] rsyncerror: error in rsync protocol data stream (code 12) atio.c(843) [sender]

On Wed, May 03, 2006 at 11:58:07AM +1000, Anthony Sadler wrote:
> Notice /etc/localtime not being able to open? 

That happens because you're using "use chroot = yes".  When rsync is
running inside a chroot jail, it cannot access files that exist outside
the rsync module's path.

Rsync attempts to handle the timezone situation by using localtime()
prior to the chroot call, but on some systems this is not enough to keep
the library code really happy.  I've checked in a change that makes
rsync also call strftime() prior to the chroot (for those systems that
are configured to use strftime()).

..wayne..