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.
m christensen <dfs@xmission.com>
11/09/2004 02:24 PM
To:
cc: users@subversion.tigris.org
Subject: Re: SVNADMIN Recover and Verify show good but
repository still hosed??? SO No Ideas? Anybody?
So, no ideas I guess?!?
m christensen wrote:
> Jani Averbach wrote:
>
>> On 2004-11-09 09:57-0700, m christensen wrote:
>>
>>
>>> I get :
>>> PROPFIND request failed on '/svn/esh_docs/safety'
>>> PROPFIND of '/svn/esh_docs/safety': 500 internal server error
>>> (http://mis-dev:81)
>>>
>>>
>>
>>
>> First, stop Apache on your server and all other repository access
>> method, make a copy of repository (as backup, so we won't broke it any
>> more). Then start looking why you get 500 error. Show us relevant
>> apache
>> error logs.
>>
>> Br, Jani
>>
>>
>>
> Backup has been run.
>
> Apache logs follow:
>
> [Tue Nov 09 08:35:25 2004] [error] [client 10.1.0.219] Unable to PUT
> new contents for
>
/svn/esh_docs/!svn/wrk/7403c3b6-e94f-5949-b856-65a443b747a6/safety/safety_suggest_box.cfm.
> [403, #0]
> [Tue Nov 09 08:35:25 2004] [error] [client 10.1.0.219] Could not
> prepare to write the file [500, #160029]
> [Tue Nov 09 08:35:25 2004] [error] [client 10.1.0.219] Berkeley DB
> error while appending string for filesystem
> D:\\SVN/esh_docs/db:\nDB_RUNRECOVERY: Fatal error, run database
> recovery [500, #160029]
> [Tue Nov 09 08:35:25 2004] [error] [client 10.1.0.219] (20014)Error
> string not specified yet: Berkeley DB error while closing 'nodes'
> database for filesystem D:\\SVN/esh_docs/db:\nDB_RUNRECOVERY: Fatal
> error, run database recovery
> [Tue Nov 09 08:35:25 2004] [error] [client 10.1.0.219] (20014)Error
> string not specified yet: Berkeley DB error while opening environment
> for filesystem D:\\SVN/esh_docs/db:\nDB_RUNRECOVERY: Fatal error, run
> database recovery
> [Tue Nov 09 08:35:25 2004] [error] [client 10.1.0.219] Could not fetch
> resource information. [500, #0]
> [Tue Nov 09 08:35:25 2004] [error] [client 10.1.0.219] Could not open
> the requested SVN filesystem [500, #160029]
> [Tue Nov 09 08:35:25 2004] [error] [client 10.1.0.219] Could not open
> the requested SVN filesystem [500, #160029]
> [Tue Nov 09 08:49:01 2004] [error] [client 10.1.0.65] (20014)Error
> string not specified yet: Berkeley DB error while opening environment
> for filesystem D:\\SVN/esh_docs/db:\nDB_RUNRECOVERY: Fatal error, run
> database recovery
> [Tue Nov 09 08:49:01 2004] [error] [client 10.1.0.65] Could not fetch
> resource information. [500, #0]
> [Tue Nov 09 08:49:01 2004] [error] [client 10.1.0.65] Could not open
> the requested SVN filesystem [500, #160029]
> [Tue Nov 09 08:49:01 2004] [error] [client 10.1.0.65] Could not open
> the requested SVN filesystem [500, #160029]
> [Tue Nov 09 08:49:01 2004] [error] [client 10.1.0.65] (20014)Error
> string not specified yet: Berkeley DB error while opening environment
> for filesystem D:\\SVN/esh_docs/db:\nDB_RUNRECOVERY: Fatal error, run
> database recovery
> [Tue Nov 09 08:49:01 2004] [error] [client 10.1.0.65] Could not fetch
> resource information. [500, #0]
> [Tue Nov 09 08:49:01 2004] [error] [client 10.1.0.65] Could not open
> the requested SVN filesystem [500, #160029]
> [Tue Nov 09 08:49:01 2004] [error] [client 10.1.0.65] Could not open
> the requested SVN filesystem [500, #160029]
> [Tue Nov 09 08:50:37 2004] [error] [client 10.1.0.65] (20014)Error
> string not specified yet: Berkeley DB error while opening environment
> for filesystem D:\\SVN/esh_docs/db:\nDB_RUNRECOVERY: Fatal error, run
> database recovery
> [Tue Nov 09 08:50:37 2004] [error] [client 10.1.0.65] Could not fetch
> resource information. [500, #0]
> [Tue Nov 09 08:50:37 2004] [error] [client 10.1.0.65] Could not open
> the requested SVN filesystem [500, #160029]
> [Tue Nov 09 08:50:37 2004] [error] [client 10.1.0.65] Could not open
> the requested SVN filesystem [500, #160029]
> [Tue Nov 09 08:50:37 2004] [error] [client 10.1.0.65] (20014)Error
> string not specified yet: Berkeley DB error while opening environment
> for filesystem D:\\SVN/esh_docs/db:\nDB_RUNRECOVERY: Fatal error, run
> database recovery
> [Tue Nov 09 08:50:37 2004] [error] [client 10.1.0.65] Could not fetch
> resource information. [500, #0]
> [Tue Nov 09 08:50:37 2004] [error] [client 10.1.0.65] Could not open
> the requested SVN filesystem [500, #160029]
> [Tue Nov 09 08:50:37 2004] [error] [client 10.1.0.65] Could not open
> the requested SVN filesystem [500, #160029]
> [Tue Nov 09 09:32:18 2004] [error] [client 10.1.0.77] (20014)Error
> string not specified yet: Berkeley DB error while opening environment
> for filesystem D:\\SVN/esh_docs/db:\nDB_RUNRECOVERY: Fatal error, run
> database recovery
> [Tue Nov 09 09:32:18 2004] [error] [client 10.1.0.77] Could not fetch
> resource information. [500, #0]
> [Tue Nov 09 09:32:19 2004] [error] [client 10.1.0.77] Could not open
> the requested SVN filesystem [500, #160029]
> [Tue Nov 09 09:32:19 2004] [error] [client 10.1.0.77] Could not open
> the requested SVN filesystem [500, #160029]
> [Tue Nov 09 09:33:25 2004] [notice] Parent: Received shutdown signal
> -- Shutting down the server.
>
> I initiated the shutdown shown in the log.
>
> All I see in the logs is the clain the DB is corrupt and need to be
> recovered. Running Recovery says it's just fine.
>
> Marc
>
>
> ---------------------------------------------------------------------
> 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 9 20:53:14 2004