| 1 |
Jarry wrote: |
| 2 |
> Hi, I noticed this error when I try to sync my portage tree: |
| 3 |
> |
| 4 |
> --------------- |
| 5 |
> obelix ~ # emerge --sync |
| 6 |
> >>> Starting rsync with rsync://134.68.220.73/gentoo-portage... |
| 7 |
> >>> Checking server timestamp ... |
| 8 |
> timed out |
| 9 |
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at |
| 10 |
> rsync.c(544) [receiver=3.0.6] |
| 11 |
> >>> Retrying... |
| 12 |
> |
| 13 |
> >>> Starting retry 1 of 3 with rsync://134.68.220.74/gentoo-portage |
| 14 |
> >>> Checking server timestamp ... |
| 15 |
> timed out |
| 16 |
> rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at |
| 17 |
> rsync.c(544) [receiver=3.0.6] |
| 18 |
> >>> Retrying... |
| 19 |
> --------------- |
| 20 |
> |
| 21 |
> It started about month ago and it happens quite frequently, I'd say |
| 22 |
> there is ~30% chance I get this message when I try "emerge --sync". |
| 23 |
> What could be the reason for this, and how could I fix it? |
| 24 |
> |
| 25 |
> Jarry |
| 26 |
> |
| 27 |
|
| 28 |
|
| 29 |
It's not rsync it's the servers. Are you using the EU pool? I am, and I |
| 30 |
have that problem frequently. In my opinion, the EU pool is of rather |
| 31 |
poor quality. |
Archives