Hey all,
Got an e-mail this morning from someone who happened to notice that my Centos tree was a bit out of date. Doing some digging it looks like the remote server just isn't answering anymore:
--- BEGIN RSYNC --- Wed Feb 24 13:43:01 UTC 2010
rsync: failed to connect to centosk3.centos.org: Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(124) [receiver=3.0.6]
--- END RSYNC --- Wed Feb 24 13:46:10 UTC 2010
However I'm not explicitly connecting to centosk3 I'm using msync-dvd.centos.org, which in turns seems to resolve as follows:
# nslookup msync-dvd.centos.org Server: 127.0.0.1 Address: 127.0.0.1#53
Non-authoritative answer: Name: msync-dvd.centos.org Address: 67.220.193.10
The issue seems to have started on or around Sat Feb 20 05:43:01 UTC 2010 as that's the first sync recently that started failing to connect.
This may have already been fixed though as literally the rsync that happened in the middle of writing this seems to have changed to z3 instead of k3 and that went through. Just a heads up in that case.
- John 'Warthog9' Hawley
On Wed, Feb 24, 2010 at 3:57 PM, J.H. warthog9@kernel.org wrote:
rsync: failed to connect to centosk3.centos.org: Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(124) [receiver=3.0.6]
That machine seems to be gone. Let me take it out of msync.
Ralph
Hey all,
Got an e-mail this morning from someone who happened to notice that my Centos tree was a bit out of date. Doing some digging it looks like the remote server just isn't answering anymore:
....
The issue seems to have started on or around Sat Feb 20 05:43:01 UTC 2010 as that's the first sync recently that started failing to connect.
Thanks, John. I sync from you, and I was seeing the same lateness. I'll keep syncing according to schedule, and hopefully it will sort itself out.
--Brian
-
Brian Collins -
J.H. -
Ralph Angenendt