Problem: My slapd.conf cannot be commited

Problem:

My slapd.conf cannot be commited
The cause of this issue maybe some missing “info” files.
If this is the cause, the slapd.conf can be build with the following command as a temporary workaround.
cat /etc/univention/templates/files/etc/ldap/slapd.conf.d/* | ucr filter > slapd.conf

If you now the missing parts you can search for them in
/etc/univention/templates/info
looking for ldapacl files:

~# ls -lah /etc/univention/templates/info/|grep ldapacl
-rw-r--r-- 1 root nogroup  158 Mai 29  2020 ldapacl_58openid-connect-provider.ldapacl.info
-rw-r--r-- 1 root nogroup  155 Apr 21 17:40 ldapacl_66univention-appcenter_app.acl.info
-rw-r--r-- 1 root nogroup  169 Apr 21 17:38 ldapacl_66univention-ldap-server_acl-master-uvmm.acl.info

A file can look like this:

cat /etc/univention/templates/info/ldapacl_66univention-appcenter_app.acl.info
Type: multifile
Multifile: etc/ldap/slapd.conf

Type: subfile
Multifile: etc/ldap/slapd.conf
Subfile: etc/ldap/slapd.conf.d/66univention-appcenter_app.acl

You can see this is building the slapd.conf

Or you can also search for slapd.conf.d to get subfile use.
rgrep slapd.conf.d /etc/univention/templates/info/

Solution:

You can copy the missing files from the backup server, if you have one, and try the ucr commit /etc/ldap/slapd.conf

An other possible solution is to initialize the ldap_extension module. This step should be tested in a testenvironment.
univention-directory-listener-ctrl resync ldap_extension

Also interesting according ucr commit issues:

Mastodon