On Thu, 13 Jan 2005, Eberhard Moenkeberg <[EMAIL PROTECTED]> wrote: .... > ftp.gwdg.de is running into timeouts of this kind: > > rsync: connection unexpectedly closed (1345637 bytes read so far) > rsync error: error in rsync protocol data stream (code 12) at io.c(342) > > while contacting the masters of almost all important primary sources > which get mirrored using rsync at ftp.gwdg.de. > It happens after building the "remote data base" and the "local database", > just during the start of the real "fetch" actions.
That was quite the essay. :) Yep - this is a known problem. This bug report: https://bugzilla.samba.org/show_bug.cgi?id=1889 requests a "keep-alive" enhancement whereby the receiver would send some kind of null (no-op) packet to the sender on a regular basis to let the sender know that the receiver is still alive and the sender should reset its timeout timer. I run into this problem quite often when trying to sync large archives with sparse updates to a very busy, disk I/O intensive server (exactly the conditions you described). -- John Van Essen Univ of MN Alumnus <[EMAIL PROTECTED]> -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
