During the past day we've been unable to rsync to the CentOS master mirror servers. Timeouts are reported:
rsync: failed to connect to us-msync.centos.org: Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(98)
rsync: failed to connect to eu-msync.centos.org: Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(98)
Are these servers really down, or are they overwhelmed with unwarranted rsync traffic ? We run a Tier1 mirror server (mirror.fysik.dtu.dk) and therefore need to rsync relatively quickly.
Is it time that the master mirror servers become restricted to Tier1 (and maybe Tier2) ?
Sorry about the problem ... 4 of our major servers in one location are down.
We have taken them out of DNS and everything should now work, albeit a bit slower. Hopefully we will get our rack back online in a day or so.
Thanks, Johnny Hughes
On Tue, 2007-06-19 at 09:33 +0200, Ole Holm Nielsen wrote:
During the past day we've been unable to rsync to the CentOS master mirror servers. Timeouts are reported:
rsync: failed to connect to us-msync.centos.org: Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(98)
rsync: failed to connect to eu-msync.centos.org: Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(98)
Are these servers really down, or are they overwhelmed with unwarranted rsync traffic ? We run a Tier1 mirror server (mirror.fysik.dtu.dk) and therefore need to rsync relatively quickly.
Is it time that the master mirror servers become restricted to Tier1 (and maybe Tier2) ?
-
Johnny Hughes -
Ole Holm Nielsen