Re: where is structuralObjectClass operational attribute generated ?

[Buchan Milne <bgmilne@obsidian.co.za>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

chuck@fiu.edu wrote:
> As pointed out by an astute reader, I forgot to state the software.
>
> It's openldap-2.1.23
>
>
> 8-)
> TIA
> Chuck Lyon
> UTS Enterprise Systems
> University Park PC 417A
> Florida International University
> Miami, FL  33199 PH (305) 348-2912
> ----- Forwarded by Chuck Lyon/FIU on 01/15/2004 03:25 PM -----
>
>
> Chuck Lyon
> 01/15/2004 12:48 PM
>
>
>         To:     openldap-software@OpenLDAP.org
>         cc:
>         Subject:        where is structuralObjectClass operational
attribute generated ?
>
> I hope I can get some help with this:
>
> I find a reference in the FAQ which implies the "No structuralObjectClass
> operational attribute" error is generated when attempting to maintain a
> slave server.  Cool so far, but where does the operational attribute
> information come from ?  The entry I'm trying to add has plenty of object
> class attributes which are structural.  The objectclasses are: person,
> organizationalPerson, inetOrgPerson, eduPerson, fiuEduPerson (all
> Structural), top (abstract). and posixAccount (Auxillary).  no errors
post
> to the master server log, and slurpd reports an "implementation specific"
> error. The log in the slave server gives the error stated above.  I just
> rebuilt everything from scratch.  No difference.

Openldap-2.1, with schema checking enabled, requires one and only one
structural objectclass. inetorgperson is derived from organizational
person (which is thus redundant). I would assume that you should be
deriving your eduperson from inetorgperson, and the fiuEduPerson from
eduPerson. If you aren't, you need to find some other way to have only
one structural objectclass per entry.

The other option is to disable schema checking, but that's not advisable.

It might help if you showed us the ldif for an account that you get this
error with, and the entry in the replog for the failure.

Regards,
Buchan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAB7dqrJK6UGDSBKcRAgDTAKCSdxY1RrPaQOR4IoyHRjfPqa7u2ACfYGKW
mlMgATlfccwMlxleFDXMc80=
=1V6d
-----END PGP SIGNATURE-----