Your message dated Thu, 12 May 2005 10:38:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#308733: rsync 2.6.4 server fails with rsync error in rsync
protocol data stream (code 12) at io.c(570)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 12 May 2005 02:17:26 +0000
>From [EMAIL PROTECTED] Wed May 11 19:17:26 2005
Return-path: <[EMAIL PROTECTED]>
Received: from zproxy.gmail.com [64.233.162.192]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DW3GQ-0006k0-00; Wed, 11 May 2005 19:17:26 -0700
Received: by zproxy.gmail.com with SMTP id 16so514000nzp
for <[EMAIL PROTECTED]>; Wed, 11 May 2005 19:16:55 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=beta; d=gmail.com;
h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
b=f0maZ3X6Ag0t1MIa5xSw1/4a4G9mvRDg59wzt8f5fTLQqCO70FKvxQtgkAInMRzXlUK1BCezl6Iki3uGYbqOGUjGpjjDyGqUI0BcVVaSLs0L9cgUiumnXwJZZO8rXh7xFoc/3ip2IK3XfIov84oJ6Vs+7j14LhO9WPLLByt5RxA=
Received: by 10.36.128.13 with SMTP id a13mr493651nzd;
Wed, 11 May 2005 19:16:55 -0700 (PDT)
Received: by 10.36.109.6 with HTTP; Wed, 11 May 2005 19:16:55 -0700 (PDT)
Message-ID: <[EMAIL PROTECTED]>
Date: Wed, 11 May 2005 22:16:55 -0400
From: hacker <[EMAIL PROTECTED]>
Reply-To: hacker <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: rsync 2.6.4 server fails with rsync error in rsync protocol data
stream (code 12) at io.c(570)
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: rsync
Version: 2.6.4-4
Severity: grave
Justification: renders package unusable
I upgraded from 2.6.4-2 to 2.6.4-4 on my local network server and now
my client gets an error:
$ rsync mydesktop::
rsync: read error: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(570)
_exit_cleanup(cope=3D3D12), file=3D3Dio.c, line=3D3D570): about to call exi=
t(12)
Also, I've upgraded my server to 2.6.4-5 and have same error.
So, I've downgraded my server to 2.6.4-2 and now can rsync ok. I've
tried all 3 versions (2.6.4-2,4,5) on my client, and all work ok on
the client side.
The only server that I can get working is 2.6.4-2. With this version,
I successfully use the following rsync commands:
$ rsync mydesktop::
$ rsync -avz --progress --delete mydesktop::rootdir/home/golfbuf/work/ work=
/
$ rsync -avz --progress mydesktop::rootdir/home/golfbuf/myfile.txt mydir/
[EMAIL PROTECTED]
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2-686
Locale: LANG=3D3Den_US, LC_CTYPE=3D3Den_US (charmap=3D3DISO-8859-1)
Versions of packages rsync depends on:
ii libc6 2.3.2.ds1-21 GNU C Library: Shared librarie=
s an
ii libpopt0 1.7-5 lib for parsing cmdline parame=
ters
-- no debconf information
---------------------------------------
Received: (at 308733-done) by bugs.debian.org; 12 May 2005 08:38:38 +0000
>From [EMAIL PROTECTED] Thu May 12 01:38:38 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mx.wurtel.net (gw.wurtel.net) [195.64.88.114] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DW9DK-0008NG-00; Thu, 12 May 2005 01:38:38 -0700
Received: from wurtel ([192.168.1.1] helo=wurtel.net)
by gw.wurtel.net with esmtp (Exim 3.36 #1 (Debian))
id 1DW9D6-000077-00; Thu, 12 May 2005 10:38:24 +0200
Received: from paul by wurtel.net with local (Exim 4.33 #1 (Debian))
id 1DW9D2-00079l-Ti; Thu, 12 May 2005 10:38:20 +0200
Date: Thu, 12 May 2005 10:38:20 +0200
From: Paul Slootman <[EMAIL PROTECTED]>
To: hacker <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#308733: rsync 2.6.4 server fails with rsync error in rsync
protocol data stream (code 12) at io.c(570)
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.6i
X-Scanner: exiscan *1DW9D6-000077-00*oFZP29HUQC2*Wurtel
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
On Wed 11 May 2005, hacker wrote:
> Package: rsync
> Version: 2.6.4-4
> Severity: grave
> Justification: renders package unusable
>
> I upgraded from 2.6.4-2 to 2.6.4-4 on my local network server and now
> my client gets an error:
>
> $ rsync mydesktop::
>
> rsync: read error: Connection reset by peer (104)
> rsync error: error in rsync protocol data stream (code 12) at io.c(570)
> _exit_cleanup(cope=3D12), file=3Dio.c, line=3D570): about to call exit(12)
>
> Also, I've upgraded my server to 2.6.4-5 and have same error.
Your mirror seems to be a bit behind, 2.6.4-6 was uploaded two days ago.
Please check existing bugs before reporting a new one.
This is essentially a duplication of #308428 and #307923, which were
fixed in the upload of 2.6.4-6.
I'm closing this bug report now. If you still have problems with
2.6.4-6, feel free to reopen or to file a new bug. However, I'm fairly
certain that your problem has been fixed there.
Paul Slootman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
