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

Re: Berkeley db version problem

From: Ulrich Eckhardt <eckhardt_at_satorlaser.com>
Date: 2004-10-04 10:36:39 CEST

Robert Rapp wrote:
> In my apache error log I see the following:
> [Sun Oct 03 19:10:21 2004] [error] [client 192.168.11.31] (20014)Error
> string not specified yet: Bad database version: compiled with 4.1.25,
> running against 4.2.52
[...]
> And looking at the libraries that svn and apache are built against
> reveals the following:
> [root@tiny /]# ldd /usr/bin/svn | fgrep libdb
> libdb-4.1.so => /usr/lib/libdb-4.1.so (0x400bc000)
> libdb-4.2.so => /usr/lib/libdb-4.2.so (0x406be000)

That is seriously broken. Subversion advises not to use 4.1 because of issues
that lead to corruption. If your packages link against that, you are better
advised to get different packages or compile them yourself using only 4.2 in
the same version that Apache uses.

> Third, how could I verify the db version in my repos? I don't know much
> about Berkeley db. Is there a command line tool that I can run against
> the db to find its version?

Not sure, but if I were you, I'd dump the repository with a working version.
The reason is that even if Subversion does not change its BD layout, the
format of BDB could have changed between 4.1 and 4.2. There might be
upgrade-tools, but I'm not sure about that.

Uli

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 4 10:37:40 2004

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.