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

SVNServe not responding anymore

From: Chausse, Claude <claude.chausse_at_positron.qc.ca>
Date: 2005-06-21 02:42:24 CEST


I used to run svnserve on a server for while without any problem (More than 1 year). I just upgraded my server and clients (Comand line and TortoiseSVN) to 1.2 .

At the beginning we coult not connect to the repository and after some search in the forums you discovered that we to do some special DataBase procedure.

Here is the procedure we applied:

* Make sure no process is accessing the repository (stop Apache, svnserve, restrict access via file://, svnlook, svnadmin, etc.)
* Using an older svnadmin binary (that is, linked to an older BerkeleyDB):

1. Recover the repository: 'svnadmin recover /path/to/repository'
2. Make a backup of the repository.
3. Delete all unused log files. You can see them by running 'svnadmin list-unused-dblogs /path/to/repeository'
4. Delete the shared-memory files. These are files in the repository's db/ directory, of the form __db.00*

Once the procedure was applied, it started to work well for a while from 1.2 Clients. Note: Not all client were updated to 1.1. Now, for no apparent reason, I am in a state where I cannot connect to the repository anymore from TortoiseSVN or from the command line. Clients will just freeze waiting for something (In TortoiseSVN I got the message: Please Wait while the repository browser is initialized ...)

By the way, it seems to be related to the repository. It does not happens with another repository.

Anything I can do as a workaround ? Any recovery procedure I should do on the repository to put it back on track ?

By the way, I tried to restart svnserve and it did not do anything. I even tried to restart the computer with no effect neither.

Thanks for your help

Received on Tue Jun 21 10:11:51 2005

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