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
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
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
, 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
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)
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
: 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
:
--
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
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()
\ /etc \
[EMAIL PROTECTED]:/home/backup/thismachine/
I am getting the following error
ssh: connect to hostx.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
] 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
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
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
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
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
) [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
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
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) a
https://bugzilla.samba.org/show_bug.cgi?id=1508
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=1508
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Additional
https://bugzilla.samba.org/show_bug.cgi?id=1477
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
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
/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
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
--
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
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://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=716action=view)
Change option parsing
This patch separates the daemon-mode's option
https://bugzilla.samba.org/show_bug.cgi?id=1633
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
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
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
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
https://bugzilla.samba.org/show_bug.cgi?id=1502
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=1477
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Additional
https://bugzilla.samba.org/show_bug.cgi?id=1477
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
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
: 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
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'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
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
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).
]
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
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
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
.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
/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
==
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
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
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.
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
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:
Hello!
Agood 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
While this does appear to work in 2.5.4, I suspect that is because
of the 2.5.4 whole-file bug.
With 2.5.5 it fails again, with the following error message:
deflate on token returned 0 (16384 bytes left)
rsync error: error in rsync protocol data stream (code 12) at token.c(288)
According
Dave Dykstra wrote:
The rsync code that prints that error on line 270 of receiverc 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
Dave Dykstra wrote:
The rsync code that prints that error on line 270 of receiverc 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
| write failed on large_file2 : Success:12
| rsync error: error in file IO (code 11) at receiver.c(271)
| rsync: connection unexpectedly closed (201 bytes read so far)
| rsync error: error in rsync protocol data stream (code 12) at io.c(151)
Hi,
I would like to humbly apologies ... one
)
| rsync error: error in rsync protocol data stream (code 12) at
io.c(140)
I have only just subscribed to this mailing list, so apologies if I have
missed any discussion on this topic. A MHonArc conversion of rsync.mbox
(from rsync.samba.org) suggests I have. The 'patch' that has been
On Wed, Feb 27, 2002 at 02:57:59PM +, Andrew McGregor wrote:
| write failed on large_file2 : Success:12
| rsync error: error in file IO (code 11) at receiver.c(271)
| rsync: connection unexpectedly closed (201 bytes read so far)
| rsync error: error in rsync protocol data stream (code
unexpectedly closed (201 bytes read so far)
| rsync error: error in rsync protocol data stream (code 12) at
io.c(140)
I have only just subscribed to this mailing list, so apologies if I have
missed any discussion on this topic. A MHonArc conversion of rsync.mbox
(from rsync.samba.org) suggests I have
I was able to reproduce this between a Solaris 2.7 and 2.8 machine with and
without ssh, although I don't have any time to debug it today. Can
somebody try applying Jos Backus latest zlib 1.1.3 upgrade patch to see
if that helps?
- Dave
On Fri, Feb 01, 2002 at 02:01:03PM -0800, Stuart Anderson
On Fri, Feb 01, 2002 at 01:06:15PM -0800, Jos Backus wrote:
On Fri, Feb 01, 2002 at 02:18:06PM -0600, Dave Dykstra wrote:
Be careful with that, because rsync's zlib is modified from the standard.
Has somebody verified that the modification is not removed with the upgrade?
I was under the
/
/export/mirror/linux/redhat/7.1/en/iso/i386/seawolf-i386-powertools.iso
deflate on token returned 0 (16384 bytes left)
rsync error: error in rsync protocol data stream (code 12) at token.c(288)
rsync finished
The file has in fact been mirrored correctly (md5sum is identical),
however, the file
/mirror/linux/redhat/7.1/en/iso/i386/
/export/mirror/linux/redhat/7.1/en/iso/i386/seawolf-i386-powertools.iso
deflate on token returned 0 (16384 bytes left)
rsync error: error in rsync protocol data stream (code 12) at token.c(288)
rsync finished
The file has in fact been mirrored
files to consider.
export/mirror/linux/redhat/7.1/en/iso/i386/
/export/mirror/linux/redhat/7.1/en/iso/i386/seawolf-i386-powertools.iso
deflate on token returned 0 (16384 bytes left)
rsync error: error in rsync protocol data stream (code 12) at token.c(288)
rsync finished
On Fri, Feb 01, 2002 at 08:51:17AM -0800, Stuart Anderson wrote:
I also found on deja-news reports that this is a known and fixed problem
with zlib-1.1.2. Any chance of rsync upgrading to zlib-1.1.3?
Jos Backus posted a patch to do this a few days ago. Try applying his
patch and reporting back
According to Albert Chin:
On Fri, Feb 01, 2002 at 08:51:17AM -0800, Stuart Anderson wrote:
I also found on deja-news reports that this is a known and fixed problem
with zlib-1.1.2. Any chance of rsync upgrading to zlib-1.1.3?
Jos Backus posted a patch to do this a few days ago. Try
On Fri, Feb 01, 2002 at 09:09:18AM -0800, Stuart Anderson wrote:
According to sba:
No I did not apply the patch, but I verified the same problem with
rsync-2.4.8, is that sufficient?
No, because rsync-2.4.8 include the same security patch that went into
2.5.2 last weekend. If you could
On Fri, Feb 01, 2002 at 02:18:06PM -0600, Dave Dykstra wrote:
Be careful with that, because rsync's zlib is modified from the standard.
Has somebody verified that the modification is not removed with the upgrade?
I was under the erroneous assumption that these fixes had made it back into
According to Dave Dykstra:
On Fri, Feb 01, 2002 at 09:09:18AM -0800, Stuart Anderson wrote:
According to sba:
No I did not apply the patch, but I verified the same problem with
rsync-2.4.8, is that sufficient?
No, because rsync-2.4.8 include the same security patch that went into
Gomez [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
01/22/2002 10:21 AM
To: [EMAIL PROTECTED]
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject:error in rsync protocol data stream (code 12) at io.c(139)
Classification:
When trying to connect to a rsync
69 matches
Mail list logo
