rsync error: error in rsync protocol data stream (code 12) at io.c(140)
Hello, I am getting the following error: | rsync: open connection using rsh conn /usr/bin/rsync --server --sender -v . "/home/andrewm/test-rsync/tree/*" | large_file2 | write failed on large_file2 : Success:06 | rsync error: error in file IO (code 11) at receiver.c(271) | rsync: connection unexpectedly closed (201 bytes read so far) | rsync error: error in rsync protocol data stream (code 12) at io.c(140) I have only just subscribed to this mailing list, so apologies if I have missed any discussion on this topic. A MHonArc conversion of rsync.mbox (from rsync.samba.org) suggests I have. The 'patch' that has been mentioned, does it relate to this? If so, has it been applied to the source available at: rsync.samba.org? Else, how can I get hold of it and apply it? FYI: | andrewm@massachusetts:~/test-rsync$ rsync --version | rsync version 2.5.2 protocol version 26 | Copyright (C) 1996-2002 by Andrew Tridgell and others | <http://rsync.samba.org/> | Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, IPv6, | 64-bit system inums, 64-bit internal inums rsync was installed from Debian's 'testing' packages, i.e. not from source. | andrewm@connecticut:~$ ls -ltr /home/andrewm/test-rsync/tree/ | total 1425384 | -rw-r--r--1 andrewm staff80999190 Feb 25 16:56 large_file2 18 files, all the same size, all ascii randomish text just for testing. The files I intend to transfer don't need to be hidden from prying eyes, but would I benefit from using `ssh' as a more resilient method of communication than `rsh'? Any comments appreciated. Regards Andrew McGregor -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
rsync error: error in rsync protocol data stream (code 12) at io.c(140)
This is an extrememly old post, so it might not be of any use anymore. I encountered this same error, and the problem ended up being a full filesystem (my destination filled up before completion). rsync error: error in rsync protocol data stream (code 12) at io.c(140) Dave Dykstra dwd at bell-labs.com <mailto:rsync%40lists.samba.org?Subject=rsync%20error%3A%20error%20in%20 rsync%20protocol%20data%20stream%20%28code%2012%29%20at%20io.c%28140%29& In-Reply-To=3C7CC328.EBEFFDE1%40amtrak.co.uk> Thu Feb 28 05:54:15 EST 2002 * Previous message: rsync error: error in rsync protocol data stream (code 12) at io.c(140) <http://lists.samba.org/archive/rsync/2002-February/001717.html> * Next message: rsync error: error in rsync protocol data stream (code 12) at io.c(140) <http://lists.samba.org/archive/rsync/2002-February/001727.html> * Messages sorted by: [ date ] <http://lists.samba.org/archive/rsync/2002-February/date.html#1716> [ thread ] <http://lists.samba.org/archive/rsync/2002-February/thread.html#1716> [ subject ] <http://lists.samba.org/archive/rsync/2002-February/subject.html#1716> [ author ] <http://lists.samba.org/archive/rsync/2002-February/author.html#1716> The rsync code that prints that error on line 270 of receiver.c is printing strerror(errno), and that error message "Success:12" looks very strange to me. If the 12 indicates errno, that's an ENOMEM error. Is your system out of virtual address space? Maybe it is so low on memory that it's printing the default error message "Success" rather the real one. An argument against the out-of-virtual-memory theory is that I don't see write_file() calling malloc as a side effect anywhere. Maybe the kernel itself is out of memory. - Dave On Wed, Feb 27, 2002 at 11:29:44AM +, Andrew McGregor wrote: > Hi, > > I have installed 2.5.3pre1 but have (virtually) the same error: > > | write failed on large_file2 : Success:12 > | rsync error: error in file IO (code 11) at receiver.c(271) > | rsync: connection unexpectedly closed (201 bytes read so far) > | rsync error: error in rsync protocol data stream (code 12) at > io.c(151) > > The command I run is: > > | andrewm at massachusetts <http://lists.samba.org/mailman/listinfo/rsync> :~/test-rsync$ rsync -v --progress > conn:/home/andrewm/test-rsync/tree/* /home/andrewm/test-rsync/rsh_tree/ > > Are there other debug options I can use? Or possibly compile the source > differently to help prove/disprove this as a bug/local system problem? > > Regards > > Andrew McGregor John Greenfelder System Engineer II Lowes Companies (336) 658-3741 -- 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: rsync error: error in rsync protocol data stream (code 12) at io.c(140)
I haven't seen that symptom, but there's a very serious bug in rsync 2.5.2 that could conceivably be causing that. I suggest using version 2.5.3pre1 from the "preview" directory in the rsync sources area at rsync.samba.org. It is possible that Debian has already put out their own 2.5.2 that has the very bad bug solved though, I'm not sure. - Dave Dykstra On Tue, Feb 26, 2002 at 05:55:24PM +, Andrew McGregor wrote: > Hello, > > I am getting the following error: > > | rsync: open connection using rsh conn /usr/bin/rsync --server --sender > -v . "/home/andrewm/test-rsync/tree/*" > | large_file2 > | write failed on large_file2 : Success:06 > | rsync error: error in file IO (code 11) at receiver.c(271) > | rsync: connection unexpectedly closed (201 bytes read so far) > | rsync error: error in rsync protocol data stream (code 12) at > io.c(140) > > I have only just subscribed to this mailing list, so apologies if I have > missed any discussion on this topic. A MHonArc conversion of rsync.mbox > (from rsync.samba.org) suggests I have. The 'patch' that has been > mentioned, does it relate to this? If so, has it been applied to the > source available at: rsync.samba.org? Else, how can I get hold of it > and apply it? > > FYI: > > | andrewm@massachusetts:~/test-rsync$ rsync --version > | rsync version 2.5.2 protocol version 26 > | Copyright (C) 1996-2002 by Andrew Tridgell and others > | <http://rsync.samba.org/> > | Capabilities: 64-bit files, socketpairs, hard links, symlinks, > batchfiles, IPv6, > | 64-bit system inums, 64-bit internal inums > > rsync was installed from Debian's 'testing' packages, i.e. not from > source. > > | andrewm@connecticut:~$ ls -ltr /home/andrewm/test-rsync/tree/ > | total 1425384 > | -rw-r--r--1 andrewm staff80999190 Feb 25 16:56 large_file2 > 18 files, all the same size, all ascii randomish text just for > testing. > > The files I intend to transfer don't need to be hidden from prying eyes, > but would I benefit from using `ssh' as a more resilient method of > communication than `rsh'? > > Any comments appreciated. > > Regards > > Andrew McGregor > > -- > To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: rsync error: error in rsync protocol data stream (code 12) at io.c(140)
Hi, I have installed 2.5.3pre1 but have (virtually) the same error: | write failed on large_file2 : Success:12 | rsync error: error in file IO (code 11) at receiver.c(271) | rsync: connection unexpectedly closed (201 bytes read so far) | rsync error: error in rsync protocol data stream (code 12) at io.c(151) The command I run is: | andrewm@massachusetts:~/test-rsync$ rsync -v --progress conn:/home/andrewm/test-rsync/tree/* /home/andrewm/test-rsync/rsh_tree/ Are there other debug options I can use? Or possibly compile the source differently to help prove/disprove this as a bug/local system problem? Regards Andrew McGregor Dave Dykstra wrote: > > I haven't seen that symptom, but there's a very serious bug in rsync 2.5.2 > that could conceivably be causing that. I suggest using version 2.5.3pre1 > from the "preview" directory in the rsync sources area at rsync.samba.org. > It is possible that Debian has already put out their own 2.5.2 that has the > very bad bug solved though, I'm not sure. > > - Dave Dykstra > > On Tue, Feb 26, 2002 at 05:55:24PM +, Andrew McGregor wrote: > > Hello, > > > > I am getting the following error: > > > > | rsync: open connection using rsh conn /usr/bin/rsync --server --sender > > -v . "/home/andrewm/test-rsync/tree/*" > > | large_file2 > > | write failed on large_file2 : Success:06 > > | rsync error: error in file IO (code 11) at receiver.c(271) > > | rsync: connection unexpectedly closed (201 bytes read so far) > > | rsync error: error in rsync protocol data stream (code 12) at > > io.c(140) > > > > I have only just subscribed to this mailing list, so apologies if I have > > missed any discussion on this topic. A MHonArc conversion of rsync.mbox > > (from rsync.samba.org) suggests I have. The 'patch' that has been > > mentioned, does it relate to this? If so, has it been applied to the > > source available at: rsync.samba.org? Else, how can I get hold of it > > and apply it? > > > > FYI: > > > > | andrewm@massachusetts:~/test-rsync$ rsync --version > > | rsync version 2.5.2 protocol version 26 > > | Copyright (C) 1996-2002 by Andrew Tridgell and others > > | <http://rsync.samba.org/> > > | Capabilities: 64-bit files, socketpairs, hard links, symlinks, > > batchfiles, IPv6, > > | 64-bit system inums, 64-bit internal inums > > > > rsync was installed from Debian's 'testing' packages, i.e. not from > > source. > > > > | andrewm@connecticut:~$ ls -ltr /home/andrewm/test-rsync/tree/ > > | total 1425384 > > | -rw-r--r--1 andrewm staff80999190 Feb 25 16:56 large_file2 > > 18 files, all the same size, all ascii randomish text just for > > testing. > > > > The files I intend to transfer don't need to be hidden from prying eyes, > > but would I benefit from using `ssh' as a more resilient method of > > communication than `rsh'? > > > > Any comments appreciated. > > > > Regards > > > > Andrew McGregor > > > > -- > > To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync > > Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html > > -- > To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: rsync error: error in rsync protocol data stream (code 12) at io.c(140)
> | write failed on large_file2 : Success:12 > | rsync error: error in file IO (code 11) at receiver.c(271) > | rsync: connection unexpectedly closed (201 bytes read so far) > | rsync error: error in rsync protocol data stream (code 12) at io.c(151) Hi, I would like to humbly apologies ... one of my partitions may have become 100% full at some stage during the 'rsync'ing. I will run a few more tests to be sure. Maybe this could go on the FAQ as there must be other people as foolish as me around ;) or even in the wishlist for an error quoting 'disk full'? At least this brought to light potential problems with running 2.5.2 and pointing out an upgrade to 2.5.3pre1. Many thanks again. Andrew McGregor -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: rsync error: error in rsync protocol data stream (code 12) at io.c(140)
The rsync code that prints that error on line 270 of receiver.c is printing strerror(errno), and that error message "Success:12" looks very strange to me. If the 12 indicates errno, that's an ENOMEM error. Is your system out of virtual address space? Maybe it is so low on memory that it's printing the default error message "Success" rather the real one. An argument against the out-of-virtual-memory theory is that I don't see write_file() calling malloc as a side effect anywhere. Maybe the kernel itself is out of memory. - Dave On Wed, Feb 27, 2002 at 11:29:44AM +, Andrew McGregor wrote: > Hi, > > I have installed 2.5.3pre1 but have (virtually) the same error: > > | write failed on large_file2 : Success:12 > | rsync error: error in file IO (code 11) at receiver.c(271) > | rsync: connection unexpectedly closed (201 bytes read so far) > | rsync error: error in rsync protocol data stream (code 12) at > io.c(151) > > The command I run is: > > | andrewm@massachusetts:~/test-rsync$ rsync -v --progress > conn:/home/andrewm/test-rsync/tree/* /home/andrewm/test-rsync/rsh_tree/ > > Are there other debug options I can use? Or possibly compile the source > differently to help prove/disprove this as a bug/local system problem? > > Regards > > Andrew McGregor > > Dave Dykstra wrote: > > > > I haven't seen that symptom, but there's a very serious bug in rsync 2.5.2 > > that could conceivably be causing that. I suggest using version 2.5.3pre1 > > from the "preview" directory in the rsync sources area at rsync.samba.org. > > It is possible that Debian has already put out their own 2.5.2 that has the > > very bad bug solved though, I'm not sure. > > > > - Dave Dykstra > > > > On Tue, Feb 26, 2002 at 05:55:24PM +, Andrew McGregor wrote: > > > Hello, > > > > > > I am getting the following error: > > > > > > | rsync: open connection using rsh conn /usr/bin/rsync --server --sender > > > -v . "/home/andrewm/test-rsync/tree/*" > > > | large_file2 > > > | write failed on large_file2 : Success:06 > > > | rsync error: error in file IO (code 11) at receiver.c(271) > > > | rsync: connection unexpectedly closed (201 bytes read so far) > > > | rsync error: error in rsync protocol data stream (code 12) at > > > io.c(140) > > > > > > I have only just subscribed to this mailing list, so apologies if I have > > > missed any discussion on this topic. A MHonArc conversion of rsync.mbox > > > (from rsync.samba.org) suggests I have. The 'patch' that has been > > > mentioned, does it relate to this? If so, has it been applied to the > > > source available at: rsync.samba.org? Else, how can I get hold of it > > > and apply it? > > > > > > FYI: > > > > > > | andrewm@massachusetts:~/test-rsync$ rsync --version > > > | rsync version 2.5.2 protocol version 26 > > > | Copyright (C) 1996-2002 by Andrew Tridgell and others > > > | <http://rsync.samba.org/> > > > | Capabilities: 64-bit files, socketpairs, hard links, symlinks, > > > batchfiles, IPv6, > > > | 64-bit system inums, 64-bit internal inums > > > > > > rsync was installed from Debian's 'testing' packages, i.e. not from > > > source. > > > > > > | andrewm@connecticut:~$ ls -ltr /home/andrewm/test-rsync/tree/ > > > | total 1425384 > > > | -rw-r--r--1 andrewm staff80999190 Feb 25 16:56 large_file2 > > > 18 files, all the same size, all ascii randomish text just for > > > testing. > > > > > > The files I intend to transfer don't need to be hidden from prying eyes, > > > but would I benefit from using `ssh' as a more resilient method of > > > communication than `rsh'? > > > > > > Any comments appreciated. > > > > > > Regards > > > > > > Andrew McGregor > > > > > > -- > > > To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync > > > Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html > > > > -- > > To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync > > Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html > > -- > To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: rsync error: error in rsync protocol data stream (code 12) at io.c(140)
On Wed, Feb 27, 2002 at 02:57:59PM +, Andrew McGregor wrote: > > | write failed on large_file2 : Success:12 > > | rsync error: error in file IO (code 11) at receiver.c(271) > > | rsync: connection unexpectedly closed (201 bytes read so far) > > | rsync error: error in rsync protocol data stream (code 12) at io.c(151) > > Hi, > > I would like to humbly apologies ... one of my partitions may have become > 100% full at some stage during the 'rsync'ing. I will run a few more tests > to be sure. > > Maybe this could go on the FAQ as there must be other people as foolish as > me around ;) or even in the wishlist for an error quoting 'disk full'? Nobody else has reported this, and write() should return ENOSPC if the disk is full and it should print "No space left on device". Something else strange is going on. Was it on your root filesystem? Sometimes kernels can get confused when the root filesystem fills up. > At least this brought to light potential problems with running 2.5.2 and > pointing out an upgrade to 2.5.3pre1. - Dave Dykstra -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: rsync error: error in rsync protocol data stream (code 12) at io.c(140)
Dave Dykstra wrote: > > The rsync code that prints that error on line 270 of receiver.c is printing > strerror(errno), and that error message "Success:12" looks very strange to > me. If the 12 indicates errno, that's an ENOMEM error. Is your system out > of virtual address space? Maybe it is so low on memory that it's printing > the default error message "Success" rather the real one. An argument against > the out-of-virtual-memory theory is that I don't see write_file() calling > malloc as a side effect anywhere. Maybe the kernel itself is out of memory. > > - Dave > Hi, I'm unsure as to how I would test the above - but there were no other system messages, and nothing in the logs. Although with reference to 'virtual address space' I am concerned about any possible memory leaks somewhere in the system. Having said that the system was otherwise functioning as normal. Yes, it was writing to the root file system. I am unable to reproduce the error unless the partition is full. My target platform is Solaris as Debian/i386 is just my devpt box, so I will try to reproduce the error there. Providing I don't manage to reproduce the error on Solaris, I will be satisfied with the result, but are there any further tests anybody would like me to do on my Debian server to try and get to the bottom of it? Thank you and regards, Andy -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
Re: rsync error: error in rsync protocol data stream (code 12) at io.c(140)
Dave Dykstra wrote: > > The rsync code that prints that error on line 270 of receiver.c is printing > strerror(errno), and that error message "Success:12" looks very strange to > me. If the 12 indicates errno, that's an ENOMEM error. Is your system out > of virtual address space? Maybe it is so low on memory that it's printing > the default error message "Success" rather the real one. An argument against > the out-of-virtual-memory theory is that I don't see write_file() calling > malloc as a side effect anywhere. Maybe the kernel itself is out of memory. > > - Dave > Hi, I think the below extract from an ftp session between two Debian boxes proves this is not an rsync problem as the error is too similar to be anything else. The file is a ~500mb tarball. | ftp> put Disk1.tar.gz | local: Disk1.tar.gz remote: Disk1.tar.gz | 200 PORT command successful. | 150 Opening BINARY mode data connection for Disk1.tar.gz. | netout: Broken pipe | 452 Error writing file: Success. | ftp> [OT] This reminds me of Dr. Damian Conway's superposition Perl module where it returns both true and false at the same time ;) http://search.cpan.org/doc/DCONWAY/Quantum-Superpositions-1.03/lib/Quantum/Superpositions.pm | andrewm@massachusetts:~$ df -k | Filesystem 1k-blocks Used Available Use% Mounted on | /dev/hda6 1968588 1868644 0 100% / Unfortunately, I can't confirm whether this is Linux or Debian obfuscating things. Once again, apologies for any inconvenience. Regards Andy -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
