Hi there,
After trying out for over 8 hours trying to restore our svn setup I have
to turn to those more experienced svn user. I had done all the reading
I could get on issues of wedged databases etc. thinking that I've
encountered that problem but that's not getting me anywhere.
back to square one
Subversion version 1.2.1
Apache Version 2.0.48
Subversion currently installed on Redhat 9.0 (fileserver machine) while
the Webserver is on a Redhat 8.0 machine.
Oursetup had worked without any flaw until two days ago where "svn co"
was failing with the following error messages
despite that the file was reachable via an http session.
-------------
svn co <repository>
svn: REPORT request failed on '/svn/!svn/vcc/default'
svn: Can't find a temporary directory
--------------
I was guessing that I had exhausted the number of locks perhaps, so
rebooted the file server to no avail.
Everything I read suggested doing recovery so I backed up my reposiotry
and did that. First round of recovery run I did pointed
out to a couple of lock files in the <repository>/db file(locks and
lock-tokens both owned by apache). The output from the recover
command was as follows:
---------------
Repository lock acquired.
Please wait; recovering the repository may take some time...
Recovery completed.
svnadmin: Berkeley DB error for filesystem /space/projects/VOB/vobs1/db
while opening 'locks' table:
Permission denied
----------------
I temporarily renames the locks to see the effect of rerunning the
recovery process once again to get the following log message:
----------------
Repository lock acquired.
Please wait; recovering the repository may take some time...
Recovery completed.
svnadmin: Berkeley DB error for filesystem /volume/projects/VOB/vobs1/db
while opening 'locks' table:
DB_RUNRECOVERY: Fatal error, run database recovery
svnadmin: bdb: /volume/projects/VOB/vobs1/db/log.0000000271: log file
open failed: Permission denied
svnadmin: bdb: PANIC: Permission denied
svnadmin: bdb: DB_ENV->log_put:
/volume/projects/VOB/vobs1/db/log.0000000271: DB_RUNRECOVERY: Fatal
error, run database recovery
svnadmin: bdb: locks: DB_RUNRECOVERY: Fatal error, run database recovery
Abort
------------
I am now left with doing a catastrophic recovery on bdb and before I go
ahead to do that I would like to ask the following:
1. Has anyone encountered similar problem, and if so how did they solve it?
2. There are a number of log. files in the <respository>/db that are of
different userid's: the maintainer of the repository and apache.
I am anticipating conflicts or perimission problems as shown above
to persisit, any clues of getting aroudn this.
Thanks much
/tesh
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 29 23:53:22 2005