do-release-upgrade -d completely successfully with no errors; this
message from the log above is a bit misleading:
Starting OpenLDAP: slapd.
slapd starts and then fails when it tried to attach to the database
(with the associated 4.7/4.8 error message).
--
won't start after Maverick upgrade;
Thanks for reporting this bug and any supporting documentation. Since
this bug has enough information provided for a developer to begin work,
I'm going to mark it as confirmed and let them handle it from here.
Thanks for taking the time to make Ubuntu better!
** Changed in: openldap (Ubuntu)
** Description changed:
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
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/658227/+attachment/1684127/+files/Dependencies.txt
--
won't start after Maverick upgrade; bdb Program version 4.8 doesn't match
environment version 4.7
https://bugs.launchpad.net/bugs/658227
You received this bug
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.
** Bug watch added: Debian Bug tracker #595672
OK, per https://bbs.archlinux.org/viewtopic.php?id=84077 and then
http://dbaspot.com/forums/berkeley-db/265933-how-upgrade-4-2-4-3-a.html,
I installed db4.7-utils and ran
cd /var/lib
cp -a ldap ldap.bak
cd ldap
db4.7_checkpoint -1
db4.7_recover
After that, slapd started normally.
--
won't
Can you look through the /var/log/dist-upgrade/apt-term.log and post the
lines that come from the upgrade of the slapd package?
(I don't know off hand if any of the discussion there applies in the
Lucid-to-Mavick upgrade case, but in case it's helpful I'll point you to
LP #536958, which covers
Ubuntu devs,
I took a quick look at the slapd.posting/slapd.scripts-common files in
the lp:ubuntu/maverick/openldap branch, and also in the Bazaar change
summary for revision 26 (which is the one that includes the note Use
libdb4.8-dev (LP: #572489)), but I don't see any edits to the postinst
Confirmed; 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
** Description changed:
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
Note that the way the pre and post installation scripts should upgrade
the database is to dump the data from the pre-upgrade database using
slapcat, wipe out the existing database files and then reload from the
pre-upgrade data dumped to disk in the post-installation step.
However as @Nathan
Here are excerpts from apt/term.log. Note that this is in a different
apt log because my dist-upgrade was a little unusual - interrupted, then
completed in a second session. I'm attaching the complete apt log file
in case it's of interest.
Log started: 2010-10-11 03:59:04
snip
Restarting
** Changed in: openldap (Ubuntu)
Importance: Undecided = Low
--
won't start after Maverick upgrade; bdb Program version 4.8 doesn't match
environment version 4.7
https://bugs.launchpad.net/bugs/658227
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Andrew,
As we expected, this shows that the slapd scripts made no attempt to do an
export/import cycle on your database. (When that happened during my
Hardy-Lucid upgrade, I had a Dumping... line, like this:
Preparing to replace slapd 2.4.9-0ubuntu0.8.04.3 (using
I just remembered that the postinst failure I mentioned in my previous
post wasn't triggered by the restart of the slapd daemon, but rather by
another step that the postinst script was attempting to do at that time.
So, in your case, did the apt upgrade/configure cycle appear to complete
15 matches
Mail list logo
