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

Re: Timeout issues when commiting

From: Alex R. Mosteo <alejandro_at_mosteo.com>
Date: 2005-03-30 10:17:30 CEST

Conner, Shawn wrote:
> That didn't resolve the issue. This is what I have.

What SVN version? What OS? What kind of repository?

I had similar issues with a bdb repository in Mandrake. Moving to fsfs
solved it. The timeouts happened at arbitrary files in each attempt.

Maybe this isn't the same problem, but the above detail will probably
help others to give advice.

>
> <Location /svn/repos/our repository>
> DAV svn
> SVNPath /path to repository
> AuthLDAPURL "LDAP url"
> AuthLDAPBindDN "bind db"
> AuthLDAPBindPassword password
> AuthType Basic
> AuthName "Subversion"
> <LimitExcept MERGE>
> require valid-user
> </LimitExcept>
> </Location>
>
> It literly times out after 5 minutes, which is less then the timeout for
> Apache.
>
> -----Original Message-----
> From: Dominic Anello [mailto:danello@danky.com]
> Sent: Tuesday, March 29, 2005 4:51 PM
> To: Conner, Shawn
> Cc: users@subversion.tigris.org
> Subject: Re: Timeout issues when commiting
>
> On 2005-03-29 16:17:59 -0700, Conner, Shawn wrote:
>
>>Hello,
>>Several times when users are commiting changes, they are recieving one
>
>
>>of the following error message
>>
>>svn: Commit failed (details follow):
>>svn: MERGE request failed on
>>'/svn/repos/abacus/Aba_apps/branches/xnetAFC_031805_18:00.branch/scrip
>>ts
>>'
>>svn: MERGE of
>>'/svn/repos/abacus/Aba_apps/branches/xnetAFC_031805_18:00.branch/scrip
>>ts
>>': timed out waiting for server (http://thabscc01
>><BLOCKED::http://thabscc01> )
>>
>>svn: Commit failed (details follow):
>>
>>svn: MKCOL of
>>'/svn/repos/abacus/Aba_apps/!svn/wrk/f9812586-7af3-0310-8c14-907e7fc56
>>fd
>>e/branches/uk_b2b_031805_19:02.branch/cmds/BAM': 405 Method Not
>>Allowed
>>(http://thabscc01 <http://thabscc01/> )
>
>
> This tends to happen when using mod_authz_svn for path auth and the user
> doesn't have write access to the highest common directory in a commit.
>
> Example:
> Say a user has read-only access to /foo and write access to /foo/bar and
> /foo/baz
>
> If a user tries to file a commit that modifies /foo/bar/a.txt and
> /foo/baz/b.txt, svn ends up doing a MERGE on /foo. Since MERGE is a
> write operation, authz will reject the operation and the commit will
> fail.
>
> The solution I employed was to exclude MERGE requests from validation.
> Note that this opens your server to maliciously crafted MERGE requests.
> Since our server runs on an intranet only, I'm not too worried about it,
> but there is probably a better work around.
>
> Anyway, try putting a <LimitExcept MERGE> around Require valid-user in
> your httpd.conf and see if that helps.
>
> Here's what I use:
> <Location /ec-svn>
> DAV svn
> SVNPath "/usr/local/svn/ec-svn/repo"
> AuthzSVNAccessFile "/usr/local/svn/ec-svn/auth/access.ini"
>
> ## AuthLDAP stuff omitted
>
> <LimitExcept MERGE>
> Require valid-user
> </LimitExcept>
> </Location>
>
> --
> If you've got a vision, then I don't want to see If you've got a notion
> -- don't waste it on me

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 30 10:21:11 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.