It seems that rsync mirror 209.177.148.226 is having some issues... An emerge --sync to this mirror has given me problems on two different servers (using two different upstream providers). server ~ # emerge --sync >>> Starting rsync with rsync://209.177.148.226/gentoo-portage... >>> Checking server timestamp ... timed out rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(276) [receiver=2.6.9] >>> Retrying... . . . Reproducible: Always Steps to Reproduce: 1. Try to sync with 208.177.148.226 Actual Results: Timeout Expected Results: Should sync without problems.
CONFIRMED - cockatoo is fubar [02:26:33]<root@rage:~> SYNC="rsync://209.177.148.226/gentoo-portage" emerge --sync >>> Starting rsync with rsync://209.177.148.226/gentoo-portage... >>> Checking server timestamp ... timed out rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(244) [receiver=2.6.9] >>> Retrying... Looks like rsyncd is no longer responding on cockatoo, yet the box and rsync daemon are still up.
Yes, I have been having problems with the cockatoo for a couple days.
I can confirm the rsyncd is still working. rsync -a cockatoo.gentoo.org::gentoo-portage /tmp/ completes without errors on my box.
Just tried again this morning and although it worked *very* slowly, it did work.
James/Burn, Can you guys completely rule out network issues? Have you seen these issue(s) again?
Duh. 209.177.148.226 isn't an official mirror.
Shyam, then why is it in dns? :P seems to be working fine now. I mentioned this bug in #g-mirrors ages ago and I think someone had a look/fixed it. Can't remember who though, might've been kurt
Robert, Since it's not in the official access list, I've removed it from DNS as well. Thanks for helping me locate it.
