[gentoo-user] Re: [solved] emerge --sync timeouts

[Matthew Closson <matt@scrapshells.com>]

On Tue, 3 Jan 2006, Bastiaan Visser wrote:

> Maybe not a direct solution, but does a web-sync work ?
>
> On Tuesday 03 January 2006 00:09, Matthew Closson wrote:
>> Hello,
>>
>> When I have not sync'd in over a month or so and when I ran:
>>
>> emerge --sync
>> It basically shows the motd of the remote rsync server and then times out.
>> I have let it run for a bit and try multiple servers and it just keeps
>> timing out after the motd regardless of which server it goes to... here is
>> some output:
>>
>>
>> --------------------------------------------------------------------------
>> Script started on Mon Jan  2 16:46:45 2006
>> sh-3.00# emerge --sync
>> ^[]2;Started emerge on: Jan 02, 2006 16:46:54\a^[]2; *** emerge  sync\a^[]2; ===
>> sync\a^[]2;>>> starting rsync with rsync://64.127.121.98/gentoo-portage\a>>>
>> starting rsync with rsync://64.127.121.98/gentoo-portage...
>>
>>>>> checking server timestamp ...
>>
>> Welcome to owl.gentoo.org
>>
>> Server Address : 64.127.121.98
>> Contact Name   : mirror-admin@gentoo.org
>> Hardware       : 4 x Intel(R) Xeon(TM) CPU 2.40GHz, 1024MB RAM
>>
>>
>> Please note: common gentoo-netiquette says you should not sync more
>> than once a day.  Users who abuse the rsync.gentoo.org rotation
>> may be added to a temporary ban list.
>>
>>
>> MOTD brought to you by motd-o-matic, version 0.3
>>
>> io timeout after 180 seconds - exiting
>> rsync error: timeout in data send/receive (code 30) at io.c(109)
>>
>>>>> retry ...
>>
>> ^[]2;>>> Starting retry 1 of 3 with rsync://134.68.220.73/gentoo-portage\a
>>
>>>>> Starting retry 1 of 3 with rsync://134.68.220.73/gentoo-portage
>>>>> checking server timestamp ...
>>
>> Welcome to raven.gentoo.org
>>
>> Server Address : 134.68.220.73
>> Contact Name   : mirror-admin@gentoo.org
>> Hardware       : 2 x Intel(R) Xeon(TM) CPU 1700MHz, 2176MB RAM
>>
>>
>> Please note: common gentoo-netiquette says you should not sync more
>> than once a day.  Users who abuse the rsync.gentoo.org rotation
>> may be added to a temporary ban list.
>>
>>
>> MOTD brought to you by motd-o-matic, version 0.3
>>
>> --------------------------------------------------------------------------
>>
>> and thats it.  I reinstalled a recent portage snapshot and also made sure
>> I don't have any config file updates pending with etc-update and a manual
>> search in etc.  The rest of portage/emerge continues to work fine.  I can
>> continue to emerge/install packages without problems, just not --sync.
>> Any ideas are appreciated.  Thanks,
>>
>>  			-Matt-
>>
>> DFI Lanparty UT Ultra-D SLI-mod 6.18-2
>> A64 3000 Venice 300x9 1.50V
>> Kingwin AWC-1 water cooled 30C/42C
>> 2x512 TwinMOS PC3200 BH-5 @ 245 3.4V
>> Rosewill X800XL 459/1100 37C/50C volt modded
>> Some cheap ass hard drives
>> Some non-color matching optical drives
>> Fortron 500w Blue Storm
>> Gentoo Linux x86 OS
>> Fluxbox Window manager
> -- 
> gentoo-user@gentoo.org mailing list
>
>


Actually, I did not try web-sync, I will and let you know, but doing some 
googling I came across the mirrorselect utility and did the following

emerge mirrorselect
mirrorselect -ri

it presents options for your rsync mirror, I choose

rsync.namerica.gentoo.org

which updated my this line in my /etc/make.conf

SYNC="rsync://rsync.gentoo.org/gentoo-portage"

to

SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"

then emerge --sync and it is working

So as far as why it was timing out trying to sync to the main rsync site 
I'm still not sure, but at least its working now.

Thanks,

 			-Matt-
-- 
gentoo-user@gentoo.org mailing list