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

Re: 500 Internal Server Error: corrupted BDB

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2004-01-27 23:45:32 CET

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.

> 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.

> [mrich@eregion gcc]$ svn commit -m ''
>
> ...................................................................................
> ...........................................svn: RA layer request failed
> svn: Commit failed (details follow):
> svn: PUT of
> /source/gcc/!svn/wrk/33e08c30-ded1-0310-a084-adaa7cf8a9b7/gcc-3.2/src/gas/testsuite/gas/sh/sh64/pt32-noexp-2.d: timed out waiting for server (https://anduril)
>
> [mrich@eregion gcc]$ svn commit -m ''
> Error validating server certificate: Unknown certificate issuer,
> Hostname mismatch. Accept? (y/N): y
> svn: RA layer request failed
> svn: Commit failed (details follow):
> svn: OPTIONS request failed on '/source/gcc'
> svn: OPTIONS of '/source/gcc': 500 Internal Server Error

Again, what happened on the server side? What does the apache errorlog
and accesslog say? It should have more details about the problem.

> This seems to be similar to the problems that most people were having,
> though I couldn't get enough information to reproduce the exact errors
> they were having. Any help would be appreciated.

At this point, the best plan to pursue is: upgrade clients and server
to 0.37 (after doing a db dump/load for the schema change), upgrade to
BDB 4.2, and see if you can reproduce problems. If you do, take extra
care to capture exactly what the client was doing, and show us the
apache logs.

At the moment, your problem descriptions are a bit too vague. We need
more specifics to be of any help to you.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 27 23:46:29 2004

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