| 1 |
I did drop firewall many times, but no effect. |
| 2 |
|
| 3 |
Here is another output: |
| 4 |
|
| 5 |
>>> starting rsync with rsync://140.105.134.102/gentoo-portage... |
| 6 |
>>> checking server timestamp ... |
| 7 |
rsync: failed to connect to 140.105.134.102: Connection timed out |
| 8 |
rsync error: error in socket IO (code 10) at clientserver.c(88) |
| 9 |
>>> retry ... |
| 10 |
|
| 11 |
>>> Starting retry 1 of 3 with rsync://137.226.34.228/gentoo-portage |
| 12 |
>>> checking server timestamp ... |
| 13 |
|
| 14 |
|
| 15 |
As you can see, `emerge sync` tries different rsync servers (they should |
| 16 |
be up and running). |
| 17 |
|
| 18 |
`emerge sync` hangs for awhile when "checking server timestamp ..." |
| 19 |
|
| 20 |
Kurt Lieber wrote: |
| 21 |
> On Tue, Apr 04, 2006 at 03:23:01PM +0200 or thereabouts, Mari?n Hercek wrote: |
| 22 |
>> The computer is posing as firewall. |
| 23 |
>> OUTPUT firewall policy is set to ACCEPT (even FORWARD policy has |
| 24 |
>> 873/tcp, 873/udp enabled). |
| 25 |
> |
| 26 |
> Drop the firewall temporarily. Does 'emerge sync' now work? If so, go fix |
| 27 |
> your firewall scripts. |
| 28 |
> |
| 29 |
> --kurt |
Archives