[Pkg-openldap-devel] Upgrades fail due to checkpoint directive
quanah at zimbra.com
Sat Dec 22 03:33:30 UTC 2007
--On Friday, December 21, 2007 3:31 PM -0800 Russ Allbery <rra at debian.org>
> The current slapd package writes a checkpoint configuration directive
> directly after the backend directive for bdb:
> backend bdb
> checkpoint 512 30
> OpenLDAP 2.4.7 can't cope with this:
> Loading from /var/backups/slapd-2.3.38-1:
> - directory dc=stanford,dc=edu... failed.
> Loading the database from the LDIF dump failed with the following
> error while running slapadd:
> /etc/ldap/slapd.conf: line 42: unknown directive <checkpoint> outside
> backend info and database definitions. slapadd: bad configuration
> Deleting the checkpoint configuration setting fixes the problem, as does
> moving it below the database and suffix settings.
> This is pretty bad. I'm not sure what to do about this. We could just
> remove checkpoint completely from the configuration, but my understanding
> is that it's important. Trying to figure out how to move it around in an
> arbitrary configuration file is going to be fairly hard.
> Why did upstream make this change? Was it actually intentional?
I think it has to go more concretely inside the database definitions now.
;) (As you found). It may be worthwhile following up with -devel just to
confirm it was intentional though. My guess is it has to do with the
expanded support for the config backend.
Principal Software Engineer
Zimbra :: the leader in open source messaging and collaboration
More information about the Pkg-openldap-devel