hi all, running a transfer from a rsync client (3.0.6) to a rsync server (3.1.0), I get the following message: $ RSYNC_PASSWORD="oooo" rsync -avn --delete /xx/yy/ rsync:// aaa at bbb.com/ccc/ddd/ <<motd displayed>> sending incremental file list unknown message 0:0 [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(436) [sender=3.0.6] Server logs says: Oct 2 10:47:36 bbb rsyncd[3947]: receiving file list Oct 2 10:47:36 bbb rsyncd[3947]: rsync: connection unexpectedly closed (4096 bytes received so far) [Receiver] Oct 2 10:47:36 bbb rsyncd[3947]: rsync error: error in rsync protocol data stream (code 12) at io.c(226) [Receiver=3.1.0] Running the same command with a rsync 3.1.0 client works fine. Did I miss something about compatibility between protocols ? thanks in advance, Tom. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20131002/c2de70c8/attachment.html>
more information about my last post : removing the trailing slash from the source folder will make the transfer work. ie : $ rsync -avn --delete /xx/yy rsync://aaa at bbb.com/ccc/ddd/ ..works. But this won't work: $ rsync -avn --delete /xx/yy/ rsync://aaa at bbb.com/ccc/ddd/ Password: sending incremental file list unknown message 0:0 [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(436) [sender=3.0.6] Also, same problem is encountered when client is 3.0.9 (and server 3.1.0. Same commands works fine with a 3.0.9 server). Any clue ? thanks Tom 2013/10/2 thomas veymont <thomas.veymont at gmail.com>> hi all, > > running a transfer from a rsync client (3.0.6) to a rsync server (3.1.0), > I get the following message: > > $ RSYNC_PASSWORD="oooo" rsync -avn --delete /xx/yy/ rsync:// > aaa at bbb.com/ccc/ddd/ > > <<motd displayed>> > > sending incremental file list > unknown message 0:0 [sender] > rsync error: error in rsync protocol data stream (code 12) at io.c(436) > [sender=3.0.6] > > Server logs says: > > Oct 2 10:47:36 bbb rsyncd[3947]: receiving file list > Oct 2 10:47:36 bbb rsyncd[3947]: rsync: connection unexpectedly closed > (4096 bytes received so far) [Receiver] > Oct 2 10:47:36 bbb rsyncd[3947]: rsync error: error in rsync protocol > data stream (code 12) at io.c(226) [Receiver=3.1.0] > > Running the same command with a rsync 3.1.0 client works fine. > Did I miss something about compatibility between protocols ? > > thanks in advance, > Tom. >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20131002/98c82f6e/attachment.html>
On Wed, Oct 2, 2013 at 3:53 AM, thomas veymont <thomas.veymont at gmail.com>wrote:> sending incremental file list > unknown message 0:0 [sender] >I assume your daemon has a timeout option set, since the newest rsync is using message 0:0 as a keep-alive signal (as it used to do in the olden days). It would appear that a protocol 30 sender (but not receiver) cannot handle that do-nothing message, so we'll need to tweak the keep-alive code a bit for better backward compatibility. Can you try the following patch for 3.1.0? http://opencoder.net/keep-alive.diff ..wayne.. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.samba.org/pipermail/rsync/attachments/20131003/eacea13f/attachment.html>