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

Handbook on server hangs

From: Jim Blandy <jimb_at_red-bean.com>
Date: 2002-07-30 00:01:35 CEST

This patch puts the information the user needs in the order they'll
need it. It also mentions that they should shut down the server while
they run db_recover.

Okay to commit?

Index: ./repos_admin.texi
--- ./repos_admin.texi
+++ ./.svn/tmp/repos_admin.texi.49872.00001.tmp Mon Jul 29 16:43:51 2002
@@ -341,10 +341,18 @@
 DB environment in a `locked' state. Any further attempts to read or
 write to the repository just sit there, waiting on the lock.
-To `unwedge' the repository, use @command{db_recover}:
+To `unwedge' the repository:
+Shut down the Subversion server, to make sure nobody is accessing the
+repository's Berkeley DB files.
+Switch to the user who owns and manages the database.
+Run the command @command{db_recover -ve -h @var{repos}/db}, where
+@var{repos} is the repository's directory name. You should see
+output like this:
-$ db_recover -ve -h repos/db
 db_recover: Finding last valid log LSN: file: 40 offset 4080873
 db_recover: Checkpoint at: [40][4080333]
 db_recover: Checkpoint LSN: [40][4080333]
@@ -355,12 +363,19 @@
 db_recover: Recovery complete at Sun Jul 14 07:15:42 2002
 db_recover: Maximum transaction id 80000000 Recovery checkpoint [40][4080333]
 @end example
+Make sure that the @command{db_recover} program you invoke is the one
+distributed with the same version of Berkeley DB you're using in your
+Subversion server.
+Restart the Subversion server.
+@end enumerate
 Make sure you run this command as the user that owns and manages the
-database and @emph{not} as root. Running @command{db_recover} as root
-will leave root owned files in the db directory which cannot be opened
-by the non-root user that manages the database, which is typically
-your Apache process.
+database --- typically your Apache process --- and @emph{not} as root.
+Running @command{db_recover} as root leaves files owned by root in the
+@file{db} directory, which the non-root user that manages the database
+cannot open. If you do this, you'll get ``permission denied'' error
+messages when you try to access the repository.
 Second, a repository administrator may need to manage the growth of
 logfiles. At any given time, the DB environment is using at least one

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 30 00:02:05 2002

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

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