Re: Each access causes need of db_recover?

"Jon Watte" <hplus@mindcontrol.org> writes:

> However, when browsing using Internet Explorer 5.5 hitting
> the repository directly, I could initially read a few of the
> neon html files, but when I got to chap02.html, I got an XML
> format error. After this error, pretty much every access to
> the neon subdirectory will tell me I need to run db_recover.
>
> Running db_recover will allow me to hit one file, which will
> typically give an XML error on the <hr noshade> line as
> emitted by the Subversion server browse code, and then I need
> to run db_recover again.

[snip]

> Any insights? Ideas for debugging, pointers to FAQs I missed,
> patches to apply and marshmallows are all welcome. I'm not
> (very) afraid of GDB.

One thing that causes db_recover to be required is when something
crashes while holding DB locks. When mod_dav_svn crashes there is
usually a message in the Apache error log (you may not have noticed
the crash if Apache is multi-process). The easiest way to track it
down is to follow the instructions in the HACKING file and run httpd
with the -X flag. Then when Apache crashes the debugger should catch
it and a stack trace should show you the offending line.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org