Re: Compression error? -- Inflate (token) returned -5
Paul Slootman wrote: On Fri 05 Sep 2008, Bas van Schaik wrote: Well, why not try upgrading to the latest? If that's not an option for you, what do you want us to do? Retro-actively fix your version by jumping in our time machine? ;-) You're right, I should have been more clear about this. I think there exist about three different threads about this problem, which all ended up in some rsync developer asking for the problematic files and the rsync user admitting that he had already deleted those. Since the cause of the problem is (AFAIK) still unknown, I assumed it wasn't fixed in the last few months. If you have reason to believe it actually _is_ fixed, I'll of course upgrade my rsync installation. But do you have reasons to believe this? I haven't seen any messages to the list about problems with compressed transfers on recent versions, so I have no reason to believe that the problems persist. I never had problems myself, so I can't personally say if it's changed. I've upgraded both client and server to rsync 3.0.3-2 from Ubuntu Intrepid and the problem still exists. Client reports: rsync: writefd_unbuffered failed to write 199 bytes [sender]: Connection reset by peer (104) inflate (token) returned -5 Since this is a production environment I'd like to stick to 3.0.3 (which is already newer than I'd like to use...) in stead of upgrading to 3.0.4, unless have very good reasons to believe it is really fixed in that last version. Regards, Bas -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Compression error? -- Inflate (token) returned -5
Hi all, A little less than a year ago I replied to this thread, but I'm still having similar problems. Again, the Inflate (token) returned -5 error occurred while syncing a file: 2008/09/04 22:11:20 [7017] name lookup failed for 172.26.3.224: Name or service not known 2008/09/04 22:11:20 [7017] connect from UNKNOWN (172.26.3.224) 2008/09/04 22:11:20 [7017] rsync to backups/tetra-networking/latest/ from [EMAIL PROTECTED] (172.26.3.224) 2008/09/04 22:11:20 [7017] receiving file list 2008/09/04 22:11:47 [7017] inflate (token) returned -5 2008/09/04 22:11:47 [7017] rsync error: error in rsync protocol data stream (code 12) at token.c(476) [receiver=2.6.9] 2008/09/04 22:11:47 [7017] rsync: connection unexpectedly closed (3301591 bytes received so far) [generator] 2008/09/04 22:11:47 [7017] rsync error: error in rsync protocol data stream (code 12) at io.c(454) [generator=2.6.9] Above you see a snippet of the server log, the client only reports: rsync: writefd_unbuffered failed to write 1 bytes [sender]: Connection reset by peer (104) rsync: connection unexpectedly closed (291575 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(454) [sender=2.6.9] And again, when using triple verbose mode the last match at lines almost matches the filesize of the file to transfer: (...) match at 68541840 last_match=68541840 j=8278 len=8280 n=0 match at 68550120 last_match=68550120 j=8279 len=8280 n=0 match at 68558400 last_match=68558400 j=8280 len=250 n=0 rsync: writefd_unbuffered failed to write 1 bytes [sender]: Connection reset by peer (104) (...) $ ls -la /backups/tetra-networking/latest/10.23.23.1/w/home/connie/Foto's BBQ 23-06-06.zip -rwxr--r-- 9 rsync nogroup 68558650 2008-08-19 23:42 /backups/tetra-networking/latest/10.23.23.1/w/home/connie/Foto's BBQ 23-06-06.zip (note that 68558400 + 250 = 68558650) The file to be transferred is quite small: about 66MB. However, if I try to sync the file on its own (not the whole directory structure) the error does not occur! The tail of the output of the successful rsync: $ rsync -ratzvvv --delete --compress-level=9 --timeout=3600 --password-file=/backups/rsync_wallis.secret client-original.zip [EMAIL PROTECTED]::tmp/ (...) match at 68550120 last_match=68550120 j=8279 len=8280 n=0 match at 68558400 last_match=68558400 j=8280 len=250 n=0 done hash search sending file_sum false_alarms=0 hash_hits=8281 matches=8281 sender finished client-original.zip send_files phase=1 send_files phase=2 send files finished total: matches=8281 hash_hits=8281 false_alarms=0 data=0 sent 104 bytes received 58005 bytes 16602.57 bytes/sec total size is 68558650 speedup is 1179.83 _exit_cleanup(code=0, file=main.c, line=977): about to call exit(0) Clearly it has something to do with the context which the file is in and not the contents of this single file. The only known workaround I know is disabling the compression... FYI: both client and server are using rsync 2.6.9 (from Ubuntu Hardy Heron). Does anyone have more information regarding this issue? Kind regards, -- Bas -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Compression error? -- Inflate (token) returned -5
Paul Slootman wrote: On Fri 05 Sep 2008, Bas van Schaik wrote: is disabling the compression... FYI: both client and server are using rsync 2.6.9 (from Ubuntu Hardy Heron). Does anyone have more information regarding this issue? Well, why not try upgrading to the latest? If that's not an option for you, what do you want us to do? Retro-actively fix your version by jumping in our time machine? ;-) You're right, I should have been more clear about this. I think there exist about three different threads about this problem, which all ended up in some rsync developer asking for the problematic files and the rsync user admitting that he had already deleted those. Since the cause of the problem is (AFAIK) still unknown, I assumed it wasn't fixed in the last few months. If you have reason to believe it actually _is_ fixed, I'll of course upgrade my rsync installation. But do you have reasons to believe this? -- Bas -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
rsync reports some files could not be transferred (code 23) when problems occur with password-file
Hi all, I think I just found a small bug in rsync... It has costed me about half an hour searching for a problem which actually didn't exist! If you use rsync like this: rsync --password-file=/tmp/non-existing-file /tmp/somefile [EMAIL PROTECTED]::tmp/ Rsync will ask for the password since the supplied file doesn't exist: rsync: could not open password file /tmp/non-existing-file: No such file or directory (2) Password: rsync error: some files could not be transferred (code 23) at main.c(977) [sender=2.6.9] But actually, the file '/tmp/somefile' did get transferred to server 'bar'. When not supplying the bogus password file, rsync will again ask for the password, but not report the code 23. Bottom line: rsync reports a code 23 when there's a problem with the password file, even when the right password is supplied and files are transferred. Regards, -- Bas van Schaik -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Compression error?
/ from [EMAIL PROTECTED] (192.168.0.221) 2007/11/01 13:15:28 [10684] receiving file list 2007/11/01 13:18:23 [10684] inflate (token) returned -5 2007/11/01 13:18:23 [10684] rsync error: error in rsync protocol data stream (code 12) at token.c(476) [receiver=2.6.9] 2007/11/01 13:18:23 [10684] rsync: connection unexpectedly closed (197 bytes received so far) [generator] 2007/11/01 13:18:23 [10684] rsync error: error in rsync protocol data stream (code 12) at io.c(453) [generator=2.6.9] As you can see, the last match at (...) line at the client mentions 1077119568, which actually looks a lot like 1077162396 (the size of article_attachment.MYD on the server). Other files causing similar problems were also very large ( 1G), also existed both on client and server and needed a partial transfer. The execution of a rsync with five -v options flooded my console even more, but didn't provide more details on the actual inflate error. To be able to reproduce this problem in the future I created copies of both the client and server article_attachment.MYD. If needed, I might be able to supply those two files to a rsync developer, but I will need to ask permission for that. This is all the information I have at this moment, please do not hesitate to ask me for more information when needed. It would be really nice to finally fix this issue! Kind regards, -- Bas van Schaik signature.asc Description: OpenPGP digital signature -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Receive more information about transfer problems in server log?
Hi Dave, Dave Markham wrote: What are you the Rsync options you are using ? Clientside: rsync -vratz --password-file=somefile --force --delete-excluded --delete --exclude-from=somefile --files-from=somefile Serverside: rsync --no-detach --daemon --config /etc/rsyncd.conf with rsyncd.conf: motd file = /etc/rsyncd.motd log file = /var/log/rsync/rsyncd.log pid file = /var/run/rsyncd.pid secrets file = /etc/rsyncd.secrets read only = no uid = rsync use chroot = yes transfer logging = yes timeout = 14400 max connections = 25 incoming chmod = u+rw Thanks for your help! Regards, -- Bas On 2/23/07, *Bas van Schaik* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hi all, I'm probably using the most basic rsync-setup: just running the rsync-daemon and use plain transfers (no encryption or other shells, plain rsync). Transfer logging is enabled. I've got a lot of client machines rsyncing their backups, both Linux and Windows. For some rsyncs, the log tells me this: 2007/02/23 02:42:04 [29077] connect from ***.nl (*.*.*.*) 2007/02/23 02:42:05 [29077] rsync to 192168162 from [EMAIL PROTECTED] (*.*.*.*) 2007/02/23 02:42:05 [29077] receiving file list 2007/02/23 02:42:06 [29077] IO error encountered -- skipping file deletion 2007/02/23 02:42:06 [29077] rsync / 2007/02/23 02:42:06 [29077] rsync error: some files could not be transferred (code 23) at main.c(872) [generator=2.6.9] (all entries about PID 29077) I can see that something went wrong during this sync. But what exactly? Which files could not be transferred exactly, and why? According to the error code (23), some files where partially transferred due to an error, but there are no files in the transfer log! And which error did occur exactly? Of course, I can browse the client logfiles every day, but that isn't really an option: there are more than 50 clients! Can anyone help me getting more information in my server log about transfer problems? Thanks! Regards, -- Bas van Schaik -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Receive more information about transfer problems in server log?
Hi all, I'm probably using the most basic rsync-setup: just running the rsync-daemon and use plain transfers (no encryption or other shells, plain rsync). Transfer logging is enabled. I've got a lot of client machines rsyncing their backups, both Linux and Windows. For some rsyncs, the log tells me this: 2007/02/23 02:42:04 [29077] connect from ***.nl (*.*.*.*) 2007/02/23 02:42:05 [29077] rsync to 192168162 from [EMAIL PROTECTED] (*.*.*.*) 2007/02/23 02:42:05 [29077] receiving file list 2007/02/23 02:42:06 [29077] IO error encountered -- skipping file deletion 2007/02/23 02:42:06 [29077] rsync / 2007/02/23 02:42:06 [29077] rsync error: some files could not be transferred (code 23) at main.c(872) [generator=2.6.9] (all entries about PID 29077) I can see that something went wrong during this sync. But what exactly? Which files could not be transferred exactly, and why? According to the error code (23), some files where partially transferred due to an error, but there are no files in the transfer log! And which error did occur exactly? Of course, I can browse the client logfiles every day, but that isn't really an option: there are more than 50 clients! Can anyone help me getting more information in my server log about transfer problems? Thanks! Regards, -- Bas van Schaik -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
