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

Re: invalid structural object class chain (ITS#1950)



try looking at this thread 
http://www.openldap.org/lists/openldap-software/200203/msg00132.html or
http://www.openldap.org/lists/openldap-software/200206/msg00285.html or 
search the list archives for a portion of the error message.

You may need to do something like change...

NAME 'account'
     SUP top
     STRUCTURAL

to...

NAME 'account'
     SUP posixaccount
     AUXILIARY

or something.

--Kervin


J.Campbell@bham.ac.uk wrote:
> Full_Name: Jim Campbell
> Version: 2.1.2
> OS: Solaris 2.6
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (147.188.40.2)
> 
> 
> Hi,
> I am getting a strange error having upgraded to 2.1.2 from 2.0.18 when trying
> to restore my database using slapadd having saved using slapcat.
> 
> Testing with adding a single entry using "ldapadd" which used to work fine
> gives:
> ------------- entry to be added -------------------
> dn: uid=jc,ou=People,dc=NP,dc=PH,dc=BHAM,dc=AC,dc=UK
> uid: jc
> cn: Jim Campbell
> givenName: Jim
> sn: Campbell
> mail: jc@np.ph.bham.ac.uk
> mailRoutingAddress: jc@np.ph.bham.ac.uk
> mailHost: np.ph.bham.ac.uk
> objectClass: inetLocalMailRecipient
> objectClass: person
> objectClass: organizationalPerson
> objectClass: inetOrgPerson
> objectClass: account
> objectClass: posixAccount
> objectClass: top
> objectClass: kerberosSecurityObject
> objectClass: shadowAccount
> userPassword: {crypt}.dh4A2U3NxvHU
> shadowLastChange: 10702
> krbName: jc@NP.PH.BHAM.AC.UK
> loginShell: /bin/csh
> uidNumber: 20
> gidNumber: 10
> homeDirectory: /home/jc
> gecos: Jim Campbell
> -------------- end of entry --------------------------------------
> 
> adding new entry "uid=jc,ou=People,dc=NP,dc=PH,dc=BHAM,dc=AC,dc=UK"
> ldapadd: update failed: uid=jc,ou=People,dc=NP,dc=PH,dc=BHAM,dc=AC,dc=UK
> ldap_add: Object class violation (65)
>         additional info: invalid structural object class chain
> (inetOrgPerson/account)
> 
> which is the same error as the bulk entry problem. It seems to be related to
> the "account" object class. Have there been changes to the schema which would
> affect this.
> 
> cheers
> Jim
>