Based on report on bug 247881, rsync1.nz.gentoo.org doesn't seem to be accepting rsync requests any more. Reproducible: Always
Milos, please open a new bug for server issues the next time (it's really easy to miss comments on closed bugs). Kat, could you check what going on here?
Working on it - sorry for the delay. Several machines at gamers.net.nz have recently been consolidated into one box and the rsync server was one of those affected. I no longer have access to fix it myself since the login credentials have changed, and am busy chasing up access to the box. I'll post a followup tomorrow.
Alright! Good news, I noticed http://linux.gamers.net.nz/ or http://rsync1.nz.gentoo.org/ is up again, but the rsync server on the same machine (60.234.76.202) is still not up as I am receiving Connection Refused (111) meaning that either rsync port is closed or the service is not running: server2 ~ # eix-sync * Running emerge --sync >>> Starting rsync with rsync://60.234.76.202/gentoo-portage... >>> Checking server timestamp ... rsync: failed to connect to 60.234.76.202: Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(124) [receiver=3.0.5] So we are indeed getting somewhere - thanks for slowly getting this machine back on track; syncing with awesome speeds again would be great :)
Man, what a nightmare! I think we are finally sorted with this now. There was more than one issue preventing rsync clients connecting to the new box, but all are hopefully now resolved. Milos, can you please check and confirm?
FANTASTIC! I've switched from the "temporary" (was longer than expected =D): --> SYNC="rsync://rsync.gentoo.org/gentoo-portage" to: --> SYNC="rsync://linux.gamers.net.nz/gentoo-portage" (or rsync1.nz.gentoo.org) and then ran `emerge --sync`; it completed in 5 seconds! :D This is superb - thank you so much Kat and the Orcon Team for helping resolve this elongated problem! I'm sure many others will also be grateful when they find out.
I know this bug is old and neglected. But now, it is invalid due to bug 276682
