On Tue, 2004-01-27 at 14:45, Ben Collins-Sussman wrote:
> On Tue, 2004-01-27 at 16:30, Matthew_Rich@playstation.sony.com wrote:
> > "500 Internal Server Error", which doesn't really tell you
> > much, and a corrupted DB.
>
> You need to look at the apache errorlog to get a better idea of what the
> '500' error means. It often means that apache segfaulted, which is
> almost guaranteed to leave the repository stuck in an inconsistent
> state, in need of recovery.
Well, this is interesting ... but Apache didn't segfault.
[Tue Jan 27 10:16:22 2004] [error] [client ] Could not fetch resource
information. [500, #0]
[Tue Jan 27 10:16:22 2004] [error] [client ] Could not open the SVN
filesystem at /home/svnroot/gcc [500, #160029]
[Tue Jan 27 10:16:22 2004] [error] [client ] (17)File exists: Berkeley
DB error while opening environment for filesystem /home/svnroot/gcc/db:
DB_RUNRECOVERY: Fatal error, run database recovery [500, #160029]
[Tue Jan 27 10:19:47 2004] [error] [client ] Could not fetch resource
information. [500, #0]
[Tue Jan 27 10:19:47 2004] [error] [client ] Could not open the SVN
filesystem at /home/svnroot/gcc [500, #160029]
[Tue Jan 27 10:19:47 2004] [error] [client ] (17)File exists: Berkeley
DB error while opening environment for filesystem /home/svnroot/gcc/db:
DB_RUNRECOVERY: Fatal error, run database recovery [500, #160029]
This is just from my attempt at reproducing these errors with a default
setup. hmm, looks familiar.
> > Related issue:
> > http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgId=251824
> > Is this problem specific to BDB 4.1.25? Anyone else tested it?
>
> There seems to be a vague correlation between BDB 4.1 and repository
> problems. Many people see the problems go away when switching to BDB
> 4.0 or 4.2.
>
> > (svn 0.32.1/Apache
> > 2.0.48/mod_dav_svn/BDB 4.1.25)
>
> This release is 3 months old; have you considered upgrading to 0.37?
> It's our first 1.0 release candidate.
I'll try this again with the latest versions.
Yes, I know, it's probably documented somewhere, but is there any
settings for Subversion to produce more debugging output? Aside from
cranking Apache up to 'debug'.
btw, we aren't using NFS :).
Thanks!
Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 28 00:30:54 2004