timeout in data send/receive ???
helices
helices at helices.org
Mon May 15 18:30:30 GMT 2006
Wayne =>
* Wayne Davison <wayned at samba.org> [2006:05:15:09:50:17-0700] scribed:
> On Mon, May 15, 2006 at 08:02:20AM -0500, helices wrote:
> > rsync error: timeout in data send/receive (code 30) at io.c(181)
>
> This means that either the client invocation or the server config file
> has set a timeout option. If the server sets a timeout option, it does
> not communicate this fact to the client, so you must also set a similar
> timeout option on the client's command-line if you want the keep-alive
> code in a modern rsync to function properly.
OK -- we currently setting:
timeout = 600
And, we have NOT set it in the client CLI.
Although, I thought that we also experienced this withOUT timeout set.
> So, things to check: is your timeout value too short?
I do not know. What do you think?
> Try increasing it.
I suppose that setting it in the client CLI is the first step?
> Are you using an rsync with keep-alive support (e.g. 2.6.6 or newer)?
> If not, you might want to upgrade.
We are on Debian sarge 2.6.4-6. Upgrading to 2.6.8-2 , requires
upgrading "libc6 (>= 2.3.5-1) but 2.3.2.ds1-22sarge3 is installed". Is
this worth it?
> Do you have a timeout set in the server's config file? If so, you
> should give a similar --timeout option to the client.
That appears to be the most appropriate first step -- right? Only if
this faults, then the other options?
What do you think?
> ..wayne..
--
Best Regards,
helices
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know. The more I know, the more I know I don't know . . .
--
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.samba.org/archive/rsync/attachments/20060515/276fc2d3/attachment.bin
More information about the rsync
mailing list