Re: [gentoo-user] Confusing persistent sync problem
Wyatt Epp schrieb: Evening, Lately, for at least a few months, actually, I've been completely unable to sync normally. I'll get the following sort of thing three times from three different servers. [...] receiving incremental file list timed out rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(544) [receiver=3.0.5] Retrying... I imagine it must be on my end, but I can't for the life of me figure out what it is. Not at my desk, but I seem to recall the syslog was empty as well. Has anyone run into this or, more importantly, a solution for this? Try to increase the timeout. Add the following line to /etc/make.conf PORTAGE_RSYNC_INITIAL_TIMEOUT=60 signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] Confusing persistent sync problem
On Fri, Apr 24, 2009 at 4:36 AM, Florian Philipp li...@f_philipp.fastmail.net wrote: Try to increase the timeout. Add the following line to /etc/make.conf PORTAGE_RSYNC_INITIAL_TIMEOUT=60 Oh come on, seriously? I'm rolling over here; it never occurred to me that the whacked-out QoS we get in Columbus could be the culprit at all! So yeah, thanks a bunch; I was a touch worried that I'd gotten us banned or something. ;) Cheers, Wyatt
[gentoo-user] Confusing persistent sync problem
Evening, Lately, for at least a few months, actually, I've been completely unable to sync normally. I'll get the following sort of thing three times from three different servers. Starting retry 2 of 3 with rsync://134.68.220.74/gentoo-portage Checking server timestamp ... Welcome to crane.gentoo.org Server Address : 134.68.220.74 Contact Name : mirror-ad...@gentoo.org Hardware : 2 x Intel(R) Xeon(TM) CPU 1700MHz, 2024MB RAM Please note: common gentoo-netiquette says you should not sync more than once a day. Users who abuse the rsync.gentoo.org rotation may be added to a temporary ban list. MOTD autogenerated by update-rsync-motd on Mon Mar 9 08:43:32 UTC 2009 receiving incremental file list timed out rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(544) [receiver=3.0.5] Retrying... I imagine it must be on my end, but I can't for the life of me figure out what it is. Not at my desk, but I seem to recall the syslog was empty as well. Has anyone run into this or, more importantly, a solution for this? Cheers, Wyatt
RE: [gentoo-user] Confusing persistent sync problem
Welcome to crane.gentoo.org Server Address : 134.68.220.74 Contact Name : mirror-ad...@gentoo.org Hardware : 2 x Intel(R) Xeon(TM) CPU 1700MHz, 2024MB RAM Please note: common gentoo-netiquette says you should not sync more than once a day. Users who abuse the rsync.gentoo.org rotation may be added to a temporary ban list. MOTD autogenerated by update-rsync-motd on Mon Mar 9 08:43:32 UTC 2009 receiving incremental file list timed out rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(544) [receiver=3.0.5] Retrying... Have you verified that the connection has been made? If not try; a...@voodoo ~ $ telnet crane.gentoo.org 873 Trying 134.68.220.74... Connected to crane.gentoo.org. Escape character is '^]'. ^]quit telnet quit Connection closed. If you don't get the Trying line, your DNS is broken. If you don't get the Escape character line, then the session hasn't been setup - check your firewall/routing. If you dot get Escape character its an application issues. Maybe try rebuilding rsync.
