Re: Updates and Checouts Failing...

I'm not too worried about a Denial of Service Attack since this server
is behind a firewall and is unreachable via The Tubes.

Of course, if someone really wanted to do a DOS attack on our clients,
they'd let us install our software (RIM SHOT!)... But, seriously
folks!

I've increased the timeout from 120 seconds to 240 seconds (these are
seconds. Right?). I was worried if this was too much, but I can see
from your example that you increased this to 1200 seconds or about 20
minutes.

I've found a bit more information going on. From what I read, this
seems to be a problem with directories that contain lots of files and
with Windows SP3. And, yes, it is happening on our Windows SP3 and in
a directory with lots and lots of files in it. We'll see if this
helps.

Anyone else ran into this issue or has modified their Timeout setting on Apache?

And, what is the official Subversion policy of the Apache "KeepAlive"
setting. By default, this is off. Should I turn it on for a Subversion
server?

On Fri, Mar 27, 2009 at 11:57 AM, <kmradke_at_rockwellcollins.com> wrote:
>
> David Weintraub <qazwart_at_gmail.com> wrote on 03/27/2009 09:12:57 AM:
>> I've recently been getting reports about Subversion commands failing.
>> This happens in Eclipse, Tortoise, and the command line. Everyone
>> whose reported on these problems have been on Windows systems. There
>> is no error in the Apache log, they simply get "Server Reset
>> Connection" errors.
>>
>> Here's the latest one that happened while doing an update in Tortoise::
>>
>> (Window Title: C:\eclipse_workspace\neo_ibfiltering - Update -
>> TortoiseSVN Failed!)
>>
>> [...]
>> Added: C:\eclipse_workspace\neo_ibfiltering\adsales\web\dojo-
>> src\dojox\dtl\demos\json\fruit.json
>> Added: C:\eclipse_workspace\neo_ibfiltering\adsales\web\dojo-
>> src\dojox\dtl\demos\json\blog
>> Error     Report of '/dev/!svn/vcc/default': Could not read response
>> body: connection was
>> Error     closed by server (http://subversion.solbright.com)
>> Finished!
>>
>> This user also reported that they got an "RA layer request failed"
>> while trying to do this via Eclipse.
>>
>> I suspect that there may be an issue with our network or our Apache
>> setup. These are extremely long operations. I wonder if the Apache
>> server is timing out. And, if it is, how can I prevent that from
>> happening.
>
> Yes, I believe you are running into a network timeout.  Subversion
> does a fair amount of disk i/o between network operations to maintain
> the working copy dirs and large files or a slow disk can cause
> the connection to be dropped before the whole transaction is complete.
> (For example, duplicating a 2G file from the .svn folder to the
>  working copy folder during the update may take longer than the
>  default network timeout)
>
> In your apache config, I think you want to adjust the Timeout value:
>
> #
> # Timeout: The number of seconds before receives and sends time out.
> #
> #####Timeout 300
> Timeout 1200
>
>
> Beware of setting this too high, since you can easily make
> it much easier for someone to perform a denial of service
> attack against your apache server...
>
> Kevin R.

-- 
--
David Weintraub
qazwart_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1445583
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].