Hi, On Fri, 28 Oct 2005, Eberhard Moenkeberg wrote:
On Fri, 28 Oct 2005, Pascal Bleser wrote:
Eberhard Moenkeberg wrote:
On Thu, 27 Oct 2005, Randall R Schulz wrote:
On Thursday 27 October 2005 11:11, Günter Lichtenberg wrote:
Pascal, please have a look. I get "connection refused".
I'm only checking my connection state at the times around when you usually grabbed my RPMs, but lately I've seen attempts in the middle of the day, at 23:00, etc.. so.. can happen ;) (it's up now, so.. ;))
But last night's sync was 2005/10/26 21:50:23 [27202] rsync: read error: Connection reset by peer (104) 2005/10/26 21:50:23 [27202] rsync error: error in rsync protocol data stream (code 12) at io.c(515)
It was hanging at my side (not terminating - --timeout was set!).
again... so it seems that downgrading rsync doesn't help at all.
Same opinion here. I have reverted to the new version now and done the YOU to SUSE-10.0 version rsync-2.6.6-2.2, but the 10.0 update was only regarding ACL support, so no new hope, I guess.
It got better the last few days, but last night failed badly.. :(
It only was better because I had iterated after each timeout error...
There is a bug in rsync regarding timeouts. Not only in 2.6.6, but already in 2.6.3. This for sure. I see it with most of the "assumed currently under high load" upstream servers, even if my side is almost idle.
Pascal, the rsync is running, and ftp4 has a load of 0.9 currently...
Done with rc=0. At least an unawaited success, but probably nothing more... APT repository generation at ftp4 will start soon, propagation to ftp will start at 3:00 MEST (in 90 minutes). Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)