Your message dated Thu, 15 Sep 2005 11:44:48 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#310739: rsync fails to connect on kernel-2.6
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; 25 May 2005 15:30:17 +0000
>From [EMAIL PROTECTED] Wed May 25 08:30:17 2005
Return-path: <[EMAIL PROTECTED]>
Received: from zproxy.gmail.com [64.233.162.195]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Daxpp-0001uo-00; Wed, 25 May 2005 08:30:17 -0700
Received: by zproxy.gmail.com with SMTP id 18so293116nzp
for <[EMAIL PROTECTED]>; Wed, 25 May 2005 08:29:47 -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=f0BwjdVTDKmwDAlfHU/B0KYVKwumhrGnSuFshEp6wH6irEVq6i/vEbmZ3v+rdOIWOsjNwWbLwbtm9Y1u0JQQZU3o+MYElnh16S91OaFhbYM7S7UMMwRORxQYsXk8AdfQ9UF7xVTs+je6L6Ys1HaFqiZdd5ATGYrNy6RxR34VfUg=
Received: by 10.36.97.13 with SMTP id u13mr176089nzb;
Wed, 25 May 2005 08:29:47 -0700 (PDT)
Received: by 10.36.105.18 with HTTP; Wed, 25 May 2005 08:29:47 -0700 (PDT)
Message-ID: <[EMAIL PROTECTED]>
Date: Wed, 25 May 2005 15:29:47 +0000
From: hacker <[EMAIL PROTECTED]>
Reply-To: hacker <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: rsync fails to connect on kernel-2.6
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-6
I've successfully used rsync (2.6.4-6) to transfer files over a plip
connection via a cable connecting the parallel ports of my desktop and
laptop, using kernel 2.4.27.
Now, I'm trying to use kernel 2.6.10 (and 2.6.11) and rsync won't
establish a connection.
root #: rsync mydesktop::
rsync: failed to connect to mydesktop: Connection refused (111)
rsync error: error in socket IO (code 10 at clientserver.c(99)
I'm guessing the problem is the ipv6 in 2.6.x. For 2.6.x, ifconfig
shows an inet6 line that isn't there under 2.4.27:
under 2.4.27:
plip0 Link encap:Ethernet HWaddr FC:FC:C0:A8:01:01
inet addr:192.168.1.1 P-t-P:192.168.1.2 Mask:255.255.255.0
UP POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:7 Base address:0x378
with 2.6.x:
plip0 Link encap:Ethernet HWaddr FC:FC:C0:A8:01:01
inet addr:192.168.1.1 P-t-P:192.168.1.2 Mask:255.255.255.0
inet6 addr: fe80::fefc:c0ff:fea8:101/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:1 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:10
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:7 Base address:0x378
In fact, I can't even ping with this. So, I thought I'd try to
disable ipv6 on this link. I added 'del 192.168.1.2' at the end of my
ifconfig to disable ipv6 (per man ifconfig) and now get:
root #: ifconfig
plip0 Link encap:Ethernet HWaddr FC:FC:C0:A8:01:01
inet addr:192.168.1.1 P-t-P:192.168.1.2 Mask:255.255.255.0
inet6 addr: fe80::fefc:c0ff:fea8:101/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:1 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:10
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:7 Base address:0x378
plip0:0 Link encap:Ethernet HWaddr FC:FC:C0:A8:01:01
inet addr:192.168.1.2 P-t-P:192.168.1.2 Mask:255.255.255.0
UP POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
Interrupt:7 Base address:0x378
Apparently, the plip0:0 listing is the subtraction of ipv6. Now I can
successfully ping:
root :~# ping -c1 192.168.1.2
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
64 bytes from 192.168.1.2: icmp_seq=3D1 ttl=3D64 time=3D0.144 ms
--- 192.168.1.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev =3D 0.144/0.144/0.144/0.000 ms
'man rsync' says to add '-4' to the options to get the daemon use
ipv4, and I did this in /etc/defaults/rsync and it works:
root :~# ps aux |grep rsync
root 8349 0.0 0.3 1912 672 ? Ss 11:02 0:00
/usr/bin/rsync --no-detach --daemon --config/etc/rsyncd.conf -4
However, when I try rsync with or without the '-4' option, on my
laptop, it still fails:
root #: rsync -4 mydesktop::
rsync: failed to connect to mydesktop: Connection refused (111)
rsync error: error in socket IO (code 10 at clientserver.c(99)
When I look in my /var/log/rsyncd logfile on the host, there is no
entry for the attempted connection.
I went back to my original ifconfig, and tried rsync with the '-6'
option, but it also failed.
This makes rsync unusable on 2.6.10/11 for me.
---------------------------------------
Received: (at 310739-done) by bugs.debian.org; 15 Sep 2005 09:45:08 +0000
>From [EMAIL PROTECTED] Thu Sep 15 02:45:08 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mx.wurtel.net [195.64.88.114] (mail)
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EFqIm-00084S-00; Thu, 15 Sep 2005 02:45:08 -0700
Received: from wurtel ([192.168.1.1] helo=wurtel.net)
by mx.wurtel.net with esmtp (Exim 3.36 #1 (Debian))
id 1EFqIU-0001Uo-00; Thu, 15 Sep 2005 11:44:50 +0200
Received: from paul by wurtel.net with local (Exim 4.33 #1 (Debian))
id 1EFqIS-0006uU-VM; Thu, 15 Sep 2005 11:44:49 +0200
Date: Thu, 15 Sep 2005 11:44:48 +0200
From: Paul Slootman <[EMAIL PROTECTED]>
To: "hacker (of golf)" <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#310739: rsync fails to connect on kernel-2.6
Message-ID: <[EMAIL PROTECTED]>
Reply-To: [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 *1EFqIU-0001Uo-00*EmVcJZw99xk*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-Level:
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
On Tue 19 Jul 2005, hacker (of golf) wrote:
> This bug is solved. Please withdraw it from your buglist.
>
> It turns out that I was loading the parport_pc module with specific
> irq and address, and the 2.6.x kernels didn't recognize it. So, now I
> just 'modprobe parport_pc' and it works. It had nothing to do with
> rsync!
OK, thanks for the feedback (and sorry for my delay in responding).
Paul Slootman
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
