People are having problems doing a "emerge rsync" due to dns lookups for rsync.gentoo.org. Reproducible: Always Steps to Reproduce: 1. emerge rsync 2. nslookup rsync.gentoo.org 3. Actual Results: >>> starting rsync with rsync://rsync.gentoo.org/gentoo-portage... rsync: getaddrinfo: rsync.gentoo.org 873: No address associated with hostname rsync error: error in socket IO (code 10) at clientserver.c(83) >>> Starting retry 1 of 3 rsync: getaddrinfo: rsync.gentoo.org 873: No address associated with hostname rsync error: error in socket IO (code 10) at clientserver.c(83) >>> Starting retry 2 of 3 rsync: getaddrinfo: rsync.gentoo.org 873: No address associated with hostname rsync error: error in socket IO (code 10) at clientserver.c(83) >>> Starting retry 3 of 3 rsync: getaddrinfo: rsync.gentoo.org 873: No address associated with hostname rsync error: error in socket IO (code 10) at clientserver.c(83) Take a look at the link to the forums and my post with subject "Lookup problems", since many people are having this problem I think it should be fixed by the gentoo.org's dns administrator.
The reasons for this are described here: http://forums.gentoo.org/viewtopic.php?p=236798#236798 It's a limitation of DNS, not any problem with Gentoo or emerge. The solution is to enable TCP/53 on your firewall. We may look at trimming down the rsync round robin as a short term solution, but that is not a fix -- only a quick hack. This is a larger issue that needs to be addressed on the client side, not the server side.
