DO NOT REPLY [Bug 6032] error in rsync protocol data stream
https://bugzilla.samba.org/show_bug.cgi?id=6032 --- Comment #4 from m...@mattmccutchen.net 2009-01-15 18:02 CST --- That is strange, but the output does seem to indicate pretty clearly that rsync is not the thing closing the connection. It's possible that the file is triggering a data-dependent bug in ssh or even the network (but that seems unlikely because ssh would be encrypting with a different random key each time). In any case, you could see whether rsync fails in the same way when you do any of the following: - Remove the -z option. - Transfer using an rsync daemon instead of ssh (unless the file is secret). - Transfer the file between a different pair of hosts. - Make a copy of the file, modify it slightly (e.g., modify a few bytes or slightly lengthen or shorten it), and transfer that. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- 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
DO NOT REPLY [Bug 6032] error in rsync protocol data stream
https://bugzilla.samba.org/show_bug.cgi?id=6032 --- Comment #3 from rm...@lexiconn.com 2009-01-13 23:26 CST --- ok, just seems strange that the rsync fails every time on the same dovecot.patched.tar.gz file. Any pointers on how to t/s would be appreciated. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- 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
DO NOT REPLY [Bug 6032] error in rsync protocol data stream
https://bugzilla.samba.org/show_bug.cgi?id=6032 m...@mattmccutchen.net changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Comment #2 from m...@mattmccutchen.net 2009-01-13 23:10 CST --- It looks like neither rsync process intentionally closed the connection, so it must have been dropped by the network. This is not a bug in rsync. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- 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
DO NOT REPLY [Bug 6032] error in rsync protocol data stream
https://bugzilla.samba.org/show_bug.cgi?id=6032 --- Comment #1 from rm...@lexiconn.com 2009-01-13 22:06 CST --- Created an attachment (id=3875) --> (https://bugzilla.samba.org/attachment.cgi?id=3875&action=view) rsync-debug output (last 200 lines) This is the last 200 lines from the 10 MB rsync-debug output file. I was not able to get a core dump. If you need anything else, please let me know. The rsync fails on the same file/location every time. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- 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
DO NOT REPLY [Bug 6032] New: error in rsync protocol data stream
https://bugzilla.samba.org/show_bug.cgi?id=6032 Summary: error in rsync protocol data stream Product: rsync Version: 3.0.4 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: way...@samba.org ReportedBy: rm...@lexiconn.com QAContact: rsync...@samba.org Command: /usr/bin/rsync -aze /usr/local/ssh/bin/ssh --hard-links --force --ignore-errors --numeric-ids --delete --exclude=/sys --exclude=/proc --exclude=/var/named/chroot/proc --exclude=/home4 --exclude=/home5 --exclude=/backup --exclude=/var/log --exclude=/home/logs --exclude=/home2/logs/ $server:/ /home/backup/$short The error happens at the same spot during the rsync copy: Read from remote host $server: Connection reset by peer rsync: connection unexpectedly closed (16892096 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(632) [receiver=3.0.4] rsync: connection unexpectedly closed (408 bytes received so far) [generator] rsync error: unexplained error (code 255) at io.c(632) [generator=3.0.4] -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- 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
DO NOT REPLY [Bug 5795] error in rsync protocol data stream (code 12) at io.c(632) [sender=3.0.4]
https://bugzilla.samba.org/show_bug.cgi?id=5795 --- Comment #1 from [EMAIL PROTECTED] 2008-09-27 18:23 CST --- It turns out there was clearly not enough space on the destination. The copy was going to take 20GB, and after the crash there was still 1GB on the destination, so I thought this was probably a protocol bug rather than a problem with running out of space. Perhaps what this is is a situation where the remote end should have sent back an indication that it was out of space and should have shut down gracefully. But there is another problem here: the two ends should start out by negotating whether there is enough space for the copy. In a better world, the destination OS would give the rsync process the ability to atomically grab disk resources up front to be used for the files and folders it creates, and if that fails, the remote rsync would tell the UI rsync no dice. Or how about this: writing the destination files could be transaction in the OS file system! Nah. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- 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
DO NOT REPLY [Bug 5795] New: error in rsync protocol data stream (code 12) at io.c(632) [sender=3.0.4]
https://bugzilla.samba.org/show_bug.cgi?id=5795 Summary: error in rsync protocol data stream (code 12) at io.c(632) [sender=3.0.4] Product: rsync Version: 3.0.4 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: blocker Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] 0 424 Z% rsync -av --sparse --progress --partial /Users/yost/Documents/VMWare/winxp.vmwarevm /Volumes/x/vmware sending incremental file list winxp.vmwarevm/ winxp.vmwarevm/winxp.vmdk 1578172416 17% 11.08MB/s0:10:35 rsync: writefd_unbuffered failed to write 4 bytes [sender]: Broken pipe (32) rsync: connection unexpectedly closed (32 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(632) [sender=3.0.4] 12 425 Z% rsync --version rsync version 3.0.4 protocol version 30 Copyright (C) 1996-2008 by Andrew Tridgell, Wayne Davison, and others. Web site: http://rsync.samba.org/ Capabilities: 64-bit files, 32-bit inums, 32-bit timestamps, 64-bit long ints, socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace, append, ACLs, xattrs, iconv, symtimes rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. 0 426 Z% -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- 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: error in rsync protocol data stream
Richard Jones wrote: Help. This one's defeated me so far. I'm tring to push files from from a local Ubuntu 6.06 server to a remote Ubuntu 6.06 server using rsync (v 2.6.6 installed on both via apt-get). Every time I get the same eg: Not much help so far :-( I've managed to isolate the problem somewhat, but am still baffled. I have 4 more-or-less identical setups which I have experimented with pushing files between. Two remote VPS servers can transfer files in either direction OK, and both can push files to my local server OK, but my local server cannot transfer files to either remote server. But it can transfer files to a local VMware server located on the same network. From this I conclude there is something interfering with file transfers from my local network to the outside - a firewall perhaps? The rsync message can get across the divide, as it generates a remote response, but no files ever get transferred. There is nothing obvious on the local server IP tables, but the router has some rules for port forwarding inbound port 22 to the local server. I don't see why it should prevent outbound rsync file transfer, since it doesn't block outbound mail, but is there something in the router config I should examine more closely? -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
error in rsync protocol data stream
Help. This one's defeated me so far. I'm tring to push files from from a local Ubuntu 6.06 server to a remote Ubuntu 6.06 server using rsync (v 2.6.6 installed on both via apt-get). Every time I get the same eg: building file list ... 4 files to consider ./ Demo1.plt 63459 100%7.32MB/s0:00:00 (1, 50.0% of 4) Test.plt 1280 100% 208.33kB/s0:00:00 (2, 75.0% of 4) USA_wp.txt 39032 100%2.66MB/s0:00:00 (3, 100.0% of 4) .. very long pause ... then: Read from remote host : Connection timed out rsync: connection unexpectedly closed (84 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(434) When there are new sub-directories involved, they get created OK on the remote server (proving we get a vaild connection), but no files get transfered. So I tried synch'ing just a single file, and found that a text file of a few kilobytes transferred OK, but once it reached a few tens of kilobytes, it no longer transferred and I got the behaviour above. I did have denyhosts running, which caused problems by adding my IP address to hosts.deny, but I removed it and killed the process but it makes no difference. There is a reference to this behaviour in the rsync FAQ (the transfer fails to finish), but I'm afraid I can't follow the information supplied. Presumably it *is* possible to rsync between 2 Ubuntu Dapper servers? -- 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 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: error in rsync protocol data stream (code 12) at io.c(463) on HP-UX 11.23
On Mon 11 Sep 2006, Bernhard Wesely wrote:
> [6951] getdents(6, 0x4003d820, 16384) .. = 152
> [6951] stat64("/test", 0x7fff84e0) . = 0
> [6951] getdents(6, 0x4003d820, 16384) .. = 0
> [6951] close(6) = 0
> [6951] Received signal 11, SIGSEGV, in user mode, [SIG_DFL], partial
> ---
>
> the only interesting thing in my opinion is the line:
> [6951] open("../", O_RDONLY|0x20, 026540)
Well, IMHO the interesting thing is the SIGSEGV, which causes the
process to die, which results in the "prococol error".
It would be interesting to see where the SIGSEGV occurs; this probably
entails getting a core dump and using a debugger to see what goes wrong.
Paul Slootman
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
error in rsync protocol data stream (code 12) at io.c(463) on HP-UX 11.23
Hello,
We discovered a slight problem with rsync 2.6.8 on HP-UX 11.23 on Itanium2.
When trying to get a directory listing via:
# [EMAIL PROTECTED]:/~ > rsync dev1::deploy
drwxr-xr-x 96 2006/09/06 12:57:36 .
drwxrwxrwx 96 2006/09/11 15:35:33 test
# ...
it works flawlessly, but when trying to get a subdirectory we get the
following error:
# DEV1:/etc# rsync dev1::deploy/test
# rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
# rsync error: error in rsync protocol data stream (code 12) at io.c(463)
# [receiver=2.6.8]
we are using rsync 2.6.8 (as mentioned before)
# [EMAIL PROTECTED]:/~ > rsync --version
# rsync version 2.6.8 protocol version 29
# Copyright (C) 1996-2006 by Andrew Tridgell, Wayne Davison, and others.
# <http://rsync.samba.org/>
# Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles,
# inplace, no IPv6, 32-bit system inums, 64-bit internal inums
our rsyncd.conf looks like this:
# log file = /log/rsyncd/test.log
# pid file = /log/rsyncd/test.pid
# use chroot = true
# [deploy]
# comment = Test
# path = /f/deploynew/ap
# gid = appl
# uid = gso
# read only = no
as this error message semms pretty generic and looking for any answers via
the web didn't
turn out that useful after all. So we installed tusc and traced rsync.
a failing request (rsync dev1::deploy/test) looks like this:
---
[6951] select(4, 0x7fffa0f8, 0x7fffa1f8, NULL, 0x7fffa0f0) . = 1
[6951] read(3, "\n", 1) = 1
[6951] brk(0x4003e000) . = 0
[6951] lstat(".", 0x7fff9760) .. = 0
[6951] open("../", O_RDONLY|0x20, 026540) .. = 6
[6951] fstat(6, 0x7fff9840) = 0
[6951] fcntl(6, F_SETFD, 0) = 0
[6951] sysfs(GETFSIND, 0xc015ac30, 0x777df220) . = 10
[6951] brk(0x40042000) . = 0
[6951] close(6) = 0
[6951] getaccess("/", -34, -5, NULL, NULL, NULL) ... = 5
[6951] open("/", O_RDONLY|0x20, 0) . = 6
[6951] fstat(6, 0x7fff8440) = 0
[6951] fcntl(6, F_SETFD, 0) = 0
[6951] sysfs(GETFSIND, 0xc015ac30, 0x777df220) . = 10
[6951] getdents(6, 0x4003d820, 16384) .. = 152
[6951] stat64("/test", 0x7fff84e0) . = 0
[6951] getdents(6, 0x4003d820, 16384) .. = 0
[6951] close(6) = 0
[6951] Received signal 11, SIGSEGV, in user mode, [SIG_DFL], partial
siginfo
[6951] Siginfo: si_code: SEGV_ACCERR, faulting address: 0, si_errno: 0
[6951] PC: 000100a0.0 break.m 0x16000
[6951] exit(11) [implicit] .
WIFSIGNALED(SIGSEGV)
[6948] Received signal 18, SIGCLD, in select(), [caught], no siginfo
[6948] select(5, 0x7fffe468, NULL, NULL, NULL) . ERR#4
EINTR
[6948] waitpid(-1, NULL, WNOHANG) .. = 6951
[6948] waitpid(-1, NULL, WNOHANG) ..
ERR#10 ECHILD
[6948] select(5, 0x7fffe468, NULL, NULL, NULL) .
[sleeping]
---
the only interesting thing in my opinion is the line:
[6951] open("../", O_RDONLY|0x20, 026540)
why get "../" from a chrooted environment? There's nothing there, as we
have a new "/" .
Any help will be appreciated,
Thanks,
Bernhard
--
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 on client end: unexpected tag 3 [sender] rsyncerror: error in rsync protocol data stream (code 12) atio.c(843) [sender]
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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Wayne Davison Sent: Wednesday, 3 May 2006 16:15 To: Anthony Sadler Cc: rsync@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.. -- 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 on client end: unexpected tag 3 [sender] rsync error: error in rsync protocol data stream (code 12) at io.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..
--- log.c 25 Apr 2006 23:51:15 - 1.146
+++ log.c 3 May 2006 06:06:19 -
@@ -154,17 +154,14 @@ static void logfile_open(void)
void log_init(void)
{
- time_t t;
-
if (log_initialised)
return;
log_initialised = 1;
/* this looks pointless, but it is needed in order for the
* C library on some systems to fetch the timezone info
* before the chroot */
- t = time(NULL);
- localtime(&t);
+ timestring(time(NULL));
/* optionally use a log file instead of syslog */
logfname = lp_log_file();
--
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 on client end: unexpected tag 3 [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(843) [sender]
On Wed, May 03, 2006 at 11:58:07AM +1000, Anthony Sadler wrote:
> unexpected tag 3 [sender]
My analysis shows that some deferred messages (which are those that
arrive in the generator when the generator is already trying to flush a
partial message down the socket) are not being handled by rwrite() like
they should be. Furthermore, the MSG_LOG message doesn't actually need
to be deferred, since they cannot result in any data being written to
the socket. This bug can only affect an rsync daemon that is receiving
files, as all other scenarios behave correctly with the existing code.
The attached patch should fix the problem. I've also checked the fix
into CVS (and it will appear in the next nightly tar file that gets
generated).
Thanks for the detailed report, it was very helpful.
..wayne..
--- io.c25 Apr 2006 23:51:15 - 1.193
+++ io.c3 May 2006 05:13:31 -
@@ -294,6 +294,7 @@ static void read_msg_fd(void)
exit_cleanup(RERR_STREAMIO);
}
close_multiplexing_out();
+ defer_forwarding_messages = 0;
/* FALL THROUGH */
case MSG_INFO:
case MSG_ERROR:
@@ -303,7 +304,8 @@ static void read_msg_fd(void)
if (n >= sizeof buf)
n = sizeof buf - 1;
read_loop(fd, buf, n);
- if (am_generator && am_server &&
defer_forwarding_messages)
+ if (am_generator && am_server
+&& defer_forwarding_messages && tag != MSG_LOG)
msg_list_add(&msg2sndr, tag, buf, n);
else
rwrite((enum logcode)tag, buf, n);
@@ -1134,11 +1136,20 @@ static void msg2sndr_flush(void)
while (msg2sndr.head && io_multiplexing_out) {
struct msg_list_item *m = msg2sndr.head;
+ int tag = (IVAL(m->buf, 0) >> 24) - MPLEX_BASE;
if (!(msg2sndr.head = m->next))
msg2sndr.tail = NULL;
- stats.total_written += m->len;
defer_forwarding_messages = 1;
- writefd_unbuffered(sock_f_out, m->buf, m->len);
+ switch (tag) {
+ case MSG_INFO:
+ case MSG_ERROR:
+ rwrite((enum logcode)tag, m->buf + 4, m->len - 4);
+ break;
+ default:
+ stats.total_written += m->len;
+ writefd_unbuffered(sock_f_out, m->buf, m->len);
+ break;
+ }
defer_forwarding_messages = 0;
free(m);
}
--
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 error on client end: unexpected tag 3 [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(843) [sender]
Hi guys:
First post for me on this list.
THE PROBLEM
===
I have several linux servers (ranging from Redhat 7.3 to FC3) that use Rsync
(version 2.6.8 and 2.6.7, read on for reasons) to backup their data. A typical
rsync backup script looks like this:
--
#!/bin/sh
RSYNC_PASSWORD=
rsync -a --delete --password-file= --ignore-errors --exclude
'/dev/*' --exclude '/sys/*' --exclude '/proc/*' --exclude '/var/run/*'
--exclude '/tmp/*' --exclude '/home/downloads/*' /
@:: >> /var/log/rsync.log
rsync -a --progress --delete --ignore-errors --password-file=
/home/downloads/ @:: >> /var/log/rsync.log
--
(Some things have been replaced to prevent people doing mean things to our
servers :P)
For a long time rsync has worked, occasionly barfing due to lack of harddrive
space or for other external reasons. When we upgraded to version 2.6.8 however,
things started to die.
Here is a typical error we get:
--------------
unexpected tag 3 [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(828)
[sender=2.6.8]
--
SERVERS
===
For the purpose of this email, I will talk about two servers in particular. One
is an apache server, which I will refer to as APACHE, the other our backup
server, which we will call RSERVER.
APACHE is a Fedora Core release 3 (Heidelberg) box, running Linux
2.6.12-1.1381_FC3 with Rsync 2.6.8, installed from an RPM. All software is up
to date to my knowledge.
RSERVER is also a Fedora Core release 3 (Heidelberg) box, also running Linux
2.6.12-1.1381_FC3 with Rsync 2.6.8, again installed from RPM. Again, all
software is up to date.
SETUP
=
The script you see above is the script used to copy the data between APACHE and
RSERVER. It runs once a night, starting at 21:00 and goes for some hours. The
amount of data it has to think about amounts to is some 100 gig. What it has to
sync over the course of an evening can be siginificantly less (I see two
reports that say 46 meg and 32 meg).
The two machines talk to each other over a 100 megabit switched LAN. APACHE is
a server that has port forwards to it and has no software firewall running
(well Iptables almost always runs, but it has no rules and all chains are set
to ACCEPT).
The same with RSERVER.
The script is kicked off by a cronjob running as root.
DETAILS
===
Around about 10 minutes after the script runs, it will fail with the above
error message. With small amounts of data (eg 10 meg, 20 meg, no known
boundary) the script will work. In fact, I see that some files do work with the
cron script. However when I start to sync more data (1.6 gig, 1.7 gig etc), it
fails part of the way through with the above.
Interestingly, CWRsync seems to work (ie Rsync running under Cygwin on
Windows). However this is not exclusive. Some do, some do not. I cannot work
out why (it may be because they are under the size threshold?)
TROUBLESHOOTING
===
- Small Rsyncs will work. No known boundary between small and large though (ie
I cant say "More than this amount of data it will fail")
- Tried running Rsync in Xinetd.
- Tried running Rsync as a daemon, as root
- Using blocking-io
- Using no-blocking-io
- Pings and SSH sessions to watch for network problems.
- Packet dumps (very limited, I have trouble with TCPDump... give me ethereal
any day :P)
- Straces
- Replacing 2.6.8 with 2.6.7. 2.6.7 used to work. (that's why I have said above
two seperate version):
We get a marginally different error message:
--------------
unexpected tag 3 [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(843)
[sender]
--
The difference is that the sender on the 2nd line does not have
(2.6.8). That's the only difference I can find.
STRACE #1
=
I can provide whole straces if people request, but here are some interesting
things I have found.
This is on server RSERVER, the rsync server side, running 2.6.8 as xinetd:
--
21219 open("/etc/localtime", O_RDONLY) = -1 ENOENT (No such file or directory)
21219 write(3, "2006/05/02 05:10:36 [21219] recv"..., 143) = 143
21219 select(5, [4], [0], NULL, {60, 0}) = 1 (in [4], left {60, 0})
21219 select(5, [4], [], NULL, {60, 0}) = 1 (in [4], left {60, 0})
21219 read(4, "s\0\0\n",
Re: rsync error - error in rsync protocol data stream (code 12) at io.c(420)
thanks for your reply.I have tried that also but still getting the same error On 09/12/05, Paul Slootman <[EMAIL PROTECTED]> wrote: On Fri 09 Dec 2005, gg gg234 wrote:>> ssh: connect to host x.x.x.x port 22: No route to host > rsync: connection unexpectedly closed (0 bytes received so far) [sender]> rsync error: error in rsync protocol data stream (code 12) at io.c(420)>> this is related to ssh i believe.But when i try to use from the command > prompt it is working without any problem through sshPerhaps you have some host-specific options in ~/.ssh/config that aren'tpicked up when running from cron?Or there's some hidden character after one of the backslashes, or something like that... Try putting it all on one line in the script.Paul Slootman -- 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(420)
On Fri 09 Dec 2005, gg gg234 wrote: > > ssh: connect to host x.x.x.x port 22: No route to host > rsync: connection unexpectedly closed (0 bytes received so far) [sender] > rsync error: error in rsync protocol data stream (code 12) at io.c(420) > > this is related to ssh i believe.But when i try to use from the command > prompt it is working without any problem through ssh Perhaps you have some host-specific options in ~/.ssh/config that aren't picked up when running from cron? Or there's some hidden character after one of the backslashes, or something like that... Try putting it all on one line in the script. Paul Slootman -- 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 error - error in rsync protocol data stream (code 12) at io.c(420)
Hi, When i try to run rsync command from command linne it is working fine.Below is the command /usr/bin/rsync --compress \ --verbose \ --rsh=ssh \ --times \ --owner \ --group \ --ignore-times \ --links \ --perms \ --recursive \ --size-only \ --delete \ --force \ --numeric-ids \ --stats \ /etc \ [EMAIL PROTECTED]:/home/backup/thismachine/ when i try to use shell script for this #! /bin/bash /usr/bin/rsync --compress \ --verbose \ --rsh=ssh \ --times \ --owner \ --group \ --ignore-times \ --links \ --perms \ --recursive \ --size-only \ --delete \ --force \ --numeric-ids \ --stats \ /etc \ [EMAIL PROTECTED]:/home/backup/thismachine/ I am getting the following error ssh: connect to host x.x.x.x port 22: No route to hostrsync: connection unexpectedly closed (0 bytes received so far) [sender]rsync error: error in rsync protocol data stream (code 12) at io.c(420) this is related to ssh i believe.But when i try to use from the command prompt it is working without any problem through ssh Please some one help me how to fix this error in shell script.Because i want to schedule this from cron Thanks for your time -- 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: Fwd: error in rsync protocol data stream (code 12) at io.c(359)
Sorry - I haven't seen this message. I've figured out the problem. I've downloaded and build latest version - 2.6.6. However during cron job run it runs from another place version 2.6.3pre1. And with this version it doesn't run as expected. On 11/10/05, Wayne Davison <[EMAIL PROTECTED]> wrote: On Tue, Nov 08, 2005 at 11:28:19AM +0200, stoil valchkov wrote:> How can I troubleshoot this?I sent a message to this list just a few hours after your originalrequest responding to a message with an almost identical subject to yours. It essentially told you that the Issues and Debugging page isyour best resource for figuring out how to trouble-shoot a remote rsyncfailure. One of the first suggestions on that page is to upgrade rsync (on both ends!) to 2.6.6 for better error reporting of remote problems.Upgrading will also improve the timeout handling (which may be why theremote rsync is going away). You might also try increasing the timeout value...wayne.. -- 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: Fwd: error in rsync protocol data stream (code 12) at io.c(359)
On Tue, Nov 08, 2005 at 11:28:19AM +0200, stoil valchkov wrote: > How can I troubleshoot this? I sent a message to this list just a few hours after your original request responding to a message with an almost identical subject to yours. It essentially told you that the Issues and Debugging page is your best resource for figuring out how to trouble-shoot a remote rsync failure. One of the first suggestions on that page is to upgrade rsync (on both ends!) to 2.6.6 for better error reporting of remote problems. Upgrading will also improve the timeout handling (which may be why the remote rsync is going away). You might also try increasing the timeout value. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Fwd: error in rsync protocol data stream (code 12) at io.c(359)
No solution yet :( I tought that it is ok, but in fact it didn't run without problems. It was a mistake in shell script and it finished with ok status and I tought rsync finished with success. How can I troubleshoot this? Here is the command line: rsync --partial --partial-dir=$partial_dir --timeout=$rsyncTimeout -vv --compress --force -t -L --delete --rsync-path=/home/me/bin/rsync --exclu de **something** --exclude=someBugUnimportandFile.xml --include-from=rsyncInclude.txt --exclude '*' --recursive me @remoteHost:/remotepath /localPath &> $rsyncLog rsyncErrCode=$?-- Forwarded message --From: stoil valchkov <[EMAIL PROTECTED]> Date: Nov 1, 2005 3:05 PMSubject: error in rsync protocol data stream (code 12) at io.c(359)To: rsync@lists.samba.orgHi, I've been experiencing this error for 2 weeks now. I don't now ehat could be a reason. I've tried to update with latest sources, but the same result (I'm not sure for line number, but the rest is the same). rsync: connection unexpectedly closed (5881604 bytes received so far) [generator]rsync error: error in rsync protocol data stream (code 12) at io.c(359)My synchronized data is about - 6.6GB & lot of files. It used to run without problems but now it can't finish rvrn 1 time. Interesting part is that it breaks often at the same place it was filed previous run (I have a loop in shell script). I've checked source and destination rights - everything should be fine. I've even deleted part of destination data. It didn't succeed to download the deleted data. So what could be a reason for this problem? Where can I look for possible problems? Is it in rsync or in communication channel (I use ssh tunneling)? Do you think that rsync server might do this better? 10x in advance! -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
error in rsync protocol data stream (code 12) at io.c(359)
It seems however that this issue maight have soemthing with permisions on the client side. I've noticed that somehow rights of some directories are changed during rsync-ing. So I've tried to reset rights (added write access for owner) in all directoris recursievely after each rsync try. I don't know if this was the reason but this is 1st time for more than 2 weeks now it succeeded! Do you have ideas what is the reason?-- Forwarded message --From: stoil valchkov <[EMAIL PROTECTED] >Date: Nov 1, 2005 3:05 PMSubject: error in rsync protocol data stream (code 12) at io.c(359)To: rsync@lists.samba.orgHi, I've been experiencing this error for 2 weeks now. I don't now ehat could be a reason. I've tried to update with latest sources, but the same result (I'm not sure for line number, but the rest is the same). rsync: connection unexpectedly closed (5881604 bytes received so far) [generator]rsync error: error in rsync protocol data stream (code 12) at io.c(359)My synchronized data is about - 6.6GB & lot of files. It used to run without problems but now it can't finish rvrn 1 time. Interesting part is that it breaks often at the same place it was filed previous run (I have a loop in shell script). I've checked source and destination rights - everything should be fine. I've even deleted part of destination data. It didn't succeed to download the deleted data. So what could be a reason for this problem? Where can I look for possible problems? Is it in rsync or in communication channel (I use ssh tunneling)? Do you think that rsync server might do this better? 10x in advance! -- 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: error in rsync protocol data stream
On Mon, Oct 31, 2005 at 01:14:16PM -0500, Kevin Karwaski wrote: > rsync: connection unexpectedly closed (12 bytes read so far) > rsync error: error in rsync protocol data stream (code 12) at io.c(189) As the Issues and Debugging page mentions (see item #3 at this URL: http://rsync.samba.org/issues.html), this error just means that the other side went away. Why? They didn't tell us. Either the net connection closed due to ouside circumstances, or the remote rsync crashed/failed. The page gives you several things you can do to help you test the failure, including upgrading for better remote-error reporting (the latest is 2.6.6), enabling core dumps, and enabling remote system-call tracing. ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
error in rsync protocol data stream (code 12) at io.c(359)
Hi, I've been experiencing this error for 2 weeks now. I don't now ehat could be a reason. I've tried to update with latest sources, but the same result (I'm not sure for line number, but the rest is the same). rsync: connection unexpectedly closed (5881604 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(359)My synchronized data is about - 6.6GB & lot of files. It used to run without problems but now it can't finish rvrn 1 time. Interesting part is that it breaks often at the same place it was filed previous run (I have a loop in shell script). I've checked source and destination rights - everything should be fine. I've even deleted part of destination data. It didn't succeed to download the deleted data. So what could be a reason for this problem? Where can I look for possible problems? Is it in rsync or in communication channel (I use ssh tunneling)? Do you think that rsync server might do this better? 10x in advance! -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
error in rsync protocol data stream
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Everyone, I've been running into a protocol error when attempting to rsync files between to hosts over ssh. Here is the line I've been using with the verbosity cranked up: rsync -a -e "ssh -l test" /localpath/to/sync xxx.xxx.xxx.xxx::module cmd=ssh -l test machine=xxx.xxx.xxx.xxx user= path=module cmd=ssh -l test xxx.xxx.xxx.xxx rsync --server --daemon . opening connection using ssh -l test xxx.xxx.xxx.xxx rsync --server - --daemon . [EMAIL PROTECTED]'s password: rsync: connection unexpectedly closed (12 bytes read so far) _exit_cleanup(code=12, file=io.c, line=189): entered rsync error: error in rsync protocol data stream (code 12) at io.c(189) _exit_cleanup(code=12, file=io.c, line=189): about to call exit(12) Does anyone know what could be causing the data stream error? Thanks, - -Kevin -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDZl747gLcxOJB4lcRAqR8AJ9HDSWIgestkpL8awQNWUq1AlN3WgCfW5Ac MB9kK8Hhs7fkH6LZfIn57EA= =hyI8 -END PGP 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: Partial files cause: error in rsync protocol data stream (code 12) at io.c(584)
On Wed, Sep 14, 2005 at 08:51:41PM -0700, Ian Webber wrote: > rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" [sender]: > Connection reset by peer (104) See the "issues and debugging" page of the website for instructions on how to go about debugging a failure on the remote end of the rsync connection (e.g. enabling core files to check for a crash, or logging system calls to see what is failing). ..wayne.. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Partial files cause: error in rsync protocol data stream (code 12) at io.c(584)
Hello, I am wondering if any of you have any ideas for what I am experiencing. I use Rsync over a local network to backup files from a laptop to my main PC which is running the server as a service. These are both Windows 2000 machines running Cygwin 1.5.18-1 and Rsync 2.6.6. It works fine unless I turn on the partial file option (--partial) and then try to resume an interrupted copy. This is a log of what's happening. opening tcp connection to 192.168.0.102 port 873opening connection using --server -vvtr --partial . avcopybuilding file list ...24 files to considerShouldIWorryAbout/ShouldIWorryAbout/Should I Worry About... Drinking.avirsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" [sender]: Connection reset by peer (104)rsync: read error: Connection reset by peer (104)rsync error: error in rsync protocol data stream (code 12) at io.c(584) It definately seems to be a problem when it finds a partial of the file it is trying to copy in the destination directory. >From what I have seen if you have the --partial option set, if you stop the transfer, the file in the destination directory is renamed to it's 'proper' name even though it is not complete. When the partial didn't rename properly I could start the transfer again without difficulty, otherwise I had to delete the partial file and start the transfer again. Once the partial file is in the directory, even if I change the command to not make use of partial files, rsync still fails with the above error. I am not using a secure channel and I have tried it without any firewalls running but this makes no difference. I am running cwRsync 2.03 (http://www.itefix.no) on both the computers. Only the main PC has the server installed on it running as a service. I have checked the permissions and the correct local user has the ability to write to the required directory. I googled the web and the archive list and didn't find anything that seemed to relate to it. Thanks for any help you can offer. Ian -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 1508] Using options --modify-window and --password-file cause error in rsync protocol data stream (code 12)
https://bugzilla.samba.org/show_bug.cgi?id=1508 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2005-03-18 19:47 --- I haven't been able to duplicate this bug. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 1508] Using options --modify-window and --password-file cause error in rsync protocol data stream (code 12)
https://bugzilla.samba.org/show_bug.cgi?id=1508 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Additional Comments From [EMAIL PROTECTED] 2005-02-25 11:14 --- I am unable to duplicate this using 2.6.3 on cygwin. Do you still see this problem? The only theory I have is that the asprintf() call that is used to create the --modify-window option that is passed to the server was not working right in that build of rsync (or perhaps in that version of cygwin's library?). If you still see the problem, try specifying --max-delete=200 instead of --modify-window=1 and see if there is a problem for that option as well. If so, it is likely to be an asprintf()-related bug. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 1477] error in rsync protocol data stream (code 12) at io.c(836)
https://bugzilla.samba.org/show_bug.cgi?id=1477 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-02-13 21:36 --- This was probably a case of the mkstemp() function not opening the file with large-file support enabled. The current code attempts to work around this by using mktemp() and a large-file-supporting open() call when it thinks that this is going to be a problem. If you don't believe this analysis to be the case, let me know. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- 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: error in rsync protocol data stream (code 12) at io.c(692)
On Fri, 14 Jan 2005, Wayne Davison wrote: > On Thu, Jan 13, 2005 at 07:51:33PM +0100, Dag Wieers wrote: > > unexpected tag -111 > > rsync error: error in rsync protocol data stream (code 12) at io.c(692) > > > > Can this be caused by the delay-renames patch ? > > I tested how the code handles the verification-failed redo phase, both > with and without the --delayed-rename patch, and I didn't get it to > fail. I thereafter diagnosed and checked-in fixes for the two problems > above. You'll probably want to check-out the latest CVS source to get > them (since --delayed-renames makes use of the --partial-dir logic). I did not see the same problem with the latest CVS sources yet. And before using the new version it was a repeatable problem. Thanks Wayne ! -- dag wieers, [EMAIL PROTECTED], http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power] -- 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: error in rsync protocol data stream (code 12) at io.c(692)
On Thu, Jan 13, 2005 at 07:51:33PM +0100, Dag Wieers wrote: > unexpected tag -111 > rsync error: error in rsync protocol data stream (code 12) at io.c(692) > > Can this be caused by the delay-renames patch ? I don't think so. An "unexpected tag" error indicates that something went wrong in the synchronization of the data being transferred over the socket, which is pretty strange. While looking into this, I did notice a couple minor problems in the --partial-dir code in CVS (these aren't in the 2.6.3 code as they were caused by new features getting added to the codebase): - If --whole-file is in effect, the generator would ignore the presence of a basis file in the partial-dir, and the file would therefore not be removed by the receiver (because the receiver now depends on the generator to be told what the basis file is for the transfer). - If --whole-file is NOT in effect, the generator might use a partial- dir file for the basis but not be able to tell the receiver about it (since the "name pipe" might not have been requested). This could result in a corrupted transfer if the basis file for the generator was the partial-dir file and the basis file for the receiver was the normal file. I tested how the code handles the verification-failed redo phase, both with and without the --delayed-rename patch, and I didn't get it to fail. I thereafter diagnosed and checked-in fixes for the two problems above. You'll probably want to check-out the latest CVS source to get them (since --delayed-renames makes use of the --partial-dir logic). ..wayne.. -- 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: error in rsync protocol data stream (code 12) at io.c(692)
On Thu, 13 Jan 2005, Dag Wieers wrote:
> Hi Wayne, Jeff,
>
> With the same version/build as the last report, I got this error now:
>
> ...
> extra/state/all-packages.list
>145 100% 46.83kB/s0:00:30 (634, 0.0% of 201605)
> WARNING: fedora/1/en/i386/base/pkglist.dag.bz2 failed verification --
> update put into partial-dir (will try again).
> unexpected tag -111
> rsync error: error in rsync protocol data stream (code 12) at io.c(692)
>
> Can this be caused by the delay-renames patch ?
After this, got another one:
source/perl-Net-XMPP-1.0-1.rf.src.rpm
99575 100%1.28kB/s0:00:51 (645, 99.6% of 200819)
WARNING: extra/state/all-packages.list failed verification -- update
put
into partial-dir (will try again).
unexpected tag 60
rsync error: error in rsync protocol data stream (code 12) at io.c(692)
-- dag wieers, [EMAIL PROTECTED], http://dag.wieers.com/ --
[all I want is a warm bed and a kind word and unlimited power]
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
error in rsync protocol data stream (code 12) at io.c(692)
Hi Wayne, Jeff, With the same version/build as the last report, I got this error now: ... extra/state/all-packages.list 145 100% 46.83kB/s0:00:30 (634, 0.0% of 201605) WARNING: fedora/1/en/i386/base/pkglist.dag.bz2 failed verification -- update put into partial-dir (will try again). unexpected tag -111 rsync error: error in rsync protocol data stream (code 12) at io.c(692) Can this be caused by the delay-renames patch ? Kind regards, -- dag wieers, [EMAIL PROTECTED], http://dag.wieers.com/ -- [all I want is a warm bed and a kind word and unlimited power] -- 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 error: error in rsync protocol data stream (code 12) at io.c(666)
Hi sir, While I am trying to run rsync -rvzl . rsync-destination it is giving the above error after copying few files. If I run it again then its copying some more files and again exiting with the above problem. Thanks srinivas -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 1477] error in rsync protocol data stream (code 12) at io.c(836)
https://bugzilla.samba.org/show_bug.cgi?id=1477 --- Additional Comments From [EMAIL PROTECTED] 2004-10-11 04:00 --- Created an attachment (id=716) --> (https://bugzilla.samba.org/attachment.cgi?id=716&action=view) Change option parsing This patch separates the daemon-mode's option parsing from the normal client/server's option parsing. It also separates the options in the usage message (requiring the user to use "rsync --daemon --help" to see the daemon options). Lightly tested, including daemon mode over ssh. Need to double-check option parsing separation to ensure I didn't miss anything. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 1633] error in rsync protocol data stream (code 12) at io.c(359)
https://bugzilla.samba.org/show_bug.cgi?id=1633 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-09-18 10:11 --- Rsync doesn't use any ssh protocol itself -- it just calls ssh and lets it do whatever you've configured ssh to do. You can affect this by either setting per-host config items in your ssh config file, or by setting ssh options using the --rsh (-e) option, like this: --rsh="ssh -2" You can also specify 2 -v options to see what command rsync is running to talk to the remote host and you can try running that outside of rsync to see what it does (you can substitite a different remote command than rsync too, such as "uptime"). -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 1477] error in rsync protocol data stream (code 12) at io.c(836)
https://bugzilla.samba.org/show_bug.cgi?id=1477 --- Additional Comments From [EMAIL PROTECTED] 2004-09-06 10:36 --- I don't know what the current status of this bug is, but I'm experiencing similar behaviour trying to "emerge sync" with Gentoo's portage. I've seen it on two different machines and only at home .. which may be important because at home I have a commercial Hughes 1.2MB inbound 0.1MB outbound 750ms latency satellite connection. When I bring the laptop to work and connect with a short latency T3 I don't experience the problem. If you need additional info or can suggest useful tests, I'd be happy to play around .. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 1633] New: error in rsync protocol data stream (code 12) at io.c(359)
https://bugzilla.samba.org/show_bug.cgi?id=1633 Summary: error in rsync protocol data stream (code 12) at io.c(359) Product: rsync Version: 2.6.3 Platform: Alpha URL: http://www.snailbook.com/faq/scp-ossh-to-ssh2.auto.html OS/Version: OSF/1 Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] Using rsync from OSF with commercial ssh.com to Solaris with Sun ssh works fine. Using rsync from Solaris with Sun (OpenSSH derived) to OSF fails with: select: Bad file number rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(359) This sounds like the scp compatibility problem between the two. Does rsync use ssh protocol 2 or protocol 1 which scp uses? Because protocol 1 is not running on the OSF machine. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream (code 12) at io.c(165)
On Tue, Jun 22, 2004 at 10:06:49AM -0400, Linux wrote: > I get the same error even after taking the advise from the subsequent > posts to this message and other message stateing "error in rsync > protocol data stream (code 12) at io.c(165)" . > > The one thing that i have noticed is that is only errors when the size > of the directory on the remote machine exceeds 65GB. if it's 66GB the > transfer will fail half way through. The files i'm transfering are BKF > files from veritas backup exec and they range from 2-4GB each. In > addition my --timeout period is set to "4000" > Thank you for reporting this error. It would be helpful if you could show the output of a failed run with the -vvv option. -chris > > So with that said if i keep the folder under 65GB i have no problems > what so ever. Also both machines taking part in this process are 2.4ghz > and have 512mb or pc-3200. > > > Thanks > Edward > > > > > On Mon, 2004-06-21 at 13:47, Nick Sylvester wrote: > > I am recieving a connection unexpectedly closed error while trying to > > sync a directory on two machines. Rsync is in my path on both > > machines. I am using ssh and I can connect to the server fine through > > ssh. I am using a vpn but have no problems connecting to any of the > > servers with it. This is the full error message I get: > > > > Remote Machine: Connection refused > > rsync: connection unexpectedly closed (0 bytes read so far) > > rsync error: error in rsync protocol data stream (code 12) at io.c(165) > > > > Here is the command I am using > > > > > > rsync -r --timeout=600 [EMAIL PROTECTED] machine:/opt/u91/scripts/sqlpath/* > > /home/oracle/sqlpath > > > > I am a new user to rsync and any suggestions or help would be much > > appreciated. > > > > Thanks > > Nick Sylvester > > -- > To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 1508] New: Using options --modify-window and --password-file cause error in rsync protocol data stream (code 12)
https://bugzilla.samba.org/show_bug.cgi?id=1508 Summary: Using options --modify-window and --password-file cause error in rsync protocol data stream (code 12) Product: rsync Version: 2.6.2 Platform: x86 OS/Version: Windows XP Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] I use rsync on Cygwin and have found a new bug in version 2.6.2 that seems to be related to the combination of command line options. I have 2 test cases and 2 machines. Test case 1 succeeds on machine A & B test case 2 fails on machine A (newer rsync) and succeeds on B. Test Case 1 (both machines ok): rsync -v --password-file .rsync.secrets t.txt [EMAIL PROTECTED]::judi2/ Test Case 2 (fails on machine B): rsync -v --modify-window=1 --password-file .rsync.secrets t.txt [EMAIL PROTECTED]::judi2/ Machine A (failing on test 2): Windows XP Home CYGWIN_NT-5.1 judi 1.5.10(0.116/4/2) 2004-05-25 22:07 i686 unknown unknown Cygwin rsync version 2.6.2 protocol version 28 Machine B (both test ok) Windows XP Home CYGWIN_NT-5.1 Dell3 1.5.5(0.94/3/2) 2003-09-20 16:31 i686 unknown unknown Cygwin rsync version 2.5.7 protocol version 26 Error says: @ERROR: auth failed on module judi2 rsync: connection unexpectedly closed (102 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at /home/lapo/packaging/tmp/rsync-2.6.2/io.c(342) I have tried to use the --rsync-path=/SOME/PATH/rsync-debug but this does not go into debug mode nor create a trace file under Cygwin; it seems to ignore the option. Please let me know if this is something I should submit to the Cygwin folk. WORKAROUND: don't use the modify-window option(!) -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 1502] rsync error: error in rsync protocol data stream (code 12) at io.c(836)
https://bugzilla.samba.org/show_bug.cgi?id=1502 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2004-07-04 10:57 --- The rsync debug output shows: [pid 5246] write(3, "\200\0\331f\17\v\0\20\230\0050#PLD20040625\200\0\331g\17". .., 4096) = -1 ENOSPC (No space left on device) However, this is not true. The system log shows: Jul 4 07:03:31 ram kernel: EXT3-fs error (device ide0(3,3)): ext3_new_block: block(9465252) >= blocks count(9464293) - block_group = 288, es == c17f5400 Rebooted the server, manually run fsck, the problem is resolved. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 1502] New: rsync error: error in rsync protocol data stream (code 12) at io.c(836)
https://bugzilla.samba.org/show_bug.cgi?id=1502 Summary: rsync error: error in rsync protocol data stream (code 12) at io.c(836) Product: rsync Version: 2.6.2 Platform: x86 OS/Version: Linux Status: NEW Severity: blocker Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] 1. Everything is under one "/" filesystem. 2. When I run this: # rsync -av --delete /apps50/backup/./home/ape/ /backup01/ape.5.20040702010001/ I got this. Please note the error at the end. The target directory contains the old backup 1 week ago, it is refreshed with the current files. building file list ... done apps01/tg/jobs/log/download_reply/ apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_09:48 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_09:58 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_10:08 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_10:18 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_10:28 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_10:38 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_10:48 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_10:58 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_11:08 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_11:18 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_11:28 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_11:38 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_11:48 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_11:58 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_12:08 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_12:18 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_12:28 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_12:38 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_12:48 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_12:58 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_13:08 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_13:18 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_13:28 apps01/tg/jobs/log/download_reply/download_reply.log.2004-06-29_13:38 rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(836) 3. Do I have enough space? # du -sk /apps50/backup/./home/ape/ /backup01/ape.5.20040702010001/ 2919456 /apps50/backup/./home/ape 2348284 /backup01/ape.5.20040702010001 # df -k . Filesystem 1K-blocks Used Available Use% Mounted on /dev/hda3 37262796 26873832 8496108 76% / So I have enough space. 4. However, if I delete all files from the destination directory: # cd /backup01/ape.5.20040702010001 # ls apps01 # \rm -rf apps01/ And rerun the command. It is fine: ... wrote 2907157423 bytes read 534660 bytes 4568251.51 bytes/sec total size is 2905200920 speedup is 1.00 This happened twice. The process is run on daily basis. I am sure it will happen again. So whatever debugging commands that I need to run, I can. Thanks a lot. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 1477] error in rsync protocol data stream (code 12) at io.c(836)
https://bugzilla.samba.org/show_bug.cgi?id=1477 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Additional Comments From [EMAIL PROTECTED] 2004-06-30 13:36 --- First suggestion: try running the command without the '*' (but with the trailing '/') and see if it still fails. Also, there is a helper script that might help you to debug what is happening: http://rsync.samba.org/rsync-debug Use it in a command like this: rsync -av --rsync-path=/SOME/PATH/rsync-debug localhost:/prod1/* /prod1n/ (Some kind of host: is needed to get rsync to use the rsync-debug script.) -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 1477] error in rsync protocol data stream (code 12) at io.c(836)
https://bugzilla.samba.org/show_bug.cgi?id=1477 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2004-06-24 10:49 --- This failure message just tells you that something went wrong on the other end. You'll have to investigate why by monitoring the remote process somehow (e.g. using a debugger, using an strace setup, enabling core dumps, etc.). Once you discover the reason for the failure (if it turns out to be a bug) you can enter a bug for the actual failure. Until then, feel free to ask for help on the mailing list. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
[Bug 1477] New: error in rsync protocol data stream (code 12) at io.c(836)
https://bugzilla.samba.org/show_bug.cgi?id=1477 Summary: error in rsync protocol data stream (code 12) at io.c(836) Product: rsync Version: 2.6.2 Platform: PA-RISC OS/Version: HP-UX Status: NEW Severity: major Priority: P3 Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] same to bug 1457, on HPUX 11i with ANSI/C compiler with largefile option. below rsync is on local file system. # rsync -av /prod1/* /prod1n/ building file list ... done DW/ DW/DATA/ DW/DATA/DWCOF02.DAT rsync: writefd_unbuffered failed to write 32768 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(836) rsync: writefd_unbuffered failed to write 69 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(836) # ls -l /prod1/DW/DATA/DWCOF02.DAT -rw-r--r-- 1 dwhdwprod 2225391444 May 31 10:59 /prod1/DW/DATA/DWCOF02.DAT KY -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the QA contact for the bug, or are watching the QA contact. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream (code 12) at io.c(165)
I get the same error even after taking the advise from the subsequent posts to this message and other message stateing "error in rsync protocol data stream (code 12) at io.c(165)" . The one thing that i have noticed is that is only errors when the size of the directory on the remote machine exceeds 65GB. if it's 66GB the transfer will fail half way through. The files i'm transfering are BKF files from veritas backup exec and they range from 2-4GB each. In addition my --timeout period is set to "4000" So with that said if i keep the folder under 65GB i have no problems what so ever. Also both machines taking part in this process are 2.4ghz and have 512mb or pc-3200. Thanks Edward On Mon, 2004-06-21 at 13:47, Nick Sylvester wrote: > I am recieving a connection unexpectedly closed error while trying to > sync a directory on two machines. Rsync is in my path on both > machines. I am using ssh and I can connect to the server fine through > ssh. I am using a vpn but have no problems connecting to any of the > servers with it. This is the full error message I get: > > Remote Machine: Connection refused > rsync: connection unexpectedly closed (0 bytes read so far) > rsync error: error in rsync protocol data stream (code 12) at io.c(165) > > Here is the command I am using > > > rsync -r --timeout=600 [EMAIL PROTECTED] machine:/opt/u91/scripts/sqlpath/* > /home/oracle/sqlpath > > I am a new user to rsync and any suggestions or help would be much > appreciated. > > Thanks > Nick Sylvester -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream (code 12) at io.c(165)
> I am recieving a connection unexpectedly closed error while trying to > sync a directory on two machines. Rsync is in my path on both > machines. I am using ssh and I can connect to the server fine through > ssh. I am using a vpn but have no problems connecting to any of the > servers with it. This is the full error message I get: > Remote Machine: Connection refused This looks like an rsh or ssh problem. Old versions of rsync uses by default rsh while the recent ones uses ssh. > rsync -r --timeout=600 [EMAIL PROTECTED] machine:/opt/u91/scripts/sqlpath/* > /home/oracle/sqlpath Try this instead to see precisely what command rsync runs on the remote machine: rsync -vv -r --timeout=600 [EMAIL PROTECTED] machine:/opt/u91/scripts/sqlpath/ \ /home/oracle/sqlpath If your version of rsync uses rsh, force then to use ssh vith: --rsh=ssh Note: It's better to use sqlpath/ instead of sqlpath/* in your command: o To prevent an eventual arg list too long on the remote o To be able to use --delete if you want an exact mirror of the sqlpath directory You may also want to use the --archive option. -- [EMAIL PROTECTED], Tel: (33) 04 92 38 79 11, Bur: C112 INRIA Sophia, 2004, rte des Lucioles, B.P.93 - 06902 Sophia Antipolis Cedex -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream (code 12) at io.c(165)
On Mon, Jun 21, 2004 at 11:47:32AM -0600, Nick Sylvester wrote: > Remote Machine: Connection refused This is the important part -- the connection to the remote machine was refused. My guess would be because it's trying to use rsh, not ssh, however you don't have to guess -- just run rsync with -vv and you'll see exactly what rsync is doing (or trying to do). If my guess is correct, see the --rsh (-e) option as well as the RSYNC_RSH environment variable. ..wayne.. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
error in rsync protocol data stream (code 12) at io.c(165)
I am recieving a connection unexpectedly closed error while trying to sync a directory on two machines. Rsync is in my path on both machines. I am using ssh and I can connect to the server fine through ssh. I am using a vpn but have no problems connecting to any of the servers with it. This is the full error message I get: Remote Machine: Connection refused rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) Here is the command I am using rsync -r --timeout=600 [EMAIL PROTECTED] machine:/opt/u91/scripts/sqlpath/* /home/oracle/sqlpath I am a new user to rsync and any suggestions or help would be much appreciated. Thanks Nick Sylvester -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream
It appears that the command you show is not a complete copy/paste job. When you changed "backup.amlaw.com" or whatever it was to "backup.domain.com", you also removed one of the colons between that and "jspfsp", as the only time rsync does a chroot is as a server. A chroot failure is almost invariably an erroneous "path =" line in the rsyncd.conf, and since it works otherwise, we know your OS can do chroot. Check the directory named under the "[jspfsp]" entry in your rsyncd.conf. Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 [EMAIL PROTECTED] I am doing this to rsync a file: rsync -avz /usr/local/websphere/appserver/hosts/default_host/jsp/servers/includes/file1 .txt backup.domain.com:jspfsp >> /var/log/rsync_backup.log I get these error: @ERROR: chroot failed rsync: connection unexpectedly closed (34 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) I am rsyncing several folders between these two servers with no problem. But now I keep getting this rsyncing a single script. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
error in rsync protocol data stream
I am doing this to rsync a file: rsync -avz /usr/local/websphere/appserver/hosts/default_host/jsp/servers/includes/file1 .txt backup.domain.com:jspfsp >> /var/log/rsync_backup.log I get these error: @ERROR: chroot failed rsync: connection unexpectedly closed (34 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) I am rsyncing several folders between these two servers with no problem. But now I keep getting this rsyncing a single script. Any ideas please? Thanks -Daniel -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
rsync error: error in rsync protocol data stream (code 12) at io.c(189)
Rsync Issue Solaris8
When performing a simple rsync between servers I was getting the
following error:
root:#> rsync -e ssh -va /export/home/a078479/bob
smmk39:/export/home/a078479/
ksh: rsync: not found
rsync: connection unexpectedly closed (0 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(189)
root:#>
I was thorghrough in setting up rsync to be used between servers and was
still getting errors , I did the following to Setup Rsync.
Added each host into the /etc/hosts file.
Added each users ssh keys from each node to their ./.ssh/authorized_keys
so I dont have to use password files or anything of the sort.
Added rsync Port Alias to /etc/services:
echo "rsync 873/tcp" >> /etc/services
Added rsync Daemon to /etc/inetd.conf:
echo "rsync stream tcp nowait root /usr/bin/rsync rsyncd --daemon" >>
/etc/inetd.conf
Recycle (HUP) inetd daemon:
for i in `ps -ef |grep inetd | grep -v grep | awk '{print $2}'
do
kill -HUP $i
done
And still got the error as indicated below.
So I tried to do some debugging with the syntax below.
root:#> rsync -e 'ssh -vv -x' -ra /export/home/a078479/bob
smmk39:/export/home/a078479/
OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f
debug1: Reading configuration data /fisc/openssh/etc/ssh_config
debug1: Applying options for *
debug1: Rhosts Authentication disabled, originating port will not be
trusted.
debug1: ssh_connect: needpriv 0
debug1: Connecting to smmk39 [172.25.108.30] port 22.
debug1: Connection established.
debug1: identity file /export/home/a078479/.ssh/identity type 0
debug2: key_type_from_name: unknown key type '-BEGIN'
debug2: key_type_from_name: unknown key type '-END'
debug1: identity file /export/home/a078479/.ssh/id_rsa type 1
debug1: identity file /export/home/a078479/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version
OpenSSH_3.4p1
debug1: match: OpenSSH_3.4p1 pat OpenSSH*
debug1: Local version string SSH-1.5-OpenSSH_3.4p1
debug1: Waiting for server public key.
debug1: Received server public key (1152 bits) and host key (1024 bits).
debug1: Host 'smmk39' is known and matches the RSA1 host key.
debug1: Found key in /export/home/a078479/.ssh/known_hosts:1
debug1: Encryption type: 3des
debug1: Sent encrypted session key.
debug1: cipher_init: set keylen (16 -> 32)
debug1: cipher_init: set keylen (16 -> 32)
debug1: Installing crc compensation attack detector.
debug1: Received encrypted confirmation.
debug1: Trying RSA authentication with key
'/export/home/a078479/.ssh/identity'
debug1: Received RSA challenge from server.
debug1: Sending response to host key RSA challenge.
debug1: Remote: RSA authentication accepted.
debug1: RSA authentication accepted by server.
debug1: Sending command: rsync --server -logDtpr . /export/home/a078479/
debug1: Entering interactive session.
debug1: fd 0 setting O_NONBLOCK
debug2: fd 1 is O_NONBLOCK
ksh: rsync: not found
debug2: fd 0 is not O_NONBLOCK
debug1: fd 1 clearing O_NONBLOCK
debug1: Transferred: stdin 4, stdout 0, stderr 23 bytes in 0.1 seconds
debug1: Bytes per second: stdin 34.4, stdout 0.0, stderr 197.7
debug1: Exit status 127
rsync: connection unexpectedly closed (0 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(189)
Here I found out that after secure shelling over to the remote system
the rsync command was not being found!!
As the user I did a which and found out that rsync was in the
/usr/local/bin/rsync so I decided to link rsync to a system binary
directory.
sdal19:/# ln -s /usr/local/bin/rsync /usr/bin/rsync
sdal19:/# which rsync
/usr/bin/rsync
root:#> rsync -e ssh -va /export/home/a078479/bob
smmk39:/export/home/a078479/
building file list ... done
bob/
bob/test
wrote 129 bytes read 40 bytes 112.67 bytes/sec
total size is 0 speedup is 0.00
Success!!
Looks like the system or user profile was not setting set when ssh logs
in and this simple change will fix it in my case.
Bobby Gunn
--
To unsubscribe or change options: http://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(189)
Standard newbie issue. rsh host command (or ssh host command in your case) does so in a fairly stripped environment, for instance, a small $PATH, which is your issue (unless rsync isn't even installed on smmk39). rsync has aneasy workaround for it. add " --rsync-path=/path/on/the/remote/host/to/rsync " commonly " --rsync-path=/usr/local/bin/rsync ". You can also link it into someplace in your path, if you're the admin, and are going to be having a lot of users doing their own rsync commandlines. The stuff you're doing with services and inetd.conf are irrelevant, unless you're going to run an inetd-managed rsyncd, which is NOT what you are doing or accessing in the commandline given. Also your inet hupping is a bit scary. If you have anything that has the word "inetd" in the ps line, it's going to get a HUP, and many things react to a HUP like to a TERM. I'd suggest a pattern like " /usr/sbin/in[eE]td -s$", as you're on Solaris 8. To call that rsync server, forget the "-e ssh". have this in your /etc/rsyncd.conf: ++ [home] path = /home ++ Or tighter yet: ++ [homeforbob] path = /home/a078479/bob ++ rsync -va /export/home/a078479/bob smmk39::homeforbob I see, having read to the bottom of your message, that you did the linking thing. That's cool, and well-documented. Glad you figured it out. It's not an rsync issue, but an environmental one. Tim Conway Unix System Administration Contractor - IBM Global Services desk:3032734776 [EMAIL PROTECTED] Rsync Issue Solaris8 When performing a simple rsync between servers I was getting the following error: root:#> rsync -e ssh -va /export/home/a078479/bob smmk39:/export/home/a078479/ ksh: rsync: not found rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) root:#> -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream
On Thursday 12 February 2004 10:55 pm, jw schultz wrote: > Try the patch and let us know.ÂÂThatÂshouldÂallowÂyouÂto > function.ÂÂCVSÂ(whichÂdoesÂnotÂhaveÂthatÂpatch)Ârequires > about 20 bytes less per-file. Instead of the patch, I simply broke my rsync job into smaller pieces. Thank you for the help. -- Ray Lischner, author of C++ in a Nutshell http://www.tempest-sw.com/cpp -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream
On Thu, Feb 12, 2004 at 10:28:31PM -0500, Ray Lischner wrote: > According to the FAQ-o-matic, rsync needs about 100 bytes/file. I am > copying about 1,000,000 files, so that comes out to roughly 100MB. The > system has 192MB of physical RAM. In addition to what J.W. says, also keep in mind that this estimate is per process. If you're doing a local copy (with all 3 processes on the same machine) you'll start out needing twice as much memory (only twice because 2 of the processes share most of their memory). As the transfer progresses, the receiving side's memory slowly becomes unshared until the 2 processes consume about twice as much real memory as they started out consuming (even though they aren't actually growing in size). The CVS version now has code that prevents this copy-on-write unsharing of memory on the receiving side, but only if file permissions are being preserved. It also uses significantly less memory in the per-file structures and in the hard-link handling. ..wayne.. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream
On Thu, Feb 12, 2004 at 10:28:31PM -0500, Ray Lischner wrote: > On Thursday 12 February 2004 06:38 pm, jw schultz wrote: > > > You have run out of memory. > > According to the FAQ-o-matic, rsync needs about 100 bytes/file. I am > copying about 1,000,000 files, so that comes out to roughly 100MB. The > system has 192MB of physical RAM. Of course, the kernel and all the > other daemons and what-not need memory, but there should still be > enough for rsync. > > I was successful when copying fewer files at a time. When I copy 300,000 > files, rsync's RSS is 50MB after building the file list, and while it > is copying, the RSS rises to about 75MB. > > I conclude that rsync actually needs as much as 250 bytes/file. This > explains why 192MB is insufficient when I want to copy 1M files. That 100 bytes/file is per file usage for the purpose of scaling. Subject to variability according to actual filename lengths and system wordsize, and does not account for the additional 72bytes/file that were needed if -H was in play. Don't confuse per-file with flat overhead and data requirements for one-file-at-a-time transfers that get reused every file. Try the patch and let us know. That should allow you to function. CVS (which does not have that patch) requires about 20 bytes less per-file. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream
On Thursday 12 February 2004 06:38 pm, jw schultz wrote: > You have run out of memory. According to the FAQ-o-matic, rsync needs about 100 bytes/file. I am copying about 1,000,000 files, so that comes out to roughly 100MB. The system has 192MB of physical RAM. Of course, the kernel and all the other daemons and what-not need memory, but there should still be enough for rsync. I was successful when copying fewer files at a time. When I copy 300,000 files, rsync's RSS is 50MB after building the file list, and while it is copying, the RSS rises to about 75MB. I conclude that rsync actually needs as much as 250 bytes/file. This explains why 192MB is insufficient when I want to copy 1M files. -- Ray Lischner, author of C++ in a Nutshell http://www.tempest-sw.com/cpp -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream
On Thu, 12 Feb 2004, jw schultz wrote:
> Try this patch which adds an arbitrary 100ms back-off delay
> to hopefully give the system a chance to recover.
There should be some counting done - if rsync ends up banging too often
against ENOBUFS it might get in the crosshairs of the OOM killer. Maybe we
might want to even consider a sync() call after a number of ENOBUFS?
> Index: io.c
> ===
> RCS file: /data/cvs/rsync/io.c,v
> retrieving revision 1.115
> diff -u -p -r1.115 io.c
> --- io.c 26 Dec 2003 23:04:01 - 1.115
> +++ io.c 12 Feb 2004 23:33:42 -
> @@ -655,6 +655,11 @@ static void writefd_unbuffered(int fd,ch
> continue;
> }
>
> + if (ret == -1 && errno == ENOBUFS) {
> + msleep(100); /* system overload, back off */
> + continue;
> + }
> +
> if (ret <= 0) {
> /* Don't try to write errors back
>* across the stream */
> --
Cristian
--
--
Cristian Gafton -- [EMAIL PROTECTED] -- Red Hat, Inc.
~~
"There are two kinds of people who never amount to much: those who
cannot do what they are told, and those who can do nothing else."
--Cyrus Curtis
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream
On Thu, Feb 12, 2004 at 02:14:12PM -0500, Ray Lischner wrote:
> On Thursday 12 February 2004 12:44 pm, Ray Lischner wrote:
>
> > I am trying to backup an entire disk to a USB-mounted disk, for backup
> > purposes. Many files are copied, but eventually rsync dies:
>
> I tried it again, and this time it fails at a different point and with a
> different error:
>
> $ rsync -axHSv --delete /backup /media/sda1
> ...
> rsync: writefd_unbuffered failed to write 32768 bytes: phase "unknown":
> No buffer space available
> rsync error: error in rsync protocol data stream (code 12) at io.c(666)
>
> As I mentioned in my previous post, the system has 192MB RAM, 400MB
> swap. The file system I am trying to copy takes up about 15GB.
You have run out of memory. Per the SuSE distributed
write(2) manpage ENOBUFS is not supposed to happen but SUSv3
does list such an error.
Try this patch which adds an arbitrary 100ms back-off delay
to hopefully give the system a chance to recover.
Index: io.c
===
RCS file: /data/cvs/rsync/io.c,v
retrieving revision 1.115
diff -u -p -r1.115 io.c
--- io.c26 Dec 2003 23:04:01 - 1.115
+++ io.c12 Feb 2004 23:33:42 -
@@ -655,6 +655,11 @@ static void writefd_unbuffered(int fd,ch
continue;
}
+ if (ret == -1 && errno == ENOBUFS) {
+ msleep(100); /* system overload, back off */
+ continue;
+ }
+
if (ret <= 0) {
/* Don't try to write errors back
* across the stream */
--
J.W. SchultzPegasystems Technologies
email address: [EMAIL PROTECTED]
Remember Cernan and Schmitt
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream
On Thursday 12 February 2004 04:00 pm, Lee Eakin wrote: > Is your USB disk a usb-1 device? No, USB 2.0: Maxtor OneTouch (0x0d49/0x7010). I've repeated this attempt three times in a row. Each time, it fails after about 90-100 minutes of elapsed time. -- Ray Lischner, author of C++ in a Nutshell http://www.tempest-sw.com/cpp -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream
On Thu, 12 Feb 2004, Lee Eakin wrote: > Is your USB disk a usb-1 device? I got various errors due to the slow > access times over usb-1 (not rsync's problem). I was able to reduce the > number of errors using the --bwlimit option to slow down rsync so the > device could keep up better. I've had no problems since I upgraded to > usb-2. You can also try to mount the usb storage with the sync option. Cristian -- -- Cristian Gafton -- [EMAIL PROTECTED] -- Red Hat, Inc. ~~ "There are two kinds of people who never amount to much: those who cannot do what they are told, and those who can do nothing else." --Cyrus Curtis -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream
Is your USB disk a usb-1 device? I got various errors due to the slow access times over usb-1 (not rsync's problem). I was able to reduce the number of errors using the --bwlimit option to slow down rsync so the device could keep up better. I've had no problems since I upgraded to usb-2. -Lee > Date: Thu, 12 Feb 2004 14:14:12 -0500 > From: Ray Lischner <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: error in rsync protocol data stream > X-Original-To: [EMAIL PROTECTED] > X-Injected-Via-Gmane: http://gmane.org/ > X-Complaints-To: [EMAIL PROTECTED] > X-Gmane-NNTP-Posting-Host: dsl092-046-090.blt1.dsl.speakeasy.net > User-Agent: KNode/0.7.2 > X-BeenThere: [EMAIL PROTECTED] > X-Mailman-Version: 2.1.3 > > On Thursday 12 February 2004 12:44 pm, Ray Lischner wrote: > > > I am trying to backup an entire disk to a USB-mounted disk, for backup > > purposes. Many files are copied, but eventually rsync dies: > > I tried it again, and this time it fails at a different point and with a > different error: > > $ rsync -axHSv --delete /backup /media/sda1 > ... > rsync: writefd_unbuffered failed to write 32768 bytes: phase "unknown": > No buffer space available > rsync error: error in rsync protocol data stream (code 12) at io.c(666) > > As I mentioned in my previous post, the system has 192MB RAM, 400MB > swap. The file system I am trying to copy takes up about 15GB. > -- > Ray Lischner, author of C++ in a Nutshell > http://www.tempest-sw.com/cpp > > -- > To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- Lee Eakin - [EMAIL PROTECTED] Gerrold's Fundamental Truth: It's a good thing money can't buy happiness. We couldn't stand the commercials. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream
On Thursday 12 February 2004 12:44 pm, Ray Lischner wrote: > I am trying to backup an entire disk to a USB-mounted disk, for backup > purposes. Many files are copied, but eventually rsync dies: I tried it again, and this time it fails at a different point and with a different error: $ rsync -axHSv --delete /backup /media/sda1 ... rsync: writefd_unbuffered failed to write 32768 bytes: phase "unknown": No buffer space available rsync error: error in rsync protocol data stream (code 12) at io.c(666) As I mentioned in my previous post, the system has 192MB RAM, 400MB swap. The file system I am trying to copy takes up about 15GB. -- Ray Lischner, author of C++ in a Nutshell http://www.tempest-sw.com/cpp -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
error in rsync protocol data stream
I am trying to backup an entire disk to a USB-mounted disk, for backup purposes. Many files are copied, but eventually rsync dies: $ rsync -axHSv --delete /backup /media/sda1 ... rsync: connection unexpectedly closed (239508 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(189) I am running Suse 9.0 and rsync 2.6.0 on an AMD-K6-2/450 (192MB RAM, 400MB swap). I ran fsck on the source and destination partitions (ext3), and both are error-free. Can anyone shed some light on what is going wrong? Thanks. -- Ray Lischner, author of C++ in a Nutshell http://www.tempest-sw.com/cpp -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
RE: error in rsync protocol data stream (code 12) at io.c(298)
The "--blocking-io" option fixed the problem. Thanks to jw for the solution. Thanks also to Wayne Davison for his response. Doug -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jw schultz Sent: Tuesday, December 30, 2003 12:45 PM To: [EMAIL PROTECTED] Subject: Re: error in rsync protocol data stream (code 12) at io.c(298) On Tue, Dec 30, 2003 at 12:23:30PM -0800, Doug Floer wrote: > I'm running into a problem rsynchronizing over an rsh connection on the same > subnet. I get variations of the "unexpected tag" error, consistently failing > within io.c at line 298: > > unexpected tag 88 > rsync error: error in rsync protocol data stream (code 12) at io.c(298) > > Here's the rsync command I've been using: > > rsync -lrpogtz --delete --rsh=rsh --rsync-path=/usr/local/bin/rsync /home dest:/ > > I've been all over the net looking for help and am about to give up. Can anyone > out there provide some suggestions? This is probably a [non]blocking io problem. Rsync has two options for that. Try them. --blocking-io use blocking IO for the remote shell --no-blocking-ioturn off --blocking-io You also failed to say what platform and rsync version. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream (code 12) at io.c(298)
On Tue, Dec 30, 2003 at 12:23:30PM -0800, Doug Floer wrote: > rsync -lrpogtz --delete --rsh=rsh --rsync-path=/usr/local/bin/rsync /home dest:/ One quick thing to try is removing the -z option. The 2.6.0 release has some fixes for the compression code (when it gets released in a couple days). ..wayne.. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream (code 12) at io.c(298)
On Tue, Dec 30, 2003 at 12:23:30PM -0800, Doug Floer wrote: > I'm running into a problem rsynchronizing over an rsh connection on the same > subnet. I get variations of the "unexpected tag" error, consistently failing > within io.c at line 298: > > unexpected tag 88 > rsync error: error in rsync protocol data stream (code 12) at io.c(298) > > Here's the rsync command I've been using: > > rsync -lrpogtz --delete --rsh=rsh --rsync-path=/usr/local/bin/rsync /home dest:/ > > I've been all over the net looking for help and am about to give up. Can anyone > out there provide some suggestions? This is probably a [non]blocking io problem. Rsync has two options for that. Try them. --blocking-io use blocking IO for the remote shell --no-blocking-ioturn off --blocking-io You also failed to say what platform and rsync version. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
error in rsync protocol data stream (code 12) at io.c(298)
I'm running into a problem rsynchronizing over an rsh connection on the same subnet. I get variations of the "unexpected tag" error, consistently failing within io.c at line 298: unexpected tag 88 rsync error: error in rsync protocol data stream (code 12) at io.c(298) Here's the rsync command I've been using: rsync -lrpogtz --delete --rsh=rsh --rsync-path=/usr/local/bin/rsync /home dest:/ I've been all over the net looking for help and am about to give up. Can anyone out there provide some suggestions? Regards, Doug -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
error in rsync protocol data stream (code 12) at io.c
I DID read the archives and from them figured that I would receive a very helpful responce from you Mr. Schultz. Thanks for your attention. The recomendation to turn up verbosity on the client did not help. I still only know that I can connect and then I get an error as shown below: [EMAIL PROTECTED] admin]# rsync -az mysql.sql vader::vice opening tcp connection to vader port 873 rsync: connection unexpectedly closed (0 bytes read so far) _exit_cleanup(code=12, file=io.c, line=165): entered rsync error: error in rsync protocol data stream (code 12) at io.c(165) _exit_cleanup(code=12, file=io.c, line=165): about to call exit(12) [EMAIL PROTECTED] admin]# Nothing that I can think of has changed on either the server or clients but obviously something must have because it was working in the past. I updated rsync, so it is no longer 17 months outdated: >>> (09:01pm) ([EMAIL PROTECTED]) (0/pts/0) (~) # rsync --version rsync version 2.5.6 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 comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. See the GNU General Public Licence for details. One thing I have noticed while troubleshooting is that other rsync servers with the same configuration, ie. same rsyncd.conf and xinetd.d/rsync config respond differently to netcat as shown below: Working Rsync server: [EMAIL PROTECTED] admin]# nc -vvv excelsior 873 excelsior.ait.nrl.navy.mil [132.250.128.31] 873 (rsync) open @RSYNCD: 26 @ERROR: protocol startup error sent 1, rcvd 43 Not Working (vader): [EMAIL PROTECTED] admin]# nc -vvv vader 873 vader.ait.nrl.navy.mil [132.250.129.162] 873 (rsync) open sent 2, rcvd 0 So it does look like a network problem. I have disabled both firewalls on each machine, even though they shouldn't be affecting this and I still get the same thing. I have moved the /etc/hosts.allow files out of the way along with /etc/hosts.deny. Running tcpdump on vader while I try to rsync from vice shows the packets are getting there: >>> (09:16pm) ([EMAIL PROTECTED]) (0/pts/0) (~) # tcpdump -i eth0 | grep vice tcpdump: listening on eth0 21:17:44.973404 vice.48443 > vader.rsync: S 4014526995:4014526995(0) win 5840 (DF) 21:17:44.973471 vader.rsync > vice.48443: S 668679285:668679285(0) ack 4014526996 win 5792 (DF) 21:17:44.973614 vice.48443 > vader.rsync: . ack 1 win 5840 (DF) 21:17:44.973678 vice.48443 > vader.rsync: P 1:13(12) ack 1 win 5840 (DF) 21:17:44.973708 vader.rsync > vice.48443: . ack 13 win 1448 (DF) 21:17:44.973957 vader.rsync > vice.48443: F 1:1(0) ack 13 win 1448 (DF) 21:17:44.974387 vice.48443 > vader.rsync: F 13:13(0) ack 2 win 5840 (DF) 21:17:44.974413 vader.rsync > vice.48443: . ack 14 win 1448 (DF) So I dont think it is a network problem, the packets from vice are being sent correctly and are being received. The rsync server on vader does not respond correctly. Do you have any ideas on what else I can change or test? Thanks, Jonathan Sabo Code 5580 NRL -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: error in rsync protocol data stream (code 12) at io.c
On Mon, Oct 06, 2003 at 11:42:00AM -0400, jonathan sabo wrote: > List, > > I am having trouble with a previously working rsync server. > > Version: > > ># rsync --version > >rsync version 2.5.4 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 While 2.5.4 was obsoleted about 17 months ago this is unlikely to be a bug. > Rsync is running and I can connect to it with netcat from the server > vice. It shows the port is open. On vader which is the rsync server, > the disk is not full. > > /dev/sdb1352153072 124431844 209832856 38% /vader1 > > I had been running a script to rsync over a bunch of stuff but now its > giving me this error: > > [EMAIL PROTECTED] admin]# rsync -avz mysql.sql vader::vice > rsync: connection unexpectedly closed (0 bytes read so far) > rsync error: error in rsync protocol data stream (code 12) at io.c(150) > > I have been reading the posts and havent found an answer yet. Your help > is greatly appreciated. Apparently you didn't read the archives. Start by examining what might have changed. Look at the logs on vader. Then increment the verbosity at the client. If no other error messages turn up it is probably a firewall dropping the session. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
error in rsync protocol data stream (code 12) at io.c
List, I am having trouble with a previously working rsync server. Version: # rsync --version rsync version 2.5.4 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 rsyncd.conf : # RSYNCD Configuration [vice] path = /vader1/admin/backup/vice/ comment = vice msqldb backup hosts allow = 'ip address of vice' uid = 0 gid = 0 max connections = 30 use chroot = yes read only = no Rsync is running and I can connect to it with netcat from the server vice. It shows the port is open. On vader which is the rsync server, the disk is not full. /dev/sdb1352153072 124431844 209832856 38% /vader1 I had been running a script to rsync over a bunch of stuff but now its giving me this error: [EMAIL PROTECTED] admin]# rsync -avz mysql.sql vader::vice rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(150) I have been reading the posts and havent found an answer yet. Your help is greatly appreciated. Thanks, -- Jonathan W. Sabo Code 5580 Naval Research Lab [EMAIL PROTECTED] Fax: (202)-404-1190 Phone: (202)-767-3901 -- To unsubscribe or change options: http://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(463)
> The remote disk is full. Is there a chance that > rsync could give a more descriptive error ? I sent a suggested patch for rsync 2.5.6 back in May: http://lists.samba.org/pipermail/rsync/2003-May/010757.html http://lists.samba.org/pipermail/rsync/2003-May/010763.html John -- To unsubscribe or change options: http://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(463)
On Sat, 13 Sep 2003, Dag Wieers wrote: > Using rsync-2.5.6 I get the exact same error: > > building file list ... > 28844 files to consider > apt/packages/ > apt/packages/avifile/ > apt/packages/avifile/avifile-0.7.34-1.dag.rh90.i386.rpm > rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe > rsync error: error in rsync protocol data stream (code 12) at io.c(515) > > I'm now going to test with an unpatched rsync, although looking at the Red > Hat patches I don't see anything that could cause this. Ok, I found the FAQ ;) The remote disk is full. Is there a chance that rsync could give a more descriptive error ? The reason why I didn't look in the FAQ right away was because it looked like a real bug, not something that is known. -- dag wieers, [EMAIL PROTECTED], http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors] -- To unsubscribe or change options: http://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(463)
On Sat, 13 Sep 2003, Dag Wieers wrote:
> I'm having a problem rsyncing one file (since I signed it). It seems that
> the content of a file is able to cause problems in the protocol.
>
> building file list ...
> 28820 files to consider
> apt/packages/avifile/
> apt/packages/avifile/avifile-0.7.34-1.dag.rh90.i386.rpm
> rsync: error writing 4 unbuffered bytes - exiting: Broken pipe
> rsync error: error in rsync protocol data stream (code 12) at io.c(463)
>
> I'm using rsync-2.5.5-4 (the rsync shipped with RH9). The first time rsync
> halted (indefinitely), every other run gives the above error.
Using rsync-2.5.6 I get the exact same error:
building file list ...
28844 files to consider
apt/packages/
apt/packages/avifile/
apt/packages/avifile/avifile-0.7.34-1.dag.rh90.i386.rpm
rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown": Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(515)
I'm now going to test with an unpatched rsync, although looking at the Red
Hat patches I don't see anything that could cause this.
PS: Is there a reason why the Red Hat patches are not applied to the rsync
sourcecode ? I've attached them for inspection.
-- dag wieers, [EMAIL PROTECTED], http://dag.wieers.com/ --
[Any errors in spelling, tact or fact are transmission errors]
--- io.c.orig 2003-09-13 22:36:40.0 +0200
+++ io.c2003-09-13 22:39:13.0 +0200
@@ -509,7 +509,7 @@
* across the stream */
io_multiplexing_close();
rprintf(FERROR, RSYNC_NAME
- ": writefd_unbuffered failed to write %ld
bytes: phase \"%s\": %s\n",
+ ": writefd_unbuffered failed to write %lu
bytes: phase \"%s\": %s\n",
(long) len, io_write_phase,
strerror(errno));
exit_cleanup(RERR_STREAMIO);
@@ -605,7 +605,7 @@
}
while (len) {
- int n = MIN((int) len, IO_BUFFER_SIZE-io_buffer_count);
+ int n = MIN((ssize_t) len, IO_BUFFER_SIZE-io_buffer_count);
if (n > 0) {
memcpy(io_buffer+io_buffer_count, buf, n);
buf += n;
--- match.c.orig2003-09-13 22:39:22.0 +0200
+++ match.c 2003-09-13 22:42:59.0 +0200
@@ -153,12 +153,12 @@
last_i = -1;
if (verbose > 2)
- rprintf(FINFO,"hash search b=%ld len=%.0f\n",
+ rprintf(FINFO,"hash search b=%lu len=%.0f\n",
(long) s->n, (double)len);
/* cast is to make s->n signed; it should always be reasonably
* small */
- k = MIN(len, (OFF_T) s->n);
+ k = MIN(len, (ssize_t) s->n);
map = (schar *)map_ptr(buf,0,k);
@@ -173,7 +173,7 @@
end = len + 1 - s->sums[s->count-1].len;
if (verbose > 3)
- rprintf(FINFO, "hash search s->n=%ld len=%.0f count=%ld\n",
+ rprintf(FINFO, "hash search s->n=%lu len=%.0f count=%lu\n",
(long) s->n, (double) len, (long) s->count);
do {
@@ -190,13 +190,13 @@
sum = (s1 & 0x) | (s2 << 16);
tag_hits++;
- for (; j < (int) s->count && targets[j].t == t; j++) {
+ for (; j < (ssize_t) s->count && targets[j].t == t; j++) {
int l, i = targets[j].i;
if (sum != s->sums[i].sum1) continue;
/* also make sure the two blocks are the same length */
- l = MIN(s->n,len-offset);
+ l = MIN((ssize_t) s->n,len-offset);
if (l != s->sums[i].len) continue;
if (verbose > 3)
@@ -216,7 +216,7 @@
/* we've found a match, but now check to see
if last_i can hint at a better match */
- for (j++; j < (int) s->count && targets[j].t == t; j++) {
+ for (j++; j < (ssize_t) s->count && targets[j].t == t; j++) {
int i2 = targets[j].i;
if (i2 == last_i + 1) {
if (sum != s->sums[i2].sum1) break;
@@ -232,7 +232,7 @@
matched
rsync error: error in rsync protocol data stream (code 12) at io.c(463)
Hi, I'm having a problem rsyncing one file (since I signed it). It seems that the content of a file is able to cause problems in the protocol. building file list ... 28820 files to consider apt/packages/avifile/ apt/packages/avifile/avifile-0.7.34-1.dag.rh90.i386.rpm rsync: error writing 4 unbuffered bytes - exiting: Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(463) I'm using rsync-2.5.5-4 (the rsync shipped with RH9). The first time rsync halted (indefinitely), every other run gives the above error. Kind regards, -- dag wieers, [EMAIL PROTECTED], http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors] -- To unsubscribe or change options: http://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 (Broken pipe)
Just for the record, the patch to token.c for the -z bug that was discovered by Yasuoka Masahiko and patched by him and Wayne Davison has fixed the problem that I reported here: http://www.mail-archive.com/[EMAIL PROTECTED]/msg07289.html Thanks guys, this bug has been biting me for the past 6 months... -Andy -- To unsubscribe or change options: http://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 (Broken pipe)
On Wed, Jun 18, 2003 at 10:38:54AM -0400, Andrew J. Schorr wrote: > On Tue, Jun 17, 2003 at 06:35:50AM -0700, jw schultz wrote: > > > > You could try turning on transfer logging i suppose. If you > > haven't already done so you might want to use the "log file" > > option in case chroot is getting in the way. Beyond this i > > have no suggestions; i dont use rsyncd. > > I may be having a similar problem. I'm using rsync version 2.5.6cvs-20030205 > every night on Solaris 8/x86 to do a backup from a client system to a > backup server using rsyncd. Almost every night I see the following errors > logged on the rsyncd server: > > Jun 18 00:48:18 ead62 rsyncd[9632]: [ID 702911 daemon.warning] inflate returned -3 > (0 bytes) > Jun 18 00:48:18 ead62 rsyncd[9632]: [ID 702911 daemon.warning] rsync error: error in > rsync protocol data stream (code 12) at ../token.c(416) > Jun 18 00:48:18 ead62 rsyncd[9632]: [ID 702911 daemon.warning] rsync: connection > unexpectedly closed (197041 bytes read so far) > Jun 18 00:48:18 ead62 rsyncd[9632]: [ID 702911 daemon.warning] rsync error: error in > rsync protocol data stream (code 12) at ../io.c(187) > > And on the client side, I see the following error: > > rsync: writefd_unbuffered failed to write 42 bytes: phase "unknown": Broken pipe > rsync error: error in rsync protocol data stream (code 12) at ../io.c(622) > > This has been happening to me for months almost every night. I find > that I can check the return code from rsync to see whether the > transfer succeeded. If it failed, I simply try again, and it almost > always finishes the backup successfully on the second invocation. But if > not I keep retrying up to 10 times. I think one evening it took 9 attempts, > but most of the time it works in 2 tries. It's a hack, but it gets > the job done, and I was having no luck debugging the problem. "inflate returned -3" is a compression error where it has bad data. It could be there is a bug in zlib but it seems more likely there is something wrong on your systems, perhaps flaky hardware. I haven't looked into that part of the code much, it is possible this could be a symptom of a file being changed during the transfer. If this is happening that frequently i'd try not using the -z option. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://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 (Broken pipe)
On Tue, Jun 17, 2003 at 06:35:50AM -0700, jw schultz wrote: > > You could try turning on transfer logging i suppose. If you > haven't already done so you might want to use the "log file" > option in case chroot is getting in the way. Beyond this i > have no suggestions; i dont use rsyncd. I may be having a similar problem. I'm using rsync version 2.5.6cvs-20030205 every night on Solaris 8/x86 to do a backup from a client system to a backup server using rsyncd. Almost every night I see the following errors logged on the rsyncd server: Jun 18 00:48:18 ead62 rsyncd[9632]: [ID 702911 daemon.warning] inflate returned -3 (0 bytes) Jun 18 00:48:18 ead62 rsyncd[9632]: [ID 702911 daemon.warning] rsync error: error in rsync protocol data stream (code 12) at ../token.c(416) Jun 18 00:48:18 ead62 rsyncd[9632]: [ID 702911 daemon.warning] rsync: connection unexpectedly closed (197041 bytes read so far) Jun 18 00:48:18 ead62 rsyncd[9632]: [ID 702911 daemon.warning] rsync error: error in rsync protocol data stream (code 12) at ../io.c(187) And on the client side, I see the following error: rsync: writefd_unbuffered failed to write 42 bytes: phase "unknown": Broken pipe rsync error: error in rsync protocol data stream (code 12) at ../io.c(622) This has been happening to me for months almost every night. I find that I can check the return code from rsync to see whether the transfer succeeded. If it failed, I simply try again, and it almost always finishes the backup successfully on the second invocation. But if not I keep retrying up to 10 times. I think one evening it took 9 attempts, but most of the time it works in 2 tries. It's a hack, but it gets the job done, and I was having no luck debugging the problem. -Andy -- To unsubscribe or change options: http://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 (Broken pipe)
On Tue, Jun 17, 2003 at 09:10:38AM -0500, Nathaniel Case wrote: > On Mon, 16 Jun 2003 at 16:24:25 -0700, jw schultz wrote: > > > > > After looking at io.c, it seems like the problem (rather, the symptom) > > > for > > > this error message is a failed write() call (which explains the Broken > > > Pipe message to stderr). I thought maybe --blocking-io would avoid this > > > issue, but it still happened when using --blocking-io. > > > > It would seem that the server process (forked off from the > > daemon) is dying. Look in the rsyncd log file (may be > > syslog) for clues. > > Yes, this does appear to be what is happening. I actually had tried > looking at the daemon logs, but there didn't appear to be anything > remotely interesting in it. This is the only line I see in the log: > > 2003/06/16 16:23:48 [17924] rsync to blah/blah/Blah/ from [EMAIL PROTECTED] > (10.x.x.x) > > Is there any way to increase the verbosity for this? Adding -v's to the > daemon process didn't appear to affect it. Oh well, I guess it's time to > start debugging. You could try turning on transfer logging i suppose. If you haven't already done so you might want to use the "log file" option in case chroot is getting in the way. Beyond this i have no suggestions; i dont use rsyncd. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://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 (Broken pipe)
On Mon, 16 Jun 2003 at 16:24:25 -0700, jw schultz wrote: > > > After looking at io.c, it seems like the problem (rather, the symptom) > > for > > this error message is a failed write() call (which explains the Broken > > Pipe message to stderr). I thought maybe --blocking-io would avoid this > > issue, but it still happened when using --blocking-io. > > It would seem that the server process (forked off from the > daemon) is dying. Look in the rsyncd log file (may be > syslog) for clues. Yes, this does appear to be what is happening. I actually had tried looking at the daemon logs, but there didn't appear to be anything remotely interesting in it. This is the only line I see in the log: 2003/06/16 16:23:48 [17924] rsync to blah/blah/Blah/ from [EMAIL PROTECTED] (10.x.x.x) Is there any way to increase the verbosity for this? Adding -v's to the daemon process didn't appear to affect it. Oh well, I guess it's time to start debugging. - Nate Case <[EMAIL PROTECTED]> (not subscribed) -- To unsubscribe or change options: http://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 (Broken pipe)
On Mon, Jun 16, 2003 at 11:53:04AM -0500, Nate Case wrote: > I'm experiencing some unexpected behavior with rsync v2.5.6. After > looking around it seems like several people have experienced similar > problems in the past, but those appear to be old bugs that are solved now. > Also doesn't appear to be any direct bugfixes made for this issue since > 2.5.6. > > The strange thing is that things seem to work when I use ssh for > transport. However now I need to switch to using the rsync daemon > directly and this problem has arose. > > I'm pushing local data to a remote rsync backup server: > > ---[snip]--- > # rsync -a -v --modify-window=2 /backup/Source/Dir/ > [EMAIL PROTECTED]::backup/dest > Password: > building file list ... rsync: writefd_unbuffered failed to write 4092 > bytes: phase "send_file_entry": Broken pipe > rsync error: error in rsync protocol data stream (code 12) at io.c(515) > ---[snip]--- > > With more -v's, I end up with the same message at the end, but it's > preceeded by a bunch of lines like this (filenames altered): > > make_file(3,file1) > make_file(3,file2) > make_file(3,file3) > make_file(3,file4) > > It stops on the same file each time. I tried deleting this file to see if > it's just choking on a particular file (or type of file), but in that case > it just chokes on the next file (different type) in the directory. The > files in this directory are no bigger than 2MB. If I remove the > subdirectory entirely, it still just dies on the next file it encounters. > > The directories that I'm syncing do have a large number of files, but as I > mentioned earlier, it does seem to work when using "-e ssh". I do not > seem to be running out of memory. I also tried the same parameters but > breaking it up into smaller subdirectories, and it still failed after X > amount of files with the same error (I did not determine whether or not X > is always the same with using other directories). Note that this is > always occuring in the "building file list" stage, and not the actual file > transfer. > > After looking at io.c, it seems like the problem (rather, the symptom) for > this error message is a failed write() call (which explains the Broken > Pipe message to stderr). I thought maybe --blocking-io would avoid this > issue, but it still happened when using --blocking-io. It would seem that the server process (forked off from the daemon) is dying. Look in the rsyncd log file (may be syslog) for clues. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
rsync error: error in rsync protocol data stream (Broken pipe)
I'm experiencing some unexpected behavior with rsync v2.5.6. After looking around it seems like several people have experienced similar problems in the past, but those appear to be old bugs that are solved now. Also doesn't appear to be any direct bugfixes made for this issue since 2.5.6. The strange thing is that things seem to work when I use ssh for transport. However now I need to switch to using the rsync daemon directly and this problem has arose. I'm pushing local data to a remote rsync backup server: ---[snip]--- # rsync -a -v --modify-window=2 /backup/Source/Dir/ [EMAIL PROTECTED]::backup/dest Password: building file list ... rsync: writefd_unbuffered failed to write 4092 bytes: phase "send_file_entry": Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(515) ---[snip]--- With more -v's, I end up with the same message at the end, but it's preceeded by a bunch of lines like this (filenames altered): make_file(3,file1) make_file(3,file2) make_file(3,file3) make_file(3,file4) It stops on the same file each time. I tried deleting this file to see if it's just choking on a particular file (or type of file), but in that case it just chokes on the next file (different type) in the directory. The files in this directory are no bigger than 2MB. If I remove the subdirectory entirely, it still just dies on the next file it encounters. The directories that I'm syncing do have a large number of files, but as I mentioned earlier, it does seem to work when using "-e ssh". I do not seem to be running out of memory. I also tried the same parameters but breaking it up into smaller subdirectories, and it still failed after X amount of files with the same error (I did not determine whether or not X is always the same with using other directories). Note that this is always occuring in the "building file list" stage, and not the actual file transfer. After looking at io.c, it seems like the problem (rather, the symptom) for this error message is a failed write() call (which explains the Broken Pipe message to stderr). I thought maybe --blocking-io would avoid this issue, but it still happened when using --blocking-io. Does anyone have any ideas about what could be causing this? Thanks, - Nate Case <[EMAIL PROTECTED]> -- To unsubscribe or change options: http://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) atio.c(463)
On Thu, Jun 12, 2003 at 05:59:43PM -0700, Vlad Sweet wrote: > My setup rsync --version 2.5.5 > on client and server > client is behind firewall/nat > > on client I run: > rsync -av --progress 110mb_file.mov [EMAIL PROTECTED]::dir1 > on server: > rsync --daemon > > it asks for password, starts to transfer the file, and at about 80% gives me > this error message: > > <<==cut==>> > Password: > building file list ... > 1 file to consider > 110mb_file.mov > rsync: error writing 4 unbuffered bytes - exiting: Connection reset by peer > rsync error: error in rsync protocol data stream (code 12) at io.c(463) > <<==cut==>> > > after starting the transfer I monitored it with tcpdump on the server ... > where right about at 87% complete (--progress) i end up with following > tcpdump lines on the server, correct me if I'm wrong, but it looks like at > some point (87% through) my server started advertising TCP window of zero > size (win 0), and client timesout or something and gave the error: > [snip] It sounds like you are running out of disk space. You need enough space on the destination for two copies of the file. -- J.W. SchultzPegasystems Technologies email address: [EMAIL PROTECTED] Remember Cernan and Schmitt -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
rsync error: error in rsync protocol data stream (code 12) atio.c(463)
My setup rsync --version 2.5.5 on client and server client is behind firewall/nat on client I run: rsync -av --progress 110mb_file.mov [EMAIL PROTECTED]::dir1 on server: rsync --daemon it asks for password, starts to transfer the file, and at about 80% gives me this error message: <<==cut==>> Password: building file list ... 1 file to consider 110mb_file.mov rsync: error writing 4 unbuffered bytes - exiting: Connection reset by peer rsync error: error in rsync protocol data stream (code 12) at io.c(463) <<==cut==>> after starting the transfer I monitored it with tcpdump on the server ... where right about at 87% complete (--progress) i end up with following tcpdump lines on the server, correct me if I'm wrong, but it looks like at some point (87% through) my server started advertising TCP window of zero size (win 0), and client timesout or something and gave the error: <<==cut==>> 17:29:28.265592 box.example.com.rsync > 192.168.1.100.36310: R 1665045802:1665045802(0) win 0 (DF) 17:29:28.266160 192.168.1.100.36310 > box.example.com.rsync: . 102467925:102469373(1448) ack 94 win 5840 (DF) 17:29:28.266212 box.example.com.rsync > 192.168.1.100.36310: R 1665045802:1665045802(0) win 0 (DF) 17:29:28.266770 192.168.1.100.36310 > box.example.com.rsync: . 102469373:102470821(1448) ack 94 win 5840 (DF) 17:29:28.266821 box.example.com.rsync > 192.168.1.100.36310: R 1665045802:1665045802(0) win 0 (DF) 17:29:28.268887 192.168.1.100.36310 > box.example.com.rsync: . 102470821:102472269(1448) ack 94 win 5840 (DF) 17:29:28.268939 box.example.com.rsync > 192.168.1.100.36310: R 1665045802:1665045802(0) win 0 (DF) 17:29:28.269484 192.168.1.100.36310 > box.example.com.rsync: . 102472269:102473717(1448) ack 94 win 5840 (DF) 17:29:28.269536 box.example.com.rsync > 192.168.1.100.36310: R 1665045802:1665045802(0) win 0 (DF) 17:29:28.270718 192.168.1.100.36310 > box.example.com.rsync: . 102473717:102475165(1448) ack 94 win 5840 (DF) 17:29:28.270769 box.example.com.rsync > 192.168.1.100.36310: R 1665045802:1665045802(0) win 0 (DF) 17:29:28.271309 192.168.1.100.36310 > box.example.com.rsync: . 102475165:102476613(1448) ack 94 win 5840 (DF) 17:29:28.271362 box.example.com.rsync > 192.168.1.100.36310: R 1665045802:1665045802(0) win 0 (DF) 17:29:28.272825 192.168.1.100.36310 > box.example.com.rsync: P 102476613:102478061(1448) ack 94 win 5840 (DF) 17:29:28.272877 box.example.com.rsync > 192.168.1.100.36310: R 1665045802:1665045802(0) win 0 (DF) 17:29:28.273900 192.168.1.100.36310 > box.example.com.rsync: . 102478061:102479509(1448) ack 94 win 5840 (DF) 17:29:28.273952 box.example.com.rsync > 192.168.1.100.36310: R 1665045802:1665045802(0) win 0 (DF) 17:29:28.274998 box.example.com.rsync > 192.168.1.100.36310: R 1665045802:1665045802(0) win 0 (DF) 17:29:28.275592 box.example.com.rsync > 192.168.1.100.36310: R 1665045802:1665045802(0) win 0 (DF) 17:29:28.276221 box.example.com.rsync > 192.168.1.100.36310: R 1665045802:1665045802(0) win 0 (DF) 17:29:28.276828 box.example.com.rsync > 192.168.1.100.36310: R 1665045802:1665045802(0) win 0 (DF) 17:29:28.277437 box.example.com.rsync > 192.168.1.100.36310: R 1665045802:1665045802(0) win 0 (DF) 17:29:28.278042 box.example.com.rsync > 192.168.1.100.36310: R 1665045802:1665045802(0) win 0 (DF) <<==cut==>> so it does transfer about 90Mb before giving me this error. I also installed rsync-2.5.6 on both client and server - still same problem. rpms i used: rsync-2.5.5-1.i386.rpm and rsync-2.5.6-4.i386.rpm uname -a on client: Linux 2.4.18-14 #1 Wed Sep 4 12:13:11 EDT 2002 i686 athlon i386 GNU/Linux uname -a on server: Linux 2.4.20-8 #1 Thu Mar 13 17:54:28 EST 2003 i686 i686 i386 GNU/Linux RAM on client 512MB, server 128MB top on sever during transfer never showed more than 0.7 %MEM utilization for rsync, %CPU 5-8% df shows plenty of space left and permissions are full rwx for that user and group. I tested file transfer several times, at all times transfer would stop at the same 87% I should mention that rsync worked with smaller files size under 10 mb. I did not test other sizes. Could anyone point me in the right direction here, I'm way over my head here. please help! Vlad Network Admin -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Re: "error in rsync protocol data stream (code 12) at io.c(150)" revisited
Bart Coninckx kindly pointed out my typo: the variable to define is RSYNC_RSH, and not RSYNC_SSH. Works fine now. Thanks for your assistance. Herta -- 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: "error in rsync protocol data stream (code 12) at io.c(150)" revisited
Oops, I noticed I ran the command with the wrong rsync: Here's the proper error: bb> /usr/local/bin/rsync -a ccf.txt bbcom@tobias:/www2/virtualhosts/toledo/bbcom/ tobias.cc.kuleuven.ac.be: Connection refused rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(150) (fwiiw the command in the original message ran against rsync version 2.4.6 protocol version 24) Sorry for the confusion. Herta Herta Van den Eynde wrote: > I browsed the web and the archive, and apart from someone asking whether > anyone else had rsync problems after installing OpenSSH 3.4, I came up > empty. > Can anyone point me in the right direction to debug this? I've got over > 50 GB to keep in sync, and don't know of another elegant way to do it. > > Environment: > source system = bb: > - Linux version 2.4.7-10smp ([EMAIL PROTECTED]) (gcc > version 2.96 2731 (Red Hat Linux 7.1 2.96-98)) > - OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f > - rsync version 2.5.5 protocol version 26 > target system = tobias: > - Linux version 2.4.17 (root@www-100) (gcc version 2.95.4 (Debian > prerelease)) > - OpenSSH_3.4p1 Debian 1:3.4p1-1, SSH protocols 1.5/2.0, OpenSSL 0x00906 > - rsync version 2.5.6cvs protocol version 2603f > Neither system uses an rsync daemon. > > Here's the command and the resulting error: > > bb> ls -l ccf.txt > -rw-r--r--1 bbuser bbuser 46 Jul 2 12:02 ccf.txt > bb> echo $RSYNC_SSH > /usr/local/bin/rsync -i /home/bbuser/.ssh/bbcom-id-dsa > bb> rsync -a ccf.txt bbcom@tobias:/www2/virtualhosts/toledo/bbcom/ > tobias.cc.kuleuven.ac.be: Connection refused > unexpected EOF in read_timeout > > ssh by itself works as expected: > > bb> ssh -i ~/.ssh/bbcom-id-dsa -l bbcom tobias cat > /www2/virtualhosts/toledo/bbcom/t.txt > Hello from tobias > bb> ssh -i ~/.ssh/bbcom-id-dsa -l bbcom tobias date > Tue Oct 1 15:49:21 CEST 2002 > > And scp proves I can write in the target directory as well: > > bb> scp -i ~/.ssh/bbcom-id-dsa ccf.txt > bbcom@tobias:/www2/virtualhosts/toledo/bbcom/ > ccf.txt 100% |*|46 00:00 > > Any help greatly appreciated. > > Herta Van den Eynde > -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
"error in rsync protocol data stream (code 12) at io.c(150)" revisited
I browsed the web and the archive, and apart from someone asking whether anyone else had rsync problems after installing OpenSSH 3.4, I came up empty. Can anyone point me in the right direction to debug this? I've got over 50 GB to keep in sync, and don't know of another elegant way to do it. Environment: source system = bb: - Linux version 2.4.7-10smp ([EMAIL PROTECTED]) (gcc version 2.96 2731 (Red Hat Linux 7.1 2.96-98)) - OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090602f - rsync version 2.5.5 protocol version 26 target system = tobias: - Linux version 2.4.17 (root@www-100) (gcc version 2.95.4 (Debian prerelease)) - OpenSSH_3.4p1 Debian 1:3.4p1-1, SSH protocols 1.5/2.0, OpenSSL 0x00906 - rsync version 2.5.6cvs protocol version 2603f Neither system uses an rsync daemon. Here's the command and the resulting error: bb> ls -l ccf.txt -rw-r--r--1 bbuser bbuser 46 Jul 2 12:02 ccf.txt bb> echo $RSYNC_SSH /usr/local/bin/rsync -i /home/bbuser/.ssh/bbcom-id-dsa bb> rsync -a ccf.txt bbcom@tobias:/www2/virtualhosts/toledo/bbcom/ tobias.cc.kuleuven.ac.be: Connection refused unexpected EOF in read_timeout ssh by itself works as expected: bb> ssh -i ~/.ssh/bbcom-id-dsa -l bbcom tobias cat /www2/virtualhosts/toledo/bbcom/t.txt Hello from tobias bb> ssh -i ~/.ssh/bbcom-id-dsa -l bbcom tobias date Tue Oct 1 15:49:21 CEST 2002 And scp proves I can write in the target directory as well: bb> scp -i ~/.ssh/bbcom-id-dsa ccf.txt bbcom@tobias:/www2/virtualhosts/toledo/bbcom/ ccf.txt 100% |*|46 00:00 Any help greatly appreciated. Herta Van den Eynde -- 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: 'error in rsync protocol data stream' - Tim Conway
Tim, Thanks for the thought, but I did all that back at the start of September when I first posted all the gory details up. Rsync, if it worked reliably, would be the perfect tool for the job. ..Trevor.. At 01:03 PM 9/17/2002 -0600, [EMAIL PROTECTED] wrote: >I'm sure your system is fine. What about the rsync, though? If it's >still 2.4.6, you're not getting anywhere. Get the source from >http://rsync.samba.org/ftp/rsync/rsync-2.5.5.tar.gz >untargz it somewhere, and in the directory it creates, which will be named >"rsync-2.5.5", type "./configure ; make ; make install" >On a properly-configured Linux system, those three commands should all run >successfully to completion, leaving you with the rsync binary as >/usr/local/bin/rsync, and the man pages distributed among /usr/local/man. >If your existing version is in /usr/bin or something, and you want to >override it, add "--prefix=/usr" or whatever, to redirect the install. >It's that easy. >If you want to leave off the installation stuff, you can, because the >binary is fully static and relocatable. >I can't guarantee that this will solve your problems. Sometimes, >individual problems can be fixed only by the individual involved. In my >application, I finally had to write a custom app, completely abandoning >rsync, because of the limitations of the platforms I'm required to use. I >still use rsync a lot, but as just another tool, like tar, cp, rsh, >whatever. > >Good luck. > >Tim Conway >[EMAIL PROTECTED] >303.682.4917 office, 303.921.0301 cell >Philips Semiconductor - Longmont TC >1880 Industrial Circle, Suite D >Longmont, CO 80501 >Available via SameTime Connect within Philips, caesupport2 on AIM >"There are some who call me Tim?" > > > > >Trevor Marshall <[EMAIL PROTECTED]> >Sent by: [EMAIL PROTECTED] >09/17/2002 11:10 AM > > >To: [EMAIL PROTECTED] >cc: (bcc: Tim Conway/LMT/SC/PHILIPS) >Subject:Re: 'error in rsync protocol data stream' - Tim Conway >Classification: > > > >Tim, >I reported a protocol data stream error on 9/8/2002 >Deatils are in my postes at that time >rsync still fails everytime I run it. > >This time I added three v's as you just suggested and rsync just hung with >two tasks in execution thus: >root 3178 0.1 0.9 1796 868 pts/1S09:57 0:00 >/usr/bin/rsync -vvva --delete --exclude=root/snapsh >root 3179 0.0 0.6 1628 632 pts/1S09:57 0:00 >/usr/bin/rsync -vvva --delete --exclude=root/snapsh > >and the last data rsync put out was: >make_file(4,var/adm/fillup-templates/i4l.templ) >make_file(4,var/adm/fillup-templates/i4l_b1.templ) >make_file(4,var/adm/fillup-templates/i4l_default.templ) >make_file(4,var/adm/fillup-templates/i4l_hardware.templ) >make_file(4,var/adm/fillup-templates/i4l_hisax.templ) >make_file(4,var/adm/fillup-templates/i4l_icn.templ) >make_file(4,var/adm/fillup-templates/i4l_ignore.templ) >---then hangs- > >Any ideas? >Last time I was told to upgrade my hardware and OS. >I run a solid, scrupulously updated, SuSE 7.3 system on reliable P-II/400 >hardware > >..Trevor Marshall... > >At 10:36 AM 9/17/2002 -0600, you wrote: >>Certainly, you should upgrade your rsync. 2.4.6 had more than its share >>of problems. 2.5.5 is generating few complaints. As far as what's >>actually happening to you, if it continues after the upgrade, give us >>another run with more "v"s. >> >>Tim Conway >>[EMAIL PROTECTED] >>303.682.4917 office, 303.921.0301 cell >>Philips Semiconductor - Longmont TC >>1880 Industrial Circle, Suite D >>Longmont, CO 80501 >>Available via SameTime Connect within Philips, caesupport2 on AIM >>"There are some who call me Tim?" >> >> >> >> >>Pascal Bourguignon <[EMAIL PROTECTED]> >>Sent by: [EMAIL PROTECTED] >>09/16/2002 11:39 PM >>Please respond to pjb >> >> >>To: [EMAIL PROTECTED] >>cc: (bcc: Tim Conway/LMT/SC/PHILIPS) >> Subject:'error in rsync protocol data stream' >>Classification: >> >> >> >>Hello, >> >>While doing a local "rsync" with: >> >> rsync -v -auxHS --force / /backup/ >> >>(on /backup is mounted another disk), I get these errors: >> >>rsync: error writing 4 unbuffered bytes - exiting: Broken pipe >>rsync error: error in rsync protocol data stream (code 12) at
Re: 'error in rsync protocol data stream' - Tim Conway
I'm sure your system is fine. What about the rsync, though? If it's
still 2.4.6, you're not getting anywhere. Get the source from
http://rsync.samba.org/ftp/rsync/rsync-2.5.5.tar.gz
untargz it somewhere, and in the directory it creates, which will be named
"rsync-2.5.5", type "./configure ; make ; make install"
On a properly-configured Linux system, those three commands should all run
successfully to completion, leaving you with the rsync binary as
/usr/local/bin/rsync, and the man pages distributed among /usr/local/man.
If your existing version is in /usr/bin or something, and you want to
override it, add "--prefix=/usr" or whatever, to redirect the install.
It's that easy.
If you want to leave off the installation stuff, you can, because the
binary is fully static and relocatable.
I can't guarantee that this will solve your problems. Sometimes,
individual problems can be fixed only by the individual involved. In my
application, I finally had to write a custom app, completely abandoning
rsync, because of the limitations of the platforms I'm required to use. I
still use rsync a lot, but as just another tool, like tar, cp, rsh,
whatever.
Good luck.
Tim Conway
[EMAIL PROTECTED]
303.682.4917 office, 303.921.0301 cell
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, caesupport2 on AIM
"There are some who call me Tim?"
Trevor Marshall <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
09/17/2002 11:10 AM
To: [EMAIL PROTECTED]
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject:Re: 'error in rsync protocol data stream' - Tim Conway
Classification:
Tim,
I reported a protocol data stream error on 9/8/2002
Deatils are in my postes at that time
rsync still fails everytime I run it.
This time I added three v's as you just suggested and rsync just hung with
two tasks in execution thus:
root 3178 0.1 0.9 1796 868 pts/1S09:57 0:00
/usr/bin/rsync -vvva --delete --exclude=root/snapsh
root 3179 0.0 0.6 1628 632 pts/1S09:57 0:00
/usr/bin/rsync -vvva --delete --exclude=root/snapsh
and the last data rsync put out was:
make_file(4,var/adm/fillup-templates/i4l.templ)
make_file(4,var/adm/fillup-templates/i4l_b1.templ)
make_file(4,var/adm/fillup-templates/i4l_default.templ)
make_file(4,var/adm/fillup-templates/i4l_hardware.templ)
make_file(4,var/adm/fillup-templates/i4l_hisax.templ)
make_file(4,var/adm/fillup-templates/i4l_icn.templ)
make_file(4,var/adm/fillup-templates/i4l_ignore.templ)
---then hangs-
Any ideas?
Last time I was told to upgrade my hardware and OS.
I run a solid, scrupulously updated, SuSE 7.3 system on reliable P-II/400
hardware
..Trevor Marshall...
At 10:36 AM 9/17/2002 -0600, you wrote:
>Certainly, you should upgrade your rsync. 2.4.6 had more than its share
>of problems. 2.5.5 is generating few complaints. As far as what's
>actually happening to you, if it continues after the upgrade, give us
>another run with more "v"s.
>
>Tim Conway
>[EMAIL PROTECTED]
>303.682.4917 office, 303.921.0301 cell
>Philips Semiconductor - Longmont TC
>1880 Industrial Circle, Suite D
>Longmont, CO 80501
>Available via SameTime Connect within Philips, caesupport2 on AIM
>"There are some who call me Tim?"
>
>
>
>
>Pascal Bourguignon <[EMAIL PROTECTED]>
>Sent by: [EMAIL PROTECTED]
>09/16/2002 11:39 PM
>Please respond to pjb
>
>
>To: [EMAIL PROTECTED]
>cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
>Subject:'error in rsync protocol data stream'
>Classification:
>
>
>
>Hello,
>
>While doing a local "rsync" with:
>
> rsync -v -auxHS --force / /backup/
>
>(on /backup is mounted another disk), I get these errors:
>
>rsync: error writing 4 unbuffered bytes - exiting: Broken pipe
>rsync error: error in rsync protocol data stream (code 12) at io.c(463)
>rsync: error writing 69 unbuffered bytes - exiting: Broken pipe
>rsync error: error in rsync protocol data stream (code 12) at io.c(463)
>
>
>[pascal@thalassa mnt]$ rsync --version
>rsync version 2.5.5 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
>
>
>What's the problem?
>Should I upgrade rsync?
>
>
>--
>__Pascal_Bourguignon__ http://www.informatimago.com/
>--
> The name is Baud,.
Re: 'error in rsync protocol data stream' - Tim Conway
Tim, I just got the hung rsync window to respond to a Control-C and it put out the following text (including a few of those make files that were just before it hung.. make_file(4,var/adm/fillup-templates/i4l_default.templ) make_file(4,var/adm/fillup-templates/i4l_hardware.templ) make_file(4,var/adm/fillup-templates/i4l_hisax.templ) make_file(4,var/adm/fillup-templates/i4l_icn.templ) make_file(4,var/adm/fillup-templates/i4l_ignore.templ) rsync error: received SIGUSR1 or SIGINT (code 20) at rsync.c(229) _exit_cleanup(code=20, file=rsync.c, line=229): about to call exit(20) rsync: error writing 70 unbuffered bytes - exiting: Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(463) _exit_cleanup(code=12, file=io.c, line=463): about to call exit(12) ..trevor.. -- 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: 'error in rsync protocol data stream' - Tim Conway
Tim, I reported a protocol data stream error on 9/8/2002 Deatils are in my postes at that time rsync still fails everytime I run it. This time I added three v's as you just suggested and rsync just hung with two tasks in execution thus: root 3178 0.1 0.9 1796 868 pts/1S09:57 0:00 /usr/bin/rsync -vvva --delete --exclude=root/snapsh root 3179 0.0 0.6 1628 632 pts/1S09:57 0:00 /usr/bin/rsync -vvva --delete --exclude=root/snapsh and the last data rsync put out was: make_file(4,var/adm/fillup-templates/i4l.templ) make_file(4,var/adm/fillup-templates/i4l_b1.templ) make_file(4,var/adm/fillup-templates/i4l_default.templ) make_file(4,var/adm/fillup-templates/i4l_hardware.templ) make_file(4,var/adm/fillup-templates/i4l_hisax.templ) make_file(4,var/adm/fillup-templates/i4l_icn.templ) make_file(4,var/adm/fillup-templates/i4l_ignore.templ) ---then hangs- Any ideas? Last time I was told to upgrade my hardware and OS. I run a solid, scrupulously updated, SuSE 7.3 system on reliable P-II/400 hardware ..Trevor Marshall... At 10:36 AM 9/17/2002 -0600, you wrote: >Certainly, you should upgrade your rsync. 2.4.6 had more than its share >of problems. 2.5.5 is generating few complaints. As far as what's >actually happening to you, if it continues after the upgrade, give us >another run with more "v"s. > >Tim Conway >[EMAIL PROTECTED] >303.682.4917 office, 303.921.0301 cell >Philips Semiconductor - Longmont TC >1880 Industrial Circle, Suite D >Longmont, CO 80501 >Available via SameTime Connect within Philips, caesupport2 on AIM >"There are some who call me Tim?" > > > > >Pascal Bourguignon <[EMAIL PROTECTED]> >Sent by: [EMAIL PROTECTED] >09/16/2002 11:39 PM >Please respond to pjb > > > To: [EMAIL PROTECTED] >cc: (bcc: Tim Conway/LMT/SC/PHILIPS) >Subject:'error in rsync protocol data stream' >Classification: > > > >Hello, > >While doing a local "rsync" with: > > rsync -v -auxHS --force / /backup/ > >(on /backup is mounted another disk), I get these errors: > >rsync: error writing 4 unbuffered bytes - exiting: Broken pipe >rsync error: error in rsync protocol data stream (code 12) at io.c(463) >rsync: error writing 69 unbuffered bytes - exiting: Broken pipe >rsync error: error in rsync protocol data stream (code 12) at io.c(463) > > >[pascal@thalassa mnt]$ rsync --version >rsync version 2.5.5 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 > > >What's the problem? >Should I upgrade rsync? > > >-- >__Pascal_Bourguignon__ http://www.informatimago.com/ >-- > The name is Baud,.. James Baud. >-- >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: 'error in rsync protocol data stream'
Certainly, you should upgrade your rsync. 2.4.6 had more than its share
of problems. 2.5.5 is generating few complaints. As far as what's
actually happening to you, if it continues after the upgrade, give us
another run with more "v"s.
Tim Conway
[EMAIL PROTECTED]
303.682.4917 office, 303.921.0301 cell
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, caesupport2 on AIM
"There are some who call me Tim?"
Pascal Bourguignon <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
09/16/2002 11:39 PM
Please respond to pjb
To: [EMAIL PROTECTED]
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject: 'error in rsync protocol data stream'
Classification:
Hello,
While doing a local "rsync" with:
rsync -v -auxHS --force / /backup/
(on /backup is mounted another disk), I get these errors:
rsync: error writing 4 unbuffered bytes - exiting: Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(463)
rsync: error writing 69 unbuffered bytes - exiting: Broken pipe
rsync error: error in rsync protocol data stream (code 12) at io.c(463)
[pascal@thalassa mnt]$ rsync --version
rsync version 2.5.5 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
What's the problem?
Should I upgrade rsync?
--
__Pascal_Bourguignon__ http://www.informatimago.com/
--
The name is Baud,.. James Baud.
--
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
'error in rsync protocol data stream'
Hello, While doing a local "rsync" with: rsync -v -auxHS --force / /backup/ (on /backup is mounted another disk), I get these errors: rsync: error writing 4 unbuffered bytes - exiting: Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(463) rsync: error writing 69 unbuffered bytes - exiting: Broken pipe rsync error: error in rsync protocol data stream (code 12) at io.c(463) [pascal@thalassa mnt]$ rsync --version rsync version 2.5.5 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 What's the problem? Should I upgrade rsync? -- __Pascal_Bourguignon__ http://www.informatimago.com/ -- The name is Baud,.. James Baud. -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
error in rsync protocol data stream (code 12)
Hello! A good day to you all. I got some error messages from rsync: rsync: error writing 4092 unbuffered bytes - exiting: Connection reset by peerrsync: read error: Connection reset by peerrsync error: error in rsync protocol data stream (code 12) at io.c(162)rsync error: error in rsync protocol data stream (code 12) at io.c(463) ...used the stock rsync from the rh7.0 distro. Comments are more than welcome. Thanks! Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes
Re: "error in rsync protocol data stream"
On Tue, Apr 30, 2002 at 08:57:52AM -0400, Scott Lipcon wrote: > I just upgraded back to 2.5.5 (actually 2.5.5_1, from the FreeBSD > Ports tree - the _1 means its been patched I think) and the problem > seems to have disappeared. Maybe it was a zlib problem dealing with > a specific data pattern or something? I'll leave it at 2.5.5 and see > if I can reproduce the error in the next few days. Yes. Please see http://www.freebsd.org/cgi/query-pr.cgi?pr=36998 for the complete story. The PORTREVISION should probably have been bumped after this. -- Jos Backus _/ _/_/_/Santa Clara, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/_/ [EMAIL PROTECTED] _/_/ _/_/_/use Std::Disclaimer; -- 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: "error in rsync protocol data stream"
> I know this is late but nobody else appears to have responded. I did get one email off list from someone having a similar problem, except he was dealing with Solaris, not BSD machines. > A crashing problem on FreeBSD has been found where the rsync zlib library > crashes unless it is compiled with gcc -O2. It sounds like it's your > Sparc OpenBSD side that's crashing though so I wouldn't think it would > be the same problem. At least try it without -z. Downgrading the FreeBSD (client) side to 2.5.1 (the last binary package available for FreeBSD - I didn't try anything in between) fixed the problem. I just upgraded back to 2.5.5 (actually 2.5.5_1, from the FreeBSD Ports tree - the _1 means its been patched I think) and the problem seems to have disappeared. Maybe it was a zlib problem dealing with a specific data pattern or something? I'll leave it at 2.5.5 and see if I can reproduce the error in the next few days. Scott -- 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: "error in rsync protocol data stream"
I know this is late but nobody else appears to have responded. On Wed, Apr 03, 2002 at 11:43:48PM -0500, Scott Lipcon wrote: > Hello, > > I'm having a problem doing a remote rsync over ssh - i'm using a script that > has worked for quite a while, using rsync 2.4.6 on both ends. I upgraded the > "client" to 2.5.5, and began seeing this error: > > rsync: connection unexpectedly closed (158246 bytes read so far) > rsync error: error in rsync protocol data stream (code 12) at io.c(150) This message occurs any time the remote end disappears early. > At which time there is a large core file generated on the remote side > (unfortuantely, the debugger on the remote side isn't giving me anything > useful) > > I assumed that it was a bad interaction between the local 2.5.5 and the remote > 2.4.6, so I upgraded the remote machine to 2.5.5 as well, and the problem > remains. My local machine is an athlon running FreeBSD 4.5, and the remote > side is a Sparc 5 running OpenBSD 2.8. The command line I'm using is: > > rsync -avz -P --delete --include-from=/u0/includes --partial remote:/ . > > I'd appreciate any ideas... please cc replies to me. > > Thanks, > > Scott A crashing problem on FreeBSD has been found where the rsync zlib library crashes unless it is compiled with gcc -O2. It sounds like it's your Sparc OpenBSD side that's crashing though so I wouldn't think it would be the same problem. At least try it without -z. - 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
rsync 2.5.5 - "error in rsync protocol data stream"
I upgraded rsync from 2.3.1 to 2.5.5, and now one of my nightly jobs fails with building file list ... done rsync: connection unexpectedly closed (11980581 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(150) rsync: connection unexpectedly closed (8 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(150) I probably just need suggestions on how to better diagnose this, but maybe someone can actually tell me what's going on here. Here's what seems relevant: The transfer only fails for certain large directories -- however, there are no complaints of running out of space on the destination host. (A test, where I invoked rsync separately for each subdirectory, generated no errors -- does rsync need a certain amount of free disk for some temp file, which grows with the size of the source data?) rsync 2.5.5 (compiled from source with SUNWspro-5.0, on the same machine which is running the rsync) hindenburg# /opt/rsync-2.5.5/bin/rsync --version rsync version 2.5.5 protocol version 26 Copyright (C) 1996-2002 by Andrew Tridgell and others <http://rsync.samba.org/> Capabilities: 32-bit files, socketpairs, hard links, symlinks, batchfiles, no IPv6, 32-bit system inums, 64-bit internal inums Both hosts run Solaris 2.5.1 The transfer invoked as /opt/rsync-2.5.5/bin/rsync -azvH \ --rsync-path=/opt/rsync-2.5.5/bin/rsync \ --delete \ /export/disk01/packages/ lusitania:/export/disk01/packages/ The source partition is /dev/md/dsk/d0 16489088 14390650 160376890%/export/disk01 the destination is /dev/md/dsk/d0 16492328 14391420 45167897%/export/disk01 so, there isn't as much space on the targe as the source, but I don't *think* there's anywhere near 451678 KB of updates. Thanks, as always, for any clues! David Harnick-Shapiro <[EMAIL PROTECTED]> -- To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html
