[Date Prev][Date Next]
Re: No such object (32) ..., again
In your slapd.conf you have suffix = "dc=mydomain.com", but you're
adding dn's like "cn=Foo Bar, dc=mydomain, dc=com". I think they
have to be the same. Why don't you try modifying your slapd.conf
suffix = "dc=mydomain, dc=com"
rootdn = "cn=root, dc=mydomain, dc=com"
and then try adding only the com
if that works then try adding the dc=mydomain and finally try adding
On Thursday, November 21, 2002, at 12:50 PM, Eigil Hysvær wrote:
I don't know if you have gotten this answer before, if so I apologize.
No apologizes - thanks for trying to help me out.
Have you created the dc=mydomain and dc=com objects?
if not, you should create them *before* adding entries as children to
dn: dc=mydomain, dc=com
Unfortunately I got the same error again (No such object).
I also tried various variants with no success.
In the end I simplified the 'suffix' in slapd.conf to be
just 'mydomain.com' - then I received another error message:
Object class violation (65)
Here's what I have:
---- Shell ----
[root@ehy01 tmp]# /usr/local/bin/ldapadd -x -w secret -D
"cn=root,dc=mydomain.com" -v < ldap-roots
ldap_initialize( <DEFAULT> )
adding new entry "dc=mydomain.com"
ldapadd: update failed: dc=mydomain.com
ldap_add: Object class violation (65)
additional info: no structural object classes provided
---- Content of 'man ldap_error': ----
An object class violation occurred (e.g., a "must"
attribute was missing from the entry).
---- My comment: ---
core.shema says dc is a MUST. Below you can see that dc is present.
---- Content of ldap-roots: ----
---- Content of slapd.conf: ----
index objectClass eq
---- Content of core.shema ('dcObject' definition)
objectclass ( 126.96.36.199.4.1.1466.344 NAME 'dcObject'
DESC 'RFC2247: domain component object'
SUP top AUXILIARY MUST dc )
pgp fingerprint: BC64 2E7A CAEF 39E1 9544 80CA F7D5 784D FB46 16C1