Re: [SLE] subversion server on 9.3?
On Friday 10 June 2005 21:25, Cristian Rodriguez wrote:
2005/6/10, Steven T. Hatton
: I just upgraded the server that was serving out subversion over http, and now apache2 doesn't seem to know my configuration exists. I also don't see any indication that SuSEconfig knows about apache2. That is, when I run SuSEconfig --module apache2 as described in /usr/share/doc/packages/subversion/README.SuSE
hi. add a new install localtion (use a mirror) and then find subversion-server (apache modules and stuff for subversion is not totally included on the cd's)
bye
Thanks. That helped. Now it's not completely missing. Now it's only broken. There seems to be a version conflict with the Berkeley DB. /var/log/apache2/error_log says: "(20014)Error string not specified yet: Berkeley DB error while opening environment for filesyste :\nDB_VERSION_MISMATCH: Database environment version mismatch" I'm not sure if I should just start over, or try to fix it. I don't (didn't) have that much in the SVN DB. I just set it up last week. -- Regards, Steven
On Saturday 11 June 2005 02:02, Steven T. Hatton wrote:
On Friday 10 June 2005 21:25, Cristian Rodriguez wrote:
2005/6/10, Steven T. Hatton
: I just upgraded the server that was serving out subversion over http, and now apache2 doesn't seem to know my configuration exists. I also don't see any indication that SuSEconfig knows about apache2. That is, when I run SuSEconfig --module apache2 as described in /usr/share/doc/packages/subversion/README.SuSE
hi. add a new install localtion (use a mirror) and then find subversion-server (apache modules and stuff for subversion is not totally included on the cd's)
bye
Thanks. That helped. Now it's not completely missing. Now it's only broken. There seems to be a version conflict with the Berkeley DB. /var/log/apache2/error_log says:
"(20014)Error string not specified yet: Berkeley DB error while opening environment for filesyste
:\nDB_VERSION_MISMATCH: Database environment version mismatch"
I'm not sure if I should just start over, or try to fix it. I don't (didn't) have that much in the SVN DB. I just set it up last week. -- Regards, Steven
It looks as though I've got it fixed. I tried to run svnadmin recover /path/to/repos/name, and it gave me errors saying it couldn't find a log file named log.0000000004, when the latest version was log.0000000003. I ran svnadmin verify on it, and got * Verified revision 0. * Verified revision 1. * Verified revision 2. * Verified revision 3. ... Then I ran recover again, and it succeeded. I still couldn't access the repository, but the apache2 error log had an error saying it couldn't access the database because it didn't have permission. I looked, and sure enough, the files were owned by root. I did a chown -R wwwrun:www repos/name/{dav,db,locks} and it works. -- Regards, Steven
participants (1)
-
Steven T. Hatton