prh@wstn ~ $ emerge --sync >>> starting rsync with rsync://195.86.128.57/gentoo-portage... >>> checking server timestamp ... rsync: failed to connect to 195.86.128.57: Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(99) >>> retry ... This happens every time I get this server, and it has been happening for several weeks at least. prh@wstn ~ $ nslookup 195.86.128.57 Server: 213.208.106.212 Address: 213.208.106.212#53 Non-authoritative answer: 57.128.86.195.in-addr.arpa name = ftp.easynet.nl. Authoritative answers can be found from: 128.86.195.in-addr.arpa nameserver = ns.wirehub.net. 128.86.195.in-addr.arpa nameserver = ns2.wirehub.net. ns.wirehub.net internet address = 194.165.94.1 ns2.wirehub.net internet address = 194.165.94.5 My Internet connection is through nildram.co.uk, and I don't know of any reason for my IP to be blocked by this one rsync server - though I haven't checked this out yet. Reproducible: Always Steps to Reproduce: 1. 2. 3. prh@wstn ~ $ emerge info Portage 2.0.51.22-r1 (default-linux/amd64/2005.0, gcc-3.4.4, glibc-2.3.5-r0, 2.6.11-gentoo-r9 x86_64) ================================================================= System uname: 2.6.11-gentoo-r9 x86_64 AMD Opteron(tm) Processor 246 Gentoo Base System version 1.6.12 ccache version 2.4 [enabled] dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.8 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.16-r1 sys-devel/libtool: 1.5.18 virtual/os-headers: 2.6.11-r1 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-Os -march=opteron -mtune=opteron" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/X11/xdm/Xservers /etc/fonts /etc/gconf /etc/rc.d /etc/rsync /etc/terminfo /etc/texmf/web2c /etc/wget /etc/env.d" CXXFLAGS="-Os -march=opteron -mtune=opteron" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks sandbox sfperms strict userpriv usersandbox" GENTOO_MIRRORS="http://gentoo.blueyonder.co.uk http://ftp.easynet.nl/mirror/gentoo http://trumpetti.atm.tut.fi/gentoo/ ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo http://ftp.uni-erlangen.de/pub/mirrors/gentoo http://distfiles.gentoo.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" LANG="en_GB.utf8" LC_ALL="en_GB.utf8" LINGUAS="en_GB" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="amd64 X acpi alsa arts bash-completion berkdb bitmap-fonts cdr crypt cups curl dvd esd fam font-server foomaticdb fortran gd gif gimpprint gpm gtk imagemagick imlib ipv6 java jp2 jpeg junit kdeenablefinal libwww lzw lzw-tiff mad motif mp3 ncurses nls nptl nptlonly opengl oss pam perl png ppds python qt readline sdl ssl tcpd tetex tiff truetype truetype-fonts type1-fonts unicode usb userlocales xine xml2 xpm xrandr xv zlib linguas_en_GB userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LDFLAGS
*** Bug 95498 has been marked as a duplicate of this bug. ***
i have removed this machine from the europe rotation, along with the .nl.g.o rotation, and will be contacting the admin shortly. -jeffrey
Thanks. Incidentally, this fault has been present for several weeks at least.
Here's another one. This one is now causing connection-unexpectedly-closed errors immediately on connecting: rsync://62.197.40.130/gentoo-portage Incidentally, the behaviour of sync.europe.gentoo.org seems to have changed in recent months. It now returns the same target address repeatedly, up to half-a-dozen times in a row. Is this intended? It wastes time in the case of a misbehaving mirror, as in this case.
connection-expectedly-closed errors are due to the rsync protocol mismatches between client and server. we (gentoo) has seen promising results from using at least rsync version 2.6.5
This box has rsync versions 2.6.0-r3, 2.6.5 and 2.6.6 installed. I don't know which version emerge will pick up.
Peter, a quick 'rsync -v' will show you what version you are running
Right: $ rsync -v rsync version 2.6.0 protocol version 27 [...] Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, IPv6, 64-bit system inums, 64-bit internal inums [...] $ qpkg -v -I rsync net-misc/rsync-2.6.0-r3 * net-misc/rsync-2.6.0-r5 * net-misc/rsync-2.6.0-r6 * When I ran that qpkg command yesterday it gave different results. I hope I was running it on the right box! I have emerged --sync since then though.
Sorry, that was wrong. Please ignore my last comment and substitute this one: $ rsync -v rsync version 2.6.6 protocol version 29 $ qpkg -v -I rsync net-misc/rsync-2.6.0-r3 * net-misc/rsync-2.6.5 * net-misc/rsync-2.6.6 * net-libs/librsync-0.9.7 *
robert, i would try uninstalling all the older versions of rsync so you are only left with 2.6.5.
no response on this bug. closing.