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

Re: svnadmin dump || hotcopy : Program version matching error

From: Ryan Schmidt <subversion-2009b_at_ryandesign.com>
Date: Tue, 20 Oct 2009 13:53:45 -0500

On Oct 20, 2009, at 05:44, Nicolas.Castagne_at_imag.fr wrote:

>> Client-side settings are in the file ~/.subversion/config
> Definitely, nothing related to the problem there.
>> Server-side settings depend on how your server is set up.
> It is accessed using apache.

Ok. Then your server-side settings are in httpd.conf, or in a file
included from there.

I don't expect there will be anything related to your problem in there
either; just telling you where the settings are, since you asked.

> 1/ when using svnadmin from the machine where the repositories are,
> most
> subcommands throw an error in the form:
> “svn: Berkeley DB error while opening environment for filesystem
> cordisoff/db:
> Argument invalide
> svn: bdb: Program version 4.2 doesn't match environment version”

Then your svnadmin was built for a version of BerkeleyDB different
from 4.2.

> 2/ when using svn with the http protocol, from ANY machine, everything
> goes always OK.

Then presumably your mod_dav_svn was built for BerkeleyDB 4.2. So it
sounds like your mod_dav_svn may not be matched with the rest of your
Subversion software. On many systems, you need to manually copy
mod_dav_svn to the right place for Apache to see when you upgrade
Subversion, so don't forget this step.

> 3/ Versions and format on the svn server are:
> - svn version is 1.1.4
> - The repositories’ “format” is “3”
> - intalled bdb version is 4.2 (eg db4.2_dump, libdb4.2, etc.)

Subversion 1.4.x and earlier are unsupported now, so I'm hopeful
you'll be able to upgrade to the current version and get your
repository working with it.

> 1/ is it possible to secure temporarily the repositories, before
> updating
> the server’s configuration, since “svnadmin dump" does not work ?

You can take the server offline (e.g. stop Apache) and then use "tar"
or even just "cp -Rp" to make a copy of the repository directories for
backup purposes. This isn't a good general-purpose backup strategy
because this repository won't necessarily work on another computer,
another OS, another BDB version, etc. But for purposes of backing up
before doing a potentially destructive action on this server, with the
intention of restoring the backup to this same server in the event of
a problem, it's fine.

> 2/ should I try updating the concerned packages using simply my linux
> distribution’s package maintainer ?

If that's how they were installed initially, that might be a good
place to start.

> 3/ Apparently I should "upgrade my repository" to work around bdb
> version
> problem (eg
> http://svn.collab.net/repos/svn/trunk/notes/repos_upgrade_HOWTO )

That document seems to relate to Subversion repository schema changes,
not to BerkeleyDB version changes, so I don't think it's applicable to
your situation.

> Upgrading requires “using an old binary of svnadmin with the same
> schema
> version as my repository” (3 in my case).
> How may I get the appropriate “old binary”?

That depends on how you usually install software on your server. For
example, perhaps you could use your package management system for
this. But again, I'm not certain using an older version will be
necessary at all.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-20 20:54:47 CEST

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