You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by m christensen <df...@xmission.com> on 2004/11/09 16:57:09 UTC
SVNADMIN Recover and Verify show good but repository still hosed???
I'm using version previous stable version of SVN ( I see no option to
make it print out its release info)
I'm using version 1.1.0 of TortoiseSVN
The system is running on windows 2K
The repository is in a BDB database.
I have a respository that has a main tree with about a dozen external
repositories for a buch of subdirectories
managed by different groups.
We had a server crash yesterday and lost a network card and connectivity
to our backup network.
As such I have no access to any backups.
BUT... Subversion claims everything is just fine. (it's not fine though)
D:\SVN>svnadmin recover esh_docs
Please wait; recovering the repository may take some time...
Recovery completed.
The latest repos revision is 78.
D:\SVN>svnadmin verify esh_docs
* Verified revision 0.
* Verified revision 1.
---SNIP---
* Verified revision 77.
* Verified revision 78.
D:\SVN>
The fact is any Update Syncs or Creations fail when they hit this
particular directory.
I get :
PROPFIND request failed on '/svn/esh_docs/safety'
PROPFIND of '/svn/esh_docs/safety': 500 internal server error
(http://mis-dev:81)
They have been running fine for several months and there were no changes
aside from an OS
patch for the latest batch of worms.
Ideas, Please!
This is a critical production system and people are getting nervous.
Marc
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: SVNADMIN Recover and Verify show good but repository still hosed???
Posted by m christensen <df...@xmission.com>.
Nick_Gianakas@sybari.com wrote:
>Glad that helped.
>Out of curiosity, what version of SVN are you running?
>
>
>
As near as I can tell 1.1 Dev 9226.
I need to upgrade as soon as I can get a complete set of matching client
tools and subversion that
sounds solid and the time to do the upgrade.
Marc
>I upgraded to 1.1.1 this morning. Considering how long it took to hit
>that 500 error on 1.1.0, I'm not holding my breath.
>
>Regards,
>Nick G.
>
>
>
>
>
>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
Re: SVNADMIN Recover and Verify show good but repository still hosed???
Posted by Ni...@sybari.com.
Glad that helped.
Out of curiosity, what version of SVN are you running?
I upgraded to 1.1.1 this morning. Considering how long it took to hit
that 500 error on 1.1.0, I'm not holding my breath.
Regards,
Nick G.
m christensen <df...@xmission.com>
11/09/2004 05:06 PM
To:
cc: users@subversion.tigris.org
Subject: Re: SVNADMIN Recover and Verify show good but
repository still hosed???
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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: SVNADMIN Recover and Verify show good but repository still hosed???
Posted by Ni...@sybari.com.
While my SVN repo isn't wedged, and I'm not getting the 500 error, I am
getting errors during a hotcopy again.
I'll post the output of svnadmin hotcopy for reference:
svn: DB_RUNRECOVERY: Fatal error, run database recovery
svn: bdb: Improper file close at 206/373112
svn: bdb: Recovery function for LSN 206 373112 failed on backward pass
svn: bdb: PANIC: Invalid argument
svn: bdb: fatal region error detected; run recovery
svn: bdb: fatal region error detected; run recovery
svn: bdb: fatal region error detected; run recovery
As mentioned in an earlier post, svnadmin verify and svnadmin recover
don't report any problems; but I get these errors during hotcopy (even
after running verify and recover).
Anyone see this before?
Regards,
Nick G
m christensen <df...@xmission.com>
11/09/2004 05:06 PM
To:
cc: users@subversion.tigris.org
Subject: Re: SVNADMIN Recover and Verify show good but
repository still hosed???
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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: SVNADMIN Recover and Verify show good but repository still hosed???
Posted by m christensen <df...@xmission.com>.
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
Re: SVNADMIN Recover and Verify show good but repository still hosed???
Posted by m christensen <df...@xmission.com>.
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
Re: SVNADMIN Recover and Verify show good but repository still hosed??? SO
No Ideas? Anybody?
Posted by Ni...@sybari.com.
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 <df...@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
Re: SVNADMIN Recover and Verify show good but repository still hosed???
SO No Ideas? Anybody?
Posted by m christensen <df...@xmission.com>.
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
Re: SVNADMIN Recover and Verify show good but repository still hosed???
Posted by m christensen <df...@xmission.com>.
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
Re: SVNADMIN Recover and Verify show good but repository still hosed???
Posted by Jani Averbach <ja...@jaa.iki.fi>.
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
--
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: SVNADMIN Recover and Verify show good but repository still hosed???
Posted by Ben Collins-Sussman <su...@collab.net>.
On Nov 9, 2004, at 10:57 AM, m christensen wrote:
>
> PROPFIND request failed on '/svn/esh_docs/safety'
> PROPFIND of '/svn/esh_docs/safety': 500 internal server error
> (http://mis-dev:81)
>
So what's the actual server error? 500 is a generic errorcode returned
to the client. What does the apache error-log say? There should be
several lines in the error-log explaining the true problem.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org