| 1 |
On Mon, Sep 28, 2009 at 10:37:45AM +0100, Penguin Lover Nevynxxx squawked: |
| 2 |
> I have a server that appears unable to rsync for emerge --sync. |
| 3 |
> |
| 4 |
> When I try I get: |
| 5 |
> |
| 6 |
> >>> Starting rsync with rsync://204.74.99.100/gentoo-portage... |
| 7 |
> >>> Checking server timestamp ... |
| 8 |
> rsync: failed to connect to 204.74.99.100: No route to host (113) |
| 9 |
> rsync error: error in socket IO (code 10) at clientserver.c(124) |
| 10 |
> [receiver=3.0.6] |
| 11 |
> |
| 12 |
> So, i check the IP.... |
| 13 |
|
| 14 |
Is the rsync server you are connecting to actually running an rsync |
| 15 |
daemon? Should be port 873. |
| 16 |
|
| 17 |
Hum, on second thought, host 204.74.99.100 resolves to |
| 18 |
crs.ultradns.net which is a redirection service from UltraDNS. This |
| 19 |
really suggests that the server you are trying to sync to is no-longer |
| 20 |
in the rotation? |
| 21 |
|
| 22 |
W |
| 23 |
-- |
| 24 |
"When I say unbounded, I mean...not bounded." |
| 25 |
~DeathMech, S. Sondhi. P-town PHY 205 |
| 26 |
Sortir en Pantoufles: up 1025 days, 11:17 |
Archives