for some weeks now, each time my DNS resolves rsync.europe.gentoo.org into 126.96.36.199, emerge --sync hangs until a connection timeout occur (after that, another server is successfully used).
>>> starting rsync with rsync://188.8.131.52/gentoo-portage...
>>> checking server timestamp ...
rsync: failed to connect to 184.108.40.206: Connection timed out
rsync error: error in socket IO (code 10) at clientserver.c(88)
>>> retry ...
does the same thing for me.
220.127.116.11 = mirror002.isp.belgacom.be
rsync2.be.gentoo.org = 18.104.22.168
Looks like this is rsync2.be. Removing from europe and be rotations.
The good name of this belgian mirror is rsync.gentoo.skynet.be.
IP is 22.214.171.124.
---------- Forwarded message ----------
From: Cedric Gavage <email@example.com>
Date: Fri, 18 Feb 2005 07:13:17 +0100
Subject: Re: rsync2.be down
Peter Penkala wrote:
> Sorry for the delay, lost the email in my inbox.
> Looks like the IP was entered with a typo 126.96.36.199 instead of .4.
> I've updated rsync2.be to point to the correct IP.
> Just did a quick check, and it seems that the mirror hasn't sync'd in a month:
For this, we are sync'd... (every 30 minutes).
For this, we have now a permission denied.
@ERROR: access denied to gentoo-portage from mirror002.isp.belgacom.be
Looks like your mirror is in the ACL, so syncing should be fine to rsync1.us.gentoo.org.
Turns out the ACL IP was also incorrect. 188.8.131.52 instead of .4. Updated.
(In reply to comment #6)
> Turns out the ACL IP was also incorrect. 184.108.40.206 instead of .4. Updated.
Still impossible for us to sync on rsync1.us.gentoo.org for portage since months:
@ERROR: access denied to gentoo-portage from mirror002.isp.belgacom.be (220.127.116.11)
you should be good to go on the acl update. it will update and give you access
at the top of the hour.