[Pkg-openldap-devel] Bug#603544: Bug#603544: rc bug?

[Frederik Himpe]

On Wed, 2011-01-12 at 08:35 +0100, Matthijs Mohlmann wrote:

> About fixing this:
> Change the accesslog directory in the configuration to:
> directory /var/lib/ldap-accesslog
> 
> Create that directory and rerun the upgrade procedure.
> 
> Regards,

Yes, but IMO that 's only a work-around: slapd scripts should not break
my working configuration.


After moving the accesslog to another directory, I hit another problem:
the migration fails when the back-up directory already exists:

Setting up slapd (2.4.23-7) ...
  Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.4.11-1
+lenny2... done.
  Moving old database directories to /var/backups:

  Backup path /var/backups/cn=accesslog-2.4.11-1+lenny2.ldapdb exists.
Giving up...
dpkg: error processing slapd (--configure):
 subprocess installed post-installation script returned error exit
status 1


After removing the back-ups in /var/backups and retrying, I get:

Setting up slapd (2.4.23-7) ...
  Backing up /etc/ldap/slapd.conf in /var/backups/slapd-2.4.11-1
+lenny2... done.
  Moving old database directories to /var/backups:
  - directory dc=ai,dc=vub,dc=ac,dc=be... done.
  Loading from /var/backups/slapd-2.4.11-1+lenny2: 
  - directory cn=accesslog... failed.

Loading the database from the LDIF dump failed with the following
error while running slapadd:
    /var/backups/slapd-2.4.11-1+lenny2/cn=accesslog.ldif: No such file
or directory

There is only a slapd.conf in that directory.

slapd 2.4.23 in itself is working fine actually, it's just that
migration script which continues to fail on every package installation
and which leaves my slapd stopped.


-- 
Frederik Himpe <fhimpe at vub.ac.be>
Vrije Universiteit Brussel