wwong at math
Sep 28, 2009, 5:33 AM
Post #2 of 3
On Mon, Sep 28, 2009 at 10:37:45AM +0100, Penguin Lover Nevynxxx squawked:
Re: Rsync Failing with no route to host, when there is...
[In reply to]
> I have a server that appears unable to rsync for emerge --sync.
> When I try I get:
> >>> Starting rsync with rsync://188.8.131.52/gentoo-portage...
> >>> Checking server timestamp ...
> rsync: failed to connect to 184.108.40.206: No route to host (113)
> rsync error: error in socket IO (code 10) at clientserver.c(124)
> So, i check the IP....
Is the rsync server you are connecting to actually running an rsync
daemon? Should be port 873.
Hum, on second thought, host 220.127.116.11 resolves to
crs.ultradns.net which is a redirection service from UltraDNS. This
really suggests that the server you are trying to sync to is no-longer
in the rotation?
"When I say unbounded, I mean...not bounded."
~DeathMech, S. Sondhi. P-town PHY 205
Sortir en Pantoufles: up 1025 days, 11:17