Re: [gentoo-user] Gentoo rsync servers time out
On Wednesday 24 December 2008, Eric Martin wrote: Mick wrote: I have noticed this phenomenon which I am not sure I can explain very satisfactorily. Just after midnight (GMT) any attempt to resync proves futile: == # eix-sync * Running emerge --sync Starting rsync with rsync://88.156.78.16/gentoo-portage... rsync error: received SIGUSR1 (code 19) at main.c(1286) [receiver=3.0.4] snip Starting retry 1 of 3 with rsync://137.226.34.228/gentoo-portage Checking server timestamp ...Welcome to rsync.informatik.rwth-aachen.de (137.226.34.228). snip An hour or so later resync'ing happens without any problem. Why is this? When it works the second time, is it the same server? rsync.gentoo.org and rsync.$CONTINENT.gentoo.org are just cnames pointing to servers so you could be getting different hosts via dns round robin. This is evidenced by the two different ips in your post. I am getting different hosts every time I try of course, but no matter how many times I try immediately after midnight it will always fail in the same manner. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] Gentoo rsync servers time out
I have noticed this phenomenon which I am not sure I can explain very satisfactorily. Just after midnight (GMT) any attempt to resync proves futile: == # eix-sync * Running emerge --sync Starting rsync with rsync://88.156.78.16/gentoo-portage... Checking server timestamp ... contact: f...@vectranet.pl receiving incremental file list timestamp.chk timed out rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(541) [generator=3.0.4] Retrying... rsync error: received SIGUSR1 (code 19) at main.c(1286) [receiver=3.0.4] Starting retry 1 of 3 with rsync://137.226.34.228/gentoo-portage Checking server timestamp ... Welcome to rsync.informatik.rwth-aachen.de (137.226.34.228). This server is part of the SunSITE Central Europe and is located in Aachen, Germany (http://sunsite.informatik.rwth-aachen.de). receiving incremental file list timed out rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(541) [generator=3.0.4] Retrying... [snip...] == An hour or so later resync'ing happens without any problem. Why is this? -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Gentoo rsync servers time out
Mick wrote: I have noticed this phenomenon which I am not sure I can explain very satisfactorily. Just after midnight (GMT) any attempt to resync proves futile: == # eix-sync * Running emerge --sync Starting rsync with rsync://88.156.78.16/gentoo-portage... rsync error: received SIGUSR1 (code 19) at main.c(1286) [receiver=3.0.4] snip Starting retry 1 of 3 with rsync://137.226.34.228/gentoo-portage Checking server timestamp ...Welcome to rsync.informatik.rwth-aachen.de (137.226.34.228). snip An hour or so later resync'ing happens without any problem. Why is this? When it works the second time, is it the same server? rsync.gentoo.org and rsync.$CONTINENT.gentoo.org are just cnames pointing to servers so you could be getting different hosts via dns round robin. This is evidenced by the two different ips in your post. signature.asc Description: OpenPGP digital signature
