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

Re: svn.collab.net intermittent failures

From: Blair Zajac <blair_at_orcaware.com>
Date: 2003-04-12 18:56:21 CEST

Karl Fogel wrote:
>
> Sorry about the downtime, folks.
>
> We upgraded svn.collab.net to use Berkeley DB 4.1.25 recently, because
> we were seeing problems whereby bdb log files weren't being released.
> Certain patches and ChangeLog entries at sleepycat.com indicated that
> upgrading to 4.1.25 might solve the problem. (We left Apache at
> 2.0.44 and Subversion at 0.18.1, however.)
>
> After that, we saw different problems. Mike Pilato was doing all
> this, so I can't describe the problems with complete precision, but
> basically requests in the `nodes' table kept causing DB_RUNRECOVERY to
> be returned. Recovery itself would go smoothly, and then the
> repository would be okay until the next time, ten minutes later.

The trouble seems to continue:

% svn update
subversion/libsvn_ra_dav/util.c:391: (apr_err=160029)
svn: Berkeley DB error
svn: REPORT request failed on '/repos/svn/trunk'
subversion/libsvn_ra_dav/util.c:152: (apr_err=160029)
svn:
Berkeley DB error while opening environment for filesystem /usr/www/repositories/svn/db:
DB_RUNRECOVERY: Fatal error, run database recovery

As a note on the repository I had trouble with, the repos had only 2 revisions
when I was committing a third. The svn client was connecting via localhost to a
SSL repository when it hung. I did a series of control-C's which didn't stop
svn, so I had to kill it. Very odd.

Best,
Blair

-- 
Blair Zajac <blair@orcaware.com>
Plots of your system's performance - http://www.orcaware.com/orca/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 12 18:57:15 2003

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