You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Filip Miletic <fi...@gmail.com> on 2006/03/18 17:49:01 UTC
Very frequent transaction failure
Greetings. I run a svn server (svnserve) version 1.3.2 that, out of a
sudden began consistently making the following error.
If I don't commit for some time, say a day or two, and then revert with
a commit, the following message appears.
svn: Commit failed (details follow):
svn: Connection closed unexpectedly
Retrying the commit then gives:
svn: Commit failed (details follow):
svn: Berkeley DB error for filesystem /usr/local/src/svnroot/db while
opening environment:
DB_RUNRECOVERY: Fatal error, run database recovery
svn: bdb: PANIC: fatal region error detected; run recovery
Any further commits fail in the same way until I run 'svnadmin recover'
on the repository. After yet another 'svn update' I am able to commit
for some time.
However, if I leave the repository be for a while, the cycle has to be
repeated.
Can anyone smell the problem? I access the repository via svn+ssh://
f
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Very frequent transaction failure
Posted by Nico Kadel-Garcia <nk...@comcast.net>.
Filip Miletic wrote:
> Greetings. I run a svn server (svnserve) version 1.3.2 that, out of a
> sudden began consistently making the following error.
Perhaps you have a bad disk? Or perhaps you should tell us which OS, which
Berkeley DB release you're using, etc., etc., etc.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Very frequent transaction failure
Posted by Alan Ezust <al...@gmail.com>.
Hi, I was searching the archives of this mailing list for more ideas,
and found some. Most of them are in a thread with the subject
"berkeley db help for a newbie". Be sure to read that whole thread.
On 10/24/06, Filip Miletic <f....@tudelft.nl> wrote:
> Alan Ezust wrote:
> > I have exactly the same problem - periodic fatal errors when multiple
> > people are accessing a common repository via svn+ssh.
> >
> > "svn: Berkeley DB error while opening environment for filesystem
> > /var/local/svn/db:
> > DB_RUNRECOVERY: Fatal error, run database recovery
> > svn: bdb: PANIC: fatal region error detected; run recovery"
> >
> > After I run the recovery (as root), I need to fix the permissions
> > again so that the whole group has write permissions to all the files
> > there, before people can commit and update again.
> I apply the same workaround. My setting is very simple though. I use
> most of the repository myself, and others access it only infrequently.
> Regardless, I get frequent errors like this one, and have since learned
> to live with this svn "feature".
>
> f
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Very frequent transaction failure
Posted by Filip Miletic <f....@tudelft.nl>.
Ryan Schmidt wrote:
> On the one hand, you should not need to run recovery so often.
> [...] Or switch to an FSFS repository which cannot get wedged like
> that. Conversion instructions are in the FAQ.
FWIW, I opted for the second solution, i.e. to migrate the repository to
fsfs. The link to the appropriate FAQ section is here:
http://subversion.tigris.org/faq.html#bdb-fsfs-convert
The instructions were straightforward in my case, given that my SVN
repositories are low-bandwidth and that I did not need to copy either
templates or hooks. YMMV.
Greets,
f
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Very frequent transaction failure
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Oct 24, 2006, at 10:25, Filip Miletic wrote:
> Alan Ezust wrote:
>> I have exactly the same problem - periodic fatal errors when multiple
>> people are accessing a common repository via svn+ssh.
>>
>> "svn: Berkeley DB error while opening environment for filesystem
>> /var/local/svn/db:
>> DB_RUNRECOVERY: Fatal error, run database recovery
>> svn: bdb: PANIC: fatal region error detected; run recovery"
>>
>> After I run the recovery (as root), I need to fix the permissions
>> again so that the whole group has write permissions to all the files
>> there, before people can commit and update again.
> I apply the same workaround. My setting is very simple though. I use
> most of the repository myself, and others access it only infrequently.
> Regardless, I get frequent errors like this one, and have since
> learned
> to live with this svn "feature".
On the one hand, you should not need to run recovery so often.
On the other hand, the video about Subversion 1.4 says that it will
(with BDB 4.4?) automatically run BDB recovery when needed, so you
may want to upgrade to that. Or switch to an FSFS repository which
cannot get wedged like that. Conversion instructions are in the FAQ.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Very frequent transaction failure
Posted by Filip Miletic <f....@tudelft.nl>.
Alan Ezust wrote:
> I have exactly the same problem - periodic fatal errors when multiple
> people are accessing a common repository via svn+ssh.
>
> "svn: Berkeley DB error while opening environment for filesystem
> /var/local/svn/db:
> DB_RUNRECOVERY: Fatal error, run database recovery
> svn: bdb: PANIC: fatal region error detected; run recovery"
>
> After I run the recovery (as root), I need to fix the permissions
> again so that the whole group has write permissions to all the files
> there, before people can commit and update again.
I apply the same workaround. My setting is very simple though. I use
most of the repository myself, and others access it only infrequently.
Regardless, I get frequent errors like this one, and have since learned
to live with this svn "feature".
f
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Very frequent transaction failure
Posted by Alan Ezust <al...@gmail.com>.
I have exactly the same problem - periodic fatal errors when multiple
people are accessing a common repository via svn+ssh.
"svn: Berkeley DB error while opening environment for filesystem
/var/local/svn/db:
DB_RUNRECOVERY: Fatal error, run database recovery
svn: bdb: PANIC: fatal region error detected; run recovery"
After I run the recovery (as root), I need to fix the permissions
again so that the whole group has write permissions to all the files
there, before people can commit and update again.
Using svnserve, version 1.1.4 (r13838)
1.4.0-5 - libsvn1 (5 1.4.0-5) libapr1 (0 (null)) libc6 (2 2.3.6-6)
libsvn1 (2 1.4) subversion-tools (0 (null)) db4.4-util (0 (null))
patch (0 (null))
1.1.4-2 - libapr0 (2 2.0.54) libc6 (2 2.3.2.ds1-21) libdb4.2 (0
(null)) libexpat1 (2 1.95.8) libldap2 (2 2.1.17-1) libneon24 (2
0.24.7.dfsg) libssl0.9.7 (0 (null)) libsvn0 (2 1.1.4-2) libxml2 (2
2.6.16) zlib1g (2 1:1.2.1) patch (0 (null)) db4.2-util (0 (null))
subversion-tools (0 (null))
I've seen this not only on this particular system, but on another
svnserve also, so this seems to be a common problem. Is there some
sort of setting or permission I can set so that this doesn't keep
happening? Or is it a bug that's fixed in a newer version?
On 3/18/06, Filip Miletic <fi...@gmail.com> wrote:
> Greetings. I run a svn server (svnserve) version 1.3.2 that, out of a
> sudden began consistently making the following error.
>
> If I don't commit for some time, say a day or two, and then revert with
> a commit, the following message appears.
>
> svn: Commit failed (details follow):
> svn: Connection closed unexpectedly
>
> Retrying the commit then gives:
>
> svn: Commit failed (details follow):
> svn: Berkeley DB error for filesystem /usr/local/src/svnroot/db while
> opening environment:
> DB_RUNRECOVERY: Fatal error, run database recovery
> svn: bdb: PANIC: fatal region error detected; run recovery
>
> Any further commits fail in the same way until I run 'svnadmin recover'
> on the repository. After yet another 'svn update' I am able to commit
> for some time.
>
> However, if I leave the repository be for a while, the cycle has to be
> repeated.
>
> Can anyone smell the problem? I access the repository via svn+ssh://
>
> f
>
>
> ---------------------------------------------------------------------
> 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