[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Svn is Wedged: DB_INCOMPLETE: Cache flush was unable to complete

From: Peter Kahn <pkahn_at_connected.com>
Date: 2005-01-18 19:52:32 CET

I am having a problem with SVN. This is my second outage in a week.
Anyone have any ideas what kind of information I can gather so I can
properly trouble shoot the problem?

 svn: version 1.1.1 (r11581) compiled Oct 31
2004, 08:30:56
 protocols supported: svnserve & WebDav
 Apache: 2.0.52
 OS: Linux 2.4.20-8
 Notes: we also use WebSVN

        svn 1.1.1 on Win32, MacOS X and Linux
        svn 1.1.2 on Win32

Just about lunch time, we started getting the error:
        svn: Berkeley DB error while checkpointing after Berkeley
                DB transaction for filesystem /home/svn/repos/db:
                DB_INCOMPLETE: Cache flush was unable to complete

I have nothing in my OS logs. I am running with a permissions hook
script that logs transactions. My last commit attempt that made it to
the pre-commit stage was as follows:
        commit attempt path-to-repos krp
        2005-01-18 12:19:08 -0500 (Tue, 18 Jan 2005)

If I am to debug this to prevent it happening again, information should
I capture, what things can I try?

Here is my plan to date:
1. backup wedged repository directory
2. run recovery on repository
3. on another machine begin to prep for 1.1.2 upgrade
4. when recovery is completed, enable only svnserve and not webdav or
websvn in an attempt to determine problems

Any comments on this kind of plan?

Any help would be greatly appreciated. Thanks.

Peter Kahn
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jan 18 19:52:49 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.