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

svn and trac conflict

From: <subversion_at_jujutsu.org.uk>
Date: 2004-06-18 17:26:33 CEST

I've recently created a subversion repository and access has been
working fine using svnserve and svn: descriptors. I then installed
trac <URL:http://www.edgewall.com/products/trac/> and set up a
matching issue tracking database.

All was well - svn running smoothly, trac showing timelines, source
code etc until we committed a lot (574) changed files in one

The svn client continued to behave, until Trac was next used to
access the subversion repository: viewing a changeset. An exception
was thrown reporting "DB_RUNRECOVERY. Fatal error run database
recovery". From here on svn was unable to connect to the database.

svnadmin recover fixed the problem, allowing svn clients to connect
but any further attempts to use Trac to view source or changesets
reproduces the error.

Other subversion/trac repositories on the same system are unaffected.

I have read, and implemented, the umask setting described in
"Supporting Multiple Repository Access Methods". svnserve and
trac.cgi are both wrapped with scripts which set umask 0002.

svnserve and apache run as different users with a common group
project/db/_* files have been chmoded g+w

Does any one have any suggestions as to how I can either pin down, or
preferably, fix, the problem?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 18 17:27:56 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.