Gentoo Archives: gentoo-mirrors

From: Georgi Georgiev <chutz@×××.net>
To: gentoo-mirrors@l.g.o
Subject: Re: [gentoo-mirrors] timeout errors
Date: Thu, 24 Nov 2005 07:29:29
Message-Id: 20051124072846.GB7375@ols-dell.iic.hokudai.ac.jp
In Reply to: Re: [gentoo-mirrors] timeout errors by Veiko Kukk
1 maillog: 24/11/2005-09:11:31(+0200): Veiko Kukk types
2 > Tsiteerin Veiko Kukk <veiko@×××××.ee>:
3 >
4 > > Tsiteerin Michael Renner <robe@××××××.at>:
5 > >
6 > > > You've got --timeout 900 in your script and are using a recent rsync
7 > > > version?
8 > >
9 > > Changed --timeout=600 to --timeout=900.
10 >
11 > Problem still exists. Maybe main server is overloaded?
12 >
13 > rsync error: timeout in data send/receive (code 30) at io.c(109)
14 > rsync: connection unexpectedly closed (931718 bytes received so far) [receiver]
15 > rsync error: error in rsync protocol data stream (code 12) at io.c(434)
16 > rsync: connection unexpectedly closed (931718 bytes received so far) [generator]
17 > rsync error: error in rsync protocol data stream (code 12) at io.c(434)
18
19 The problem may occur if *your* server is overloaded or if your hard
20 disk is slow, etc. The session goes more or less like this:
21
22 1. Your rsync client requests a file list (with checksums, timestamps,
23 etc.) from the remote server
24
25 while there are local files to check; do
26 2. start computing the local file list (files, timestamps, checksums)
27 3. request updated files from the remote server when enough files that
28 need updating are found.
29
30 Since there is no communication in step 2, it may happen so that your
31 client times out while checking what you have on your disk. It may
32 easily happen if there isn't much to update and most of the local files
33 have to be processed.
34
35 --
36 / Georgi Georgiev / New York is real. The rest is done with /
37 \ chutz@×××.net \ mirrors. \
38 / http://www.gg3.net/ / /
39 --
40 gentoo-mirrors@g.o mailing list

Replies

Subject Author
Re: [gentoo-mirrors] timeout errors Veiko Kukk <veiko@×××××.ee>