It appears from my side of the internet that "208.90.224.30" hasn't been responding reliably:
us-msync.centos.org: 208.90.224.30 - Fri Apr 15 12:05:06 EDT 2011 rsync: failed to connect to 208.90.224.30: Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(107) [receiver=2.6.8]
us-msync.centos.org: 208.90.224.30 - Mon Apr 18 12:05:04 EDT 2011 rsync: failed to connect to 208.90.224.30: Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(107) [receiver=2.6.8]
Adam
I had problems with syncing also :(
2011/4/18 Adam aring@gmavt.net
It appears from my side of the internet that "208.90.224.30" hasn't been responding reliably:
us-msync.centos.org: 208.90.224.30 - Fri Apr 15 12:05:06 EDT 2011 rsync: failed to connect to 208.90.224.30: Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(107) [receiver=2.6.8]
us-msync.centos.org: 208.90.224.30 - Mon Apr 18 12:05:04 EDT 2011 rsync: failed to connect to 208.90.224.30: Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(107) [receiver=2.6.8]
Adam _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
On Mon, Apr 18, 2011 at 10:19:46PM +0200, Huib Laurens wrote:
I had problems with syncing also :(
removing too
Tru
-
Adam -
Huib Laurens -
Tru Huynh