package slapd 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

[Torkil Svensgaard]

Install failed

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: slapd 2.4.31-1+nmu2ubuntu8
ProcVersionSignature: Ubuntu 3.2.0-64.97-virtual 3.2.59
Uname: Linux 3.2.0-64-virtual x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
Date: Mon Jun 23 11:20:56 2014
DuplicateSignature: package:slapd:2.4.31-1+nmu2ubuntu8:ErrorMessage: subprocess installed post-installation script returned error exit status 1
ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2012-11-13 (586 days ago)
InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3)
SourcePackage: openldap
Title: package slapd 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to trusty on 2014-06-23 (0 days ago)
mtime.conffile..etc.apparmor.d.usr.sbin.slapd: 2012-11-20T12:43:35.122872

[Ryan Tandy (rtandy)]

Hi Torkil,

The error message from the upgrade is really unusual:

    slapadd: line 1: cannot add entry with empty dn=""

Did your previous database actually contain an entry with an empty dn?

Does the dump that was created during the upgrade actually correspond to the previous state of your database?

[Torkil Svensgaard (torkil-a)]

Hi

As to the former, I'm unsure how to check but looking at the toplevel
entry in phpldapadmin the dn entry isn't empty. I'll be happy to provide
whatever information is needed if someone lets me know what to do.

As to the latter I've rolled the machine back to a previous snapshot and
no longer have the backup dump, but I noticed that the two topmost
entries in the file had empty dn fields.

Mvh.

Torkil

On 06/23/2014 04:18 PM, Ryan Tandy wrote:
> Hi Torkil,
>
> The error message from the upgrade is really unusual:
>
> slapadd: line 1: cannot add entry with empty dn=""
>
> Did your previous database actually contain an entry with an empty dn?
>
> Does the dump that was created during the upgrade actually correspond to
> the previous state of your database?
>

--
Torkil Svensgaard
Sysadmin
MR-Forskningssektionen, afs. 714
DRCMR, Danish Research Centre for Magnetic Resonance
Hvidovre Hospital
Kettegård Allé 30
DK-2650 Hvidovre
Denmark
Tel: [phone]
E-mail: <email address hidden>

[Ryan Tandy (rtandy)]

On 24/06/14 03:11 AM, Torkil Svensgaard wrote:
> I noticed that the two topmost entries in the file had empty dn
> fields.

OK, so that part at least is confirmed.

Can you do "sudo -u openldap slapcat > /tmp/db.ldif" and see whether
that file has those entries? e.g. "grep '^dn: $' /tmp/db.ldif"

If the bogus entries are in your database, to get rid of them you'll
probably have to perform a slapcat dump like above, edit the LDIF, and
slapadd it into an empty database (see the relevant manpages and the
OpenLDAP Admin Guide for details).

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1304069, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.