>>> Starting rsync with rsync://63.150.226.21/gentoo-portage... >>> Checking server timestamp ... rsync: failed to connect to 63.150.226.21: Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(107) [receiver=2.6.8] It's been down for about a day now.
Hi Steven, Could you please take a look at this and fix it ASAP? Thanks!
This mirror still appears to be down: >>> Starting rsync with rsync://63.150.226.21/gentoo-portage... >>> Checking server timestamp ... rsync: failed to connect to 63.150.226.21: Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(107) [receiver=2.6.8] >>> Retrying...
I am shocked that this still hasn't been corrected: >>> Starting rsync with rsync://63.150.226.21/gentoo-portage... >>> Checking server timestamp ... rsync: failed to connect to 63.150.226.21: Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(107) [receiver=2.6.8] >>> Retrying...
(In reply to comment #3) > I am shocked that this still hasn't been corrected: Relax. Everyone has something called real life to attend to. We give our admins ample time to respond. Since that has not happened so far in this case, I'm removing rsync11.us.gentoo.org from our rotation with immediate effect. Steven, thank you for supporting Gentoo and if you would like to continue to do so in the future, please feel free to re-open this bug.
This same server still appears to be in the rotation for rsync.namerica.gentoo.org, and it's still down.
Apologies. This was one of the few mirrors listed on rsync.namerica.gentoo.org as well. I've removed it now. Thanks!