server 141.219.155.230 seems to be in the namerica gentoo rotation. It appears to be denying connection requests. Reproducible: Always Steps to Reproduce: 1. SYNC="rsync://141.219.155.230/gentoo-portage" emerge --sync 2. 3. Actual Results: >>> Starting rsync with rsync://141.219.155.230/gentoo-portage... >>> Checking server timestamp ... rsync: failed to connect to 141.219.155.230: Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(124) [receiver=3.0.6] >>> Retrying... Expected Results: successful syncage.
Looks good to me. I'll add it to the test system for one week to be sure. Thanks for the report.
Andrew, This bug is here because of a request that it wasn't serving properly, so I put it in the testing system for one week. The only problem I see is that it is lagging by ~40 minutes. At what intervals are you syncing? Thanks.
We mirror the main archive every hour on the 3 and 33 minute marks. We mirror the distfile archive every four hours.
(In reply to comment #3) > We mirror the main archive every hour on the 3 and 33 minute marks. We mirror > the distfile archive every four hours. > Andrew, thanks for your quick response. At 15:31 UTC, there was a 45 minute lag on your gentoo-portage mirror. At 15:34 UTC, your mirror was in sync again. Can you double check on the XX:03 job/logs? Hopefully we can resolve this.
(In reply to comment #4) > (In reply to comment #3) > > We mirror the main archive every hour on the 3 and 33 minute marks. We mirror > > the distfile archive every four hours. > > > > Andrew, thanks for your quick response. > > At 15:31 UTC, there was a 45 minute lag on your gentoo-portage mirror. > > At 15:34 UTC, your mirror was in sync again. Can you double check on the XX:03 > job/logs? Hopefully we can resolve this. > Alright, Checked at 05:01 and 05:22 and both were in-sync. We will chalk that up to random connection issues for now. Thanks.
Closing bug. Looks fine. Thanks for supporting Gentoo.
