upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so slapd aborts with "Program version 4.8 doesn't match environment version 4.7" error message)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openldap (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Lucid |
Invalid
|
High
|
James Page | ||
Maverick |
Fix Released
|
High
|
James Page | ||
Natty |
Fix Released
|
High
|
Unassigned |
Bug Description
IMPACT:Currently all configured openldap installations being upgraded from Lucid -> Maverick will fail due to underlying database version incompatibility.
FIX:slapd install/upgrade scripts already have functionality to dump existing ldap databases and re-load post upgrade. These have been amended to trigger when upgrading to 2.4.23+ as this is the point where the BDB upgrade was introduced. The fix has been tested using a PPA + modifying a lucid install to point at maverick repositories (do-release-upgrade disables PPA's so unable to test this way). Data loaded into ldap was verified pre and post upgrade.
PATCH: See proposed linked branch
TEST CASE:Steps to re-produce on a new Lucid install
sudo apt-get install slapd ldap-utilsFollow the Lucid Server guide through the section entitled populating LDAP to the point where data is loaded into ldap for the backend configuration and frontend data.Perform a Lucid->Maverick update:
sudo do-release-upgrade -d
slapd fails to start with the following error message: Oct 11 16:19:33 lucid-clone-01 slapd[773]: bdb(dc=
REGRESSION POTENTIAL:
Limited; impacts upgrades to latest version of slapd during lucid->maverick upgradeand changes are in installation scripts only.
ORIGINAL BUG REPORT:
I just upgraded from Lucid to Maverick, and now slapd won't start. From syslog:
Oct 11 06:10:31 helium slapd[12130]: @(#) $OpenLDAP: slapd 2.4.23 (Aug 7 2010 01:39:36) $#012#011buildd
Oct 11 06:10:32 helium slapd[12131]: bdb(dc=
Oct 11 06:10:32 helium slapd[12131]: hdb_db_open: database "dc=5200-
Oct 11 06:10:32 helium slapd[12131]: bdb(dc=
Oct 11 06:10:32 helium slapd[12131]: bdb_db_close: database "dc=5200-
Oct 11 06:10:32 helium slapd[12131]: backend_startup_one (type=hdb, suffix=
Oct 11 06:10:32 helium slapd[12131]: bdb_db_close: database "dc=5200-
Oct 11 06:10:32 helium slapd[12131]: slapd stopped.
Information on the web says that I need to run some kind of manual database upgrade to BDB 4.8, but I have no familiarity with the BDB tools, and the recipes that are suggested are varied and uncertain.
Please suggest a workaround or manual upgrade, as some of my network services are at a dead stop due to this problem.
Thanks,
Andrew.
ProblemType: BugDistroRelease: Ubuntu 10.10
Package: slapd 2.4.23-0ubuntu3
ProcVersionSign
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Mon Oct 11 06:07:49 2010Installatio
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=
WORKAROUND:
Install db4.7-util and recover slapd databases:
apt-get install db4.7-util
cd /var/lib
cp -a ldap ldap.bak
cd ldap
db4.7_checkpoint -1
db4.7_recover
slapd will then start correctly.
Related branches
- Mathias Gug: Pending requested
-
Diff: 45 lines (+15/-1)3 files modifieddebian/changelog (+7/-0)
debian/slapd.scripts-common (+1/-1)
debian/slapd.templates (+7/-0)
description: | updated |
Changed in openldap (Ubuntu): | |
importance: | Undecided → Low |
description: | updated |
summary: |
- won't start after Maverick upgrade; bdb "Program version 4.8 doesn't - match environment version 4.7" + upgrade process fails to upgrade underlying BDB format from 4.7 to 4.8 |
summary: |
- upgrade process fails to upgrade underlying BDB format from 4.7 to 4.8 + upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 |
Changed in openldap (Ubuntu): | |
importance: | Low → High |
Changed in openldap (Ubuntu): | |
assignee: | nobody → James Page (james-page) |
status: | Triaged → In Progress |
description: | updated |
description: | updated |
description: | updated |
tags: |
added: verification-done removed: verification-needed |
tags: | added: testcase |
This appears to be the same as http:// bugs.debian. org/cgi- bin/bugreport. cgi?bug= 595672 . A fix appears to have been released to that, but again I don't understand the cause or solution, or what I should do to recover at this point.