Full_Name: Dieter Kluenter Version: 2.4.44 OS: openSUSE URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (93.214.226.147) It seems that the config backend provides schema information only after configuration data, this leads to following error: ./slapd -h "ldap://:9007/ ldapi:///" -F ../etc/openldap/slapd.d -d256 580f76bd config error processing cn=config: olcDitContentRules: ObjectClass not found: "2.16.840.1.113730.3.2.2" 580f76bd slapd stopped. ile While the same process only with information based on slapd.conf is successful: ./slapd -h "ldap://:9007/ ldapi:///" -f ../etc/openldap/slapd.conf -d256 580f76e4 slapd starting The slapd.configuration: include /opt/openldap/etc/openldap/schema/core.schema include /opt/openldap/etc/openldap/schema/cosine.schema include /opt/openldap/etc/openldap/schema/inetorgperson.schema include /opt/openldap/etc%2pepenldap/schema/nis.schema ditcontentrule ( 2.16.840.1.113730.3.2.2 NAME 'sys4Person' AUX ( posixAccount ) ) [more configuration parameter] slapd.d dn: cn=config objectClass: olcGlobal cn: config ... olcToolThreads: 1 olcWriteTimeout: 0 olcDitContentRules: {0}( 2.16.840.1.113730.3.2.2 NAME 'sys4Person' AUX posix Account ) ... -Dieter
moved from Incoming to Software Bugs
DIT content rule handling needs reworking for OpenLDAP 2.6 when cn=config is in use.
Just like with attribute and objectclass definitions, these are stored under cn=schema,cn=config as the file that defined them or directly in cn=config if defined in slapd.conf directly (as you're doing here). Maybe keep them in a file that you also include. Don't know if we should document this behaviour or change it in some way.
Need to document how to correctly include this type of configuration as a part of an additional schema include.