Bug 13885 – emerge rsync failing to connect to rsync.gentoo.org

• Product: Portage Development
• Status: RESOLVED DUPLICATE

[Description Rob 2003-01-13 19:18:21 UTC]

After typing emerge rsync, I get the following:

---------------------------------------------
>>> starting rsync with rsync://rsync.gentoo.org/gentoo-portage...
rsync: failed to connect to rsync.gentoo.org: Connection refused
rsync error: error in socket IO (code 10) at clientserver.c(97)

>>> Updating Portage cache...

----------------------------------------------
It only cranks away for 10 seconds or so on Updating Portage cache and then
returns to the command prompt.  I'm only running a 233, so I know it shouldn't
be going through it THAT fast...  Anyway, attached is the emerge info.

As of right now I can't rsync, so I can't really update anything.

Thanks for any help you can provide.



Portage 2.0.45 (default-x86-1.4, gcc-3.2, glibc-2.2.5-r7)
=================================================================
System uname: 2.4.19-crypto-r7 i686 Pentium II (Klamath)
USE="x86 oss 3dnow apm arts avi crypt cups encode gif gpm gtk imlib java jpeg kd
e gnome libg++ libwww mikmod mmx motif mpeg ncurses nls oggvorbis opengl pdflib
png qt qtmt quicktime sdl spell svga truetype X xml2 xmms xv zlib gdbm berkdb sl
ang readline tcpd pam ssl perl python"
ARCH="x86"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-O2 -mcpu=i686 -pipe"
CXXFLAGS=""
ACCEPT_KEYWORDS="x86"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/confi
g /usr/kde/3/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
MAKEOPTS="-j2"
JDK_HOME=""
JAVA_HOME=""
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
GENTOO_MIRRORS="http://www.ibiblio.org/pub/Linux/distributions/gentoo"

[Comment 1 SpanKY 2003-01-13 19:36:15 UTC]

update your portage, it'll handle this better 

*** This bug has been marked as a duplicate of 12925 ***

[Comment 2 Rob 2003-01-15 07:04:41 UTC]

It ended up not being a duplicate of 12925.  The problem was related to
shorewall blocking the protocol that rsync uses.  Once I allowed the protocol to
come through fine, I could rsync without any problems.