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 dat
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: htt
https://bugzilla.samba.org/show_bug.cgi?id=6032
m...@mattmccutchen.net changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
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
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
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
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
(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
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
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) ..
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
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&q
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
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()
-------------
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 purpos
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 a
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 beli
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
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
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 i
$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
y. 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 (co
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.sam
ytes 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 p
sed (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
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
es 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
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 Comments
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 ?
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 in
G: 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
--
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
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 option
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 p
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
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 hav
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=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
https://bugzilla.samba.org/show_bug.cgi?id=1477
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Additional Comments
https://bugzilla.samba.org/show_bug.cgi?id=1477
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
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
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 remo
> 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 wit
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 -v
. 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
nection 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://lis
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/li
ng 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 u
ing 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 ch
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 h
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 th
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.
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
ot
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
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: er
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 Nutshel
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
-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 P
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. T
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
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
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).
..w
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
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'
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
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
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
> 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
386.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
es/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 shippe
.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 a
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
ckup 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: er
8: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: conn
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
> > > Pi
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
> > i
shing 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&quo
rce/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 sam
t 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 b
;==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 wi
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-
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
> a
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.
ia 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
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
Class
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
y: [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:
>
>
>
>H
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
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)
rs
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
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
> 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
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 ea
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
1 - 100 of 126 matches
Mail list logo
