FC3 openldap-2.2.29 breaks DB
Jason L Tibbitts III
tibbs at math.uh.edu
Wed Dec 7 03:37:33 UTC 2005
>>>>> "LMFR" == Luciano Miguel Ferreira Rocha <strange at nsk.no-ip.org> writes:
LMFR> bdb_db_init: Initializing BDB database
LMFR> bdb(dc=udp,dc=eurotux,dc=com): Program version 4.3 doesn't match
LMFR> environment version
I saw the same thing, but only on three out of four servers. I don't
understand why one server worked. I think the underlying issue is
that slapd is statically linked against the DB library, and the new
version is linked against a newer version than the old one. I haven't
pried the SRPM apart to make sure.
LMFR> I resolved the situation by downgrading.
I resolved by doing slapcat before upgrading, then cleaning out the
database and doing a slapadd.
LMFR> Was this expected? The update email mensioned backups (the
LMFR> upgrade was automated, I'd never expected a minor upgrade to
LMFR> break the DB), but not that it would be compulsory.
The package was posted for testing well in advance of its release, but
unfortunately I never found the time to test it.
LMFR> If it was, or if it was likely, couldn't next updates do a
LMFR> backup on pre-un and a restore on post?
That's a scary operation to just run automatically. Better would be
to ensure that DB version changes like this don't happen except during
distro version upgrades.
- J<
More information about the fedora-test-list
mailing list