Adam Ring wrote: > Below are the results of failed rsyncs. I don't record successes so I > don't know how many times it has seceded to this IP between the below > failures, but this is the only machine I have noticed failing so I > wanted to pass it on. > > Adam > > -- Logs -- > Sat Mar 10 16:05:02 EST 2012 > msync-dvd.centos.org: 64.150.179.24 - rsync: failed to connect to > 64.150.179.24: Connection timed out (110) > rsync error: error in socket IO (code 10) at clientserver.c(124) > [receiver=3.0.6] > > Sun Mar 18 08:05:01 EDT 2012 > msync-dvd.centos.org: 64.150.179.24 - rsync: failed to connect to > 64.150.179.24: Connection timed out (110) > rsync error: error in socket IO (code 10) at clientserver.c(124) > [receiver=3.0.6] > > Wed Apr 11 12:05:02 EDT 2012 > msync-dvd.centos.org: 64.150.179.24 - rsync: failed to connect to > 64.150.179.24: Connection timed out (110) > rsync error: error in socket IO (code 10) at clientserver.c(124) > [receiver=3.0.6] > -- Logs -- I hit this server again over the weekend and was unable to establish a connection: Sat Apr 14 04:05:01 EDT 2012 msync-dvd.centos.org: 64.150.179.24 - rsync: failed to connect to 64.150.179.24: Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(124) [receiver=3.0.6] Adam