No real revelation as to what happened or why.
A dump and reload ran without any errors and a full rebuild of a local
working copy ran without a hitch.
Marc
> I ran a dump, it appears to have worked, or at least I saw no errors.
> Maybe I'll try to rebuild from that.
>
> Nick_Gianakas@sybari.com wrote:
>
>> I experienced this same problem last week. Upon getting the 500
>> Internal Server Error, I stopped all SVN access (DAV) and ran
>> verify. It reported the last revision (which was correct)--no errors
>> or warnings.
>> However, if I tried svnadmin hotcopy, I got a bunch of errors that
>> the DB (BDB) needed recovery. I ran recover followed by verify and
>> everything came back w/out problems. Re-running hotcopy resulted in
>> the same set of warnings/errors as the first time.
>>
>> Some notes of interest:
>> - While the repo was being backed up (svnadmin hotcopy --cleanlogs ),
>> a user tried accessing it (update). That was the first time this 500
>> error came up. It then snowballed until the repo was completely
>> inaccessible.
>> - My system setup had not changed in weeks.
>> - Setup:
>> - SVN 1.1.0
>> - All repos are of type BDB
>> - Apache 2.0.52 (WebDAV)
>> - x86; Gentoo Linux
>>
>> W/out much help from Google and limited time, I dumped the repo and
>> reloaded it. So far, no problems.
>>
>> Regards,
>> Nick G.
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 9 23:07:13 2004