[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: TSVN connection to repository times-out after server is idle for some period of time (408 errors in Apache logs)

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Wed, 21 Nov 2012 21:11:18 +0100

On 19.11.2012 17:33, Ben Johnson wrote:
> Hi, everyone,
>
> This may be more of an Apache question than a TortoiseSVN question, so
> please let me know if this has nothing to do with TSVN.
>
> If I haven't connected to an SVN repository on the server in question
> for some period of time (e.g., overnight), Apache logs a 408 error the
> first time I try to connect (regardless of whether I'm updating,
> committing, etc.):
>
> XXX.XXX.XXX.XXX - - [05/Nov/2012:06:44:05 -0800] "-" 408 0 "-" "-"
>
> The TSVN error dialog says:
>
> ---------------
> Command Commit
> Error Commit failed (details follow):
> Error Unable to connect to repository at URL
> Error 'https://example.com/svn/project/trunk'
> Error OPTIONS of 'https://example.com/svn/project/trunk': Could not read
> Error status line: connection was closed by server (https://example.com)
> ---------------
>
> If I simply re-try the action, everything works as expected for the
> remainder of the day (presumably because someone is hitting the server
> often enough to prevent the timeout issue from occurring).
>
> Is this issue due to anything that TSVN is doing? Or is this related to
> Apache's mod_reqtimeout module (or similar)?
>
> On the server in question, SVN requests are handled via Apache's
> mod_dav_svn and mod_authz_svn modules.
>
> Thanks for any guidance in this regard,

The error 408 means a timeout. Since you get this on the server only,
there must be something that your server tries to do that causes a timeout.
I don't know your setup, but such errors usually happen if the server
tries to contact another server (dns, auth, proxy, ...). Since this
happens before you can authenticate with TSVN, I assume that your server
tries to contact some auth server (domain controller?) and fails at that.

also the fact that this only happens the first time indicates that the
timeout happens when contacting the DNS - because once an address has
been resolved by the DNS it is cached locally for a while.

But: this is a server problem and you'll get much better help if you ask
on the Subversion users mailing list for help about this problem.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3030025
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-11-21 21:11:30 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.