FYI: us-msync.centos.org: 208.73.35.50 appears to be unresponsive, at least from my side of the internet.
Adam
Am 21.03.11 13:33, schrieb Adam:
FYI: us-msync.centos.org: 208.73.35.50 appears to be unresponsive, at least from my side of the internet.
We seem to have hardware failure days at centos.org at the moment :/
Removed the machine from the lists, hopefully it will be back soon :)
Cheers and thanks,
Ralph
Ralph Angenendt wrote:
We seem to have hardware failure days at centos.org at the moment :/ Removed the machine from the lists, hopefully it will be back soon :) Cheers and thanks, Ralph
Ralph,
I received this error yesterday:
us-msync.centos.org: 208.73.35.50 - Thu Mar 24 04:05:03 EDT 2011 rsync: failed to connect to 208.73.35.50: Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(107) [receiver=2.6.8]
Looks like maybe it didn't get removed from the list??
Adam
2011/3/24 Adam aring@gmavt.net:
I received this error yesterday:
us-msync.centos.org: 208.73.35.50 - Thu Mar 24 04:05:03 EDT 2011 rsync: failed to connect to 208.73.35.50: Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(107) [receiver=2.6.8]
Sticky fingers. I removed it from ecverywhere it turned up, except us-msync :/
Fixed (though I'd rather have the machine back).
Cheers,
Ralph
-
Adam -
Ralph Angenendt