Hi, On Fri, 28 Oct 2005, Pascal Bleser wrote:
Eberhard Moenkeberg wrote:
...
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...
Great. And, yes, probably just being lucky this time...
APT repository generation at ftp4 will start soon, propagation to ftp will start at 3:00 MEST (in 90 minutes).
Could you please resync before that ? Just built a few more packages ;)
Done, but no luck again: rsync: read error: Connection reset by peer (104) rsync error: error in rsync protocol data stream (code 12) at io.c(584) ... and the other side is seeing just the same I bet. It seems that rsync has got very unreliable the last time... Some rsyncd admins prefer to set a short timeout value for their daemon, which is very crazy and boring (I can see this way whoever of my uploads is serving SUSE too - they all lack to feed me with their "original contents" just in the SUSE release situations). Restarted again now (with iteration after 3 minutes on abort), but only with hope (with little) for the next APT repository generation after 5 h GMT+2 (in 140 minutes). No chance but let it run, I have to enter my bed now. Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)