My ISP apparently recently bought a new bank of IP addresses: 64.66.192.0 - 64.66.223.255 Since I recently rebooted my router, my public IP changed from something else, to one of the aforementioned new ones. Since then, emerge --sync stopped working. I have temporarily turned off rsync-verify, but I still get something like this when I try to sync: * Running emerge --sync >>> Syncing repository 'gentoo' into '/usr/portage'... >>> Starting rsync with rsync://176.28.50.119/gentoo-portage... >>> Checking server timestamp ... timed out rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(642) [Receiver=3.1.3] >>> Retrying... >>> Starting retry 1 of 2 with rsync://91.186.30.235/gentoo-portage >>> Checking server timestamp ... timed out rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(642) [Receiver=3.1.3] >>> Retrying... >>> Starting retry 2 of 2 with rsync://89.238.71.6/gentoo-portage >>> Checking server timestamp ... timed out rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(642) [Receiver=3.1.3] >>> Retrying... !!! Exhausted addresses for rsync.gentoo.org If I manually run the command "rsync -av rsync://some.ip.address/gentoo-portage /tmp/blah/", it works. However, there is a noticeable delay of about 20 seconds after the connection is established and rsync is waiting to hear back after sending the first packet (strace shows me it sends "@RSYNCD: 31..0\n") I rebooted my router until I got a different IP from a totally different block (170.199.x.y) and it worked as expected, but after another unlucky IP assignment I'm back to the problematic ones. Could this a problem with portage? rsync? Reproducible: Always
I just found out about PORTAGE_RSYNC_INITIAL_TIMEOUT. If I set it to 30, I can work around my huge timeout, but still don't understand what is causing it in the first place.