Gentoo Archives: gentoo-user

From: Bastiaan Visser <Bastiaan@××××××××××××.nl>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] emerge --sync timeouts
Date: Mon, 02 Jan 2006 22:40:56
Message-Id: 200601030306.45711.Bastiaan@cj-multisoft.nl
In Reply to: [gentoo-user] emerge --sync timeouts by Matthew Closson
1 Maybe not a direct solution, but does a web-sync work ?
2
3 On Tuesday 03 January 2006 00:09, Matthew Closson wrote:
4 > Hello,
5 >
6 > When I have not sync'd in over a month or so and when I ran:
7 >
8 > emerge --sync
9 > It basically shows the motd of the remote rsync server and then times out.
10 > I have let it run for a bit and try multiple servers and it just keeps
11 > timing out after the motd regardless of which server it goes to... here is
12 > some output:
13 >
14 >
15 > --------------------------------------------------------------------------
16 > Script started on Mon Jan 2 16:46:45 2006
17 > sh-3.00# emerge --sync
18 > ]2;Started emerge on: Jan 02, 2006 16:46:54]2; *** emerge sync]2; ===
19 > sync]2;>>> starting rsync with rsync://64.127.121.98/gentoo-portage>>>
20 > starting rsync with rsync://64.127.121.98/gentoo-portage...
21 >
22 > >>> checking server timestamp ...
23 >
24 > Welcome to owl.gentoo.org
25 >
26 > Server Address : 64.127.121.98
27 > Contact Name : mirror-admin@g.o
28 > Hardware : 4 x Intel(R) Xeon(TM) CPU 2.40GHz, 1024MB RAM
29 >
30 >
31 > Please note: common gentoo-netiquette says you should not sync more
32 > than once a day. Users who abuse the rsync.gentoo.org rotation
33 > may be added to a temporary ban list.
34 >
35 >
36 > MOTD brought to you by motd-o-matic, version 0.3
37 >
38 > io timeout after 180 seconds - exiting
39 > rsync error: timeout in data send/receive (code 30) at io.c(109)
40 >
41 > >>> retry ...
42 >
43 > ]2;>>> Starting retry 1 of 3 with rsync://134.68.220.73/gentoo-portage
44 >
45 > >>> Starting retry 1 of 3 with rsync://134.68.220.73/gentoo-portage
46 > >>> checking server timestamp ...
47 >
48 > Welcome to raven.gentoo.org
49 >
50 > Server Address : 134.68.220.73
51 > Contact Name : mirror-admin@g.o
52 > Hardware : 2 x Intel(R) Xeon(TM) CPU 1700MHz, 2176MB RAM
53 >
54 >
55 > Please note: common gentoo-netiquette says you should not sync more
56 > than once a day. Users who abuse the rsync.gentoo.org rotation
57 > may be added to a temporary ban list.
58 >
59 >
60 > MOTD brought to you by motd-o-matic, version 0.3
61 >
62 > --------------------------------------------------------------------------
63 >
64 > and thats it. I reinstalled a recent portage snapshot and also made sure
65 > I don't have any config file updates pending with etc-update and a manual
66 > search in etc. The rest of portage/emerge continues to work fine. I can
67 > continue to emerge/install packages without problems, just not --sync.
68 > Any ideas are appreciated. Thanks,
69 >
70 > -Matt-
71 >
72 > DFI Lanparty UT Ultra-D SLI-mod 6.18-2
73 > A64 3000 Venice 300x9 1.50V
74 > Kingwin AWC-1 water cooled 30C/42C
75 > 2x512 TwinMOS PC3200 BH-5 @ 245 3.4V
76 > Rosewill X800XL 459/1100 37C/50C volt modded
77 > Some cheap ass hard drives
78 > Some non-color matching optical drives
79 > Fortron 500w Blue Storm
80 > Gentoo Linux x86 OS
81 > Fluxbox Window manager
82 --
83 gentoo-user@g.o mailing list

Replies

Subject Author
[gentoo-user] Re: [solved] emerge --sync timeouts Matthew Closson <matt@×××××××××××.com>