| Summary: | emerge sync with many files on rsync-2.6.0-r4 server timeouts | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Petteri Räty (RETIRED) <betelgeuse> |
| Component: | [OLD] Unspecified | Assignee: | Gentoo's Team for Core System packages <base-system> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | major | CC: | antispam, flash3001 |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Petteri Räty (RETIRED)
2005-04-23 12:01:41 UTC
i doubt it has anything to do with 2.6.0-r3 to 2.6.0-r4 because the only change between those versions is a config file move Hmm. I just checked and this happens with my desktop too. I normally use nfs for my desktop but now decided to test with my desktop too. This probably has something to do with the server side. I just did rm -fr /usr/portage/* ; emerge sync on the server but it still timeouts. From the desktop:
app-editors/emacs/metadata.xml
158 100% 0.39kB/s 0:00:00 (746, 4.8% of 114532)
io timeout after 180 seconds -- exiting
rsync error: timeout in data send/receive (code 30) at io.c(181)
rsync: connection unexpectedly closed (2698445 bytes received so far) [generator]
rsync error: error in rsync protocol data stream (code 12) at io.c(420)
Hmm. The desktop has rsync-2.6.4 (~x86). It seems more and more to be a server related problem. I had the same problem on laptop with small memory size (96 M). Probably not enough RAM to cache files or something. Rsync appears to be taking too long for default 180 second timeout. Fixed problem on my system by changing /etc/make.conf: RSYNC_TIMEOUT=2000 This seemed to give rsync enough time to do the sync and timeout didn't occur. -d I have 512 MB of memory in the laptop so that is not an issue. I guess the hard drive could be a bit in the slow slide. Same issue here. The cause is simple: - Traversing the whole local portage tree takes much more than just 3 minutes. - Rsync connection remains idle until a new/modified ebuild needs to be transferred. When idle for more than 3 minutes we reach the timeout. This point is especially true if the tree is synced regularly at short intervals (1 day) because there are few changes in the tree. Due to a continuosly incresing size portage tree, this problem could become mainstream and should be addressed. Maybe the built-in 'mytimeout=180' into emerge is just too little and not applicable for a standard installation any more. Actually, I fail to see any real disadvantage in raising this value by default as it is a *client* imposed limit anyway. Besides, if timeouts are avoided, the server suffers less (each reconnection accounts to barely 3.5MB). I really wonder how much increased traffic Gentoo mirrors support just because of this timeout. re-open if 2.6.8 still breaks (In reply to comment #9) > re-open if 2.6.8 still breaks > It still breaks. As I explained in my previous post, 'rsync' is not the issue but 'emerge'. Just increasing the default value of 'mytimeout=180' (/usr/bin/emerge, line 2392) to a saner value like 'mytimeout=1000' will solve this bug. PD: I am not allowed to reopen this bug. To whoever who can, please, do it. |