Quoting Steve <[EMAIL PROTECTED]>:
[EMAIL PROTECTED] wrote:
rsync: connection unexpectedly closed (587704 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(359)
I ran into a remarkably similar problem this weekend while doing an "emerge --sync" which was rather annoying.
I tried increasing the rsync timeout (as I'd seen suggested elsewhere) but this had no effect.
I stumbled upon a quick-fix to get my "emerge --sync" to complete... I noticed it got about as far on each attempt before generating that error - so I deleted a chunk of my local tree around where the error was being reported... and on the next attempt everything ran smoothly. To me it seemed that this was an issue of a timeout or something like that when the local and remote files were very similar and access to the local filesystem is relatively slow (My meagre gentoo server also has pitifully little RAM and relies heavily on swap.)
I realise this is merely anecdotal - but at least you know you're not alone.
Well that gives me more ideas, something I can tinker with. I'm trying single changes at a time in the server now, such as right now I set the timeout to 0 (no timeout), and I'll see what happens.
If that doesn't do it, I'll try setting the bandwidth limit lower.
If that doesn't do it, I'll mess with your idea. Hopefully I don't have to do that often, evenaually the thing is meant to be in another state. And we've only got a single T1...
-- gentoo-user@gentoo.org mailing list
