** Description changed: + 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. + + TEST CASE: + Steps to re-produce on a new Lucid install + sudo apt-get install slapd ldap-utils + Follow 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=example,dc=com): Program version 4.8 doesn't match environment version 4.7 + + REGRESSION POTENTIAL: + Limited; impacts upgrades to latest version of slapd and 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#011bui...@yellow:/build/buildd/openldap-2.4.23/debian/build/servers/slapd Oct 11 06:10:32 helium slapd[12131]: bdb(dc=5200-glenwood,dc=net): Program version 4.8 doesn't match environment version 4.7 Oct 11 06:10:32 helium slapd[12131]: hdb_db_open: database "dc=5200-glenwood,dc=net" cannot be opened, err -30971. Restore from backup! Oct 11 06:10:32 helium slapd[12131]: bdb(dc=5200-glenwood,dc=net): txn_checkpoint interface requires an environment configured for the transaction subsystem Oct 11 06:10:32 helium slapd[12131]: bdb_db_close: database "dc=5200-glenwood,dc=net": txn_checkpoint failed: Invalid argument (22). Oct 11 06:10:32 helium slapd[12131]: backend_startup_one (type=hdb, suffix="dc=5200-glenwood,dc=net"): bi_db_open failed! (-30971) Oct 11 06:10:32 helium slapd[12131]: bdb_db_close: database "dc=5200-glenwood,dc=net": alock_close failed 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 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 11 06:07:49 2010InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: - PATH=(custom, user) - LANG=en_US.UTF-8 - SHELL=/bin/bashSourcePackage: openldap + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bashSourcePackage: openldap + 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. - - TEST CASE: - Steps to re-produce on a new Lucid install - - sudo apt-get install slapd ldap-utils - - Follow the Lucid Server guide through the section entitled populating - LDAP to the point where data is loaded into ldap for the backend - configuration. - - 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=example,dc=com): - Program version 4.8 doesn't match environment version 4.7
** Description changed: - IMPACT: - Currently all configured openldap installations being upgraded from Lucid -> Maverick will fail due to underlying database version incompatibility. + 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. + 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. - TEST CASE: - Steps to re-produce on a new Lucid install - sudo apt-get install slapd ldap-utils - Follow 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=example,dc=com): Program version 4.8 doesn't match environment version 4.7 + 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=example,dc=com): Program version 4.8 doesn't match environment version 4.7 REGRESSION POTENTIAL: Limited; impacts upgrades to latest version of slapd and 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#011bui...@yellow:/build/buildd/openldap-2.4.23/debian/build/servers/slapd Oct 11 06:10:32 helium slapd[12131]: bdb(dc=5200-glenwood,dc=net): Program version 4.8 doesn't match environment version 4.7 Oct 11 06:10:32 helium slapd[12131]: hdb_db_open: database "dc=5200-glenwood,dc=net" cannot be opened, err -30971. Restore from backup! Oct 11 06:10:32 helium slapd[12131]: bdb(dc=5200-glenwood,dc=net): txn_checkpoint interface requires an environment configured for the transaction subsystem Oct 11 06:10:32 helium slapd[12131]: bdb_db_close: database "dc=5200-glenwood,dc=net": txn_checkpoint failed: Invalid argument (22). Oct 11 06:10:32 helium slapd[12131]: backend_startup_one (type=hdb, suffix="dc=5200-glenwood,dc=net"): bi_db_open failed! (-30971) Oct 11 06:10:32 helium slapd[12131]: bdb_db_close: database "dc=5200-glenwood,dc=net": alock_close failed 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 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 11 06:07:49 2010InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: openldap - 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. ** Description changed: 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=example,dc=com): Program version 4.8 doesn't match environment version 4.7 REGRESSION POTENTIAL: - Limited; impacts upgrades to latest version of slapd and changes are in installation scripts only. + 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#011bui...@yellow:/build/buildd/openldap-2.4.23/debian/build/servers/slapd Oct 11 06:10:32 helium slapd[12131]: bdb(dc=5200-glenwood,dc=net): Program version 4.8 doesn't match environment version 4.7 Oct 11 06:10:32 helium slapd[12131]: hdb_db_open: database "dc=5200-glenwood,dc=net" cannot be opened, err -30971. Restore from backup! Oct 11 06:10:32 helium slapd[12131]: bdb(dc=5200-glenwood,dc=net): txn_checkpoint interface requires an environment configured for the transaction subsystem Oct 11 06:10:32 helium slapd[12131]: bdb_db_close: database "dc=5200-glenwood,dc=net": txn_checkpoint failed: Invalid argument (22). Oct 11 06:10:32 helium slapd[12131]: backend_startup_one (type=hdb, suffix="dc=5200-glenwood,dc=net"): bi_db_open failed! (-30971) Oct 11 06:10:32 helium slapd[12131]: bdb_db_close: database "dc=5200-glenwood,dc=net": alock_close failed 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 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 11 06:07:49 2010InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: openldap 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. -- 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) https://bugs.launchpad.net/bugs/658227 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
