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

Re: apache locks up db?

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-06-25 19:56:54 CEST

On Fri, 2004-06-25 at 12:43, Robin Becker wrote:

> We then had various problems and found that something was wrong with the source
> of the merge; we couldn't ls its root folder, but subfolders were ok. I have a
> feeling that was the source of the problem. Attempts to fix up that repository
> failed ie svnadmin recover hung. We managed to get svnadmin recover to work by
> restarting apache. Clearly someone had locked something. I assume somehow using
> the commands above we managed to create a loop in the root folder or something.

Sure, you're not supposed to run 'svnadmin recover' unless you have
exclusive access to the repository. That means shutting off apache,
svnserve, and so on.

Really, we'd need to see a transcript of what commit commands caused the
lockup. To begin with, though, I suggest you read this FAQ and the book
section it mentions. The most common cause of database 'lockups' are
permissions problems:


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 25 20:06:42 2004

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.