package slapd failed to upgrade from hardy to intrepid - failed to convert slapd.conf to slapd.d/

I removed /etc/ldap/slapd.d, and `dpkg --configure slapd` crashed not finding /var/run/slapd. I created that directory, and `dpkg --configure slapd` completed.

One issue here is the assumption that I *want* to use the directory structure instead of a slapd.conf file - but I'm supporting a client that has a slapd.conf file. Shouldn't this be optional?

On Tue, Feb 24, 2009 at 07:05:08PM -0000, notromda wrote:
> Public bug reported:
>
> I don't even know where to begin here - I had modified slapd.conf to
> mirror a specific client setup, which was/is working fine, but I think
> the upgrade process is not liking the format or the directory structure
> - I don't know.

According to the log:

Setting up slapd (2.4.11-0ubuntu6.1) ...
Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.4.9-0ubuntu0.8.04.1... done.
mkdir: cannot create directory `/etc/ldap/slapd.d/': File exists
dpkg: error processing slapd (--configure):
subprocess post-installation script returned error exit status 1

Did you create the directory /etc/ldap/slapd.d/ by hand before the upgrade?

  status incomplete

--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com

No, I hadn't. This first happened when I updated from Hardy to Intrepid, and all subsequent updates. In any case, I think the configure script should handle this gracefully, and/or ask if the slapd.conf should be migrated to slapd.d format.

(IMHO the new slapd.d format took a bad config design and made it worse, but that doesn't matter here)

Could you post the original slapd.conf file (with private information such as rootpw and rootdn obfuscated)?

i think you need romove slapd trong synaptic and install again.

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!