slaptest conversion does not configure monitor module

Bug #301898 reported by Bryan McLellan
2
Affects Status Importance Assigned to Milestone
openldap (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

The intrepid package defaults to using -F and /etc/ldap/slapd.d. The postinst file uses slaptest to try to convert existing configurations to the newer directory format, however this does not configure the monitor backend module.

a 'olcDatabase={1}monitor.ldif' file is produced in /etc/ldap/slapd.d, but not the expected 'cn=module{1}.ldif'

This is particularly troubling as openldap still lacks the proper documentation for configuring monitoring using the new configuration layout:

http://www.openldap.org/doc/admin24/guide.html#Monitoring

Revision history for this message
Bryan McLellan (btm) wrote :

mkdir -p /tmp/slap/slapd.d
# save attached config to /tmp/slap
slaptest -f /tmp/slap/slapd.conf -F /tmp/slap/slapd.d
# works

# Edit /tmp/slapd/slapd.d/cn=config/cn=module{0}.ldif and remove "olcModuleLoad: {1}back_monitor"
slaptest -f /tmp/slap/slapd.conf -F /tmp/slap/slapd.d
# does not work, will not modify existing file

Revision history for this message
Mathias Gug (mathiaz) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

I've successfully converted the attached slapd.conf. Even though cn=module{1}.ldif doesn't exist, back_monitor is available in cn=module{0}.ldif:

mathiaz@intrepid-base:~/d/cn=config$ cat cn\=module\{0\}.ldif
dn: cn=module{0}
objectClass: olcModuleList
cn: module{0}
olcModulePath: /usr/lib/ldap
olcModuleLoad: {0}back_hdb
olcModuleLoad: {1}back_monitor
structuralObjectClass: olcModuleList
entryUUID: e879a08a-a14e-102d-9f99-51c73c9858e4
creatorsName: cn=config
createTimestamp: 20090309233650Z
entryCSN: 20090309233650.678062Z#000000#000#000000
modifiersName: cn=config
modifyTimestamp: 20090309233650Z

Marking this bug invalid as back_monitor is configured after the upgrade.

Changed in openldap:
status: New → Invalid
Revision history for this message
Bryan McLellan (btm) wrote :

Wow, I have no idea what I was thinking back then.

Most likely, the problem was the switch to the slapd.d directory really only lets you run slaptest once. Once the directory exists, you're stuck with it. Unless of course you delete the directory, edit slapd.conf, and run slaptest again.

I think my ignorance that you could delete the slapd.d folder safely and rerun slaptest was at play, combined with the lack of any documentation [at the time] for configuring monitoring in the new format.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.