Hello, Since our server migration from OES1 (rsync-3.0.2-2.1) to OES2 (rsync-3.0.6-3.1), rsync backup do not work anymore. Here is some explanation : With a full verbose mode on the source server : rsync: writefd_unbuffered failed to write 631 bytes to socket [sender]: Broken pipe (32) rsync: connection unexpectedly closed (786 bytes received so far) [sender] _exit_cleanup(code=12, file=io.c, line=600): entered rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.6] _exit_cleanup(code=12, file=io.c, line=600): about to call exit(12) On the rsyncd.log file to the remote server : 2009/12/21 15:50:43 [22219] unknown message 36:1587200 [generator] 2009/12/21 15:50:43 [22219] rsync error: error in rsync protocol data stream (code 12) at io.c(475) [generator=3.0.2] After many hours of search on similar subjects, nothing found to solve it. Any Ideas ? Regards, Thibaud . -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20091221/cebf1493/attachment.html>
On Mon 21 Dec 2009, Aubert Thibaud wrote:> > Since our server migration from OES1 (rsync-3.0.2-2.1) to OES2 > (rsync-3.0.6-3.1), rsync backup do not work anymore.> rsync error: error in rsync protocol data stream (code 12) at io.c(600) > [sender=3.0.6] > _exit_cleanup(code=12, file=io.c, line=600): about to call exit(12) > > On the rsyncd.log file to the remote server : > > 2009/12/21 15:50:43 [22219] unknown message 36:1587200 [generator] > 2009/12/21 15:50:43 [22219] rsync error: error in rsync protocol data > stream (code 12) at io.c(475) [generator=3.0.2]Apparently only one of the servers was migrated to OES2 (whatever that may be)? Paul
On Mon, Dec 21, 2009 at 8:27 AM, Aubert Thibaud <taubert at sopragroup.com> wrote:> 2009/12/21 15:50:43 [22219] unknown message 36:1587200 [generator]That's an error from the generator complaining about the data coming over the local pipe from the receiver. If that data is messed up, things have to be in pretty bad shape. My first inclination would be to check the patches that OES2 applied to rsync, but some simple googling failed to find the source code for OES2. You could try grabbing the official rsync source and building your own rsync executable. If the issue goes away using that (on the sending side that that was upgraded to 3.0.6), then the problem is with the patches that OES2 applied to rsync. The only way I know to mess up the data going from the receiver to the generator (which only affects 3.0.x) is for the sender to send a MSG_IO_ERROR before the end of the sending of an incremental file list's data, but the stock rsync does not do that. ..wayne..