[Date Prev][Date Next] [Chronological] [Thread] [Top]

(ITS#8388) broken schema after replacing objectClass

Full_Name: Tomasz Leśniewski
Version: 2.4.44
OS: ubuntu
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (

accidentally i broke my openldap schema when i've changed one of objectClass
definitions. For example i have two objectClasses and one is a parent for

olcObjectClasses: {0}( NAME 'foo' DESC '' SUP top AUXILIARY X-ORIGIN
'user defined' )
olcObjectClasses: {1}( NAME 'bar' DESC '' SUP foo AUXILIARY X-ORIGIN
'user defined' )

I've changed definition of foo - i've delete this object and (my mistake) put it
without any number at bottom of all classes:

dn: cn=config
changetype: modify
delete: olcObjectClasses
olcObjectClasses: {0}
add: olcObjectClasses
olcObjectClasses: ( NAME 'foo' DESC '' SUP top AUXILIARY X-ORIGIN 'user
defined' )

So i have now class bar at top of schema and foo at bottom. After restart slapd
won't start. Slapcat says:

56d4678f olcObjectClasses: value #5 olcObjectClasses: ObjectClass not found:
56d4678f config error processing cn=config: olcObjectClasses: ObjectClass not
found: "foo"
slapcat: bad configuration file! 

Should slapd allow to make something that could break schema? I thought that
there are some constraints that not allow to remove objectClass which is parent
for another class.