----- Original Message -----
Sent: Wednesday, March 06, 2002 10:05
AM
Subject: RE: parent does not exist
You must add the parent before you add a child. This is what I
meant by a "working" LDIF file. You can figure out what the parent is by
looking at the dn.
ldapmodify iterates through the LDIF from top to bottom, so
your LDIF is out of order. Rearrange the entries in your LDIF as
follows:
dn: o=University of Michigan,c=US
dn:
ou=People,o=University of Michigan,c=US
dn:
ou=Groups,o=University of Michigan,c=US
dn:
cn=Manager,o=University of Michigan,c=US
dn: ou=Alumni
Association, ou=People, o=University of Michigan, c=US
dn: cn=All Staff,ou=Groups,o=University of Michigan,c=US
dn: cn=Bjorn Jensen,ou=Information Technology
Division,ou=People,o=Universi
ty of
Michigan,c=US
etc.
Note how the parent entry "ou=Groups..." is before the
specific group "cn=All Staff..."
-----Original Message-----
From: Leila
Lappin [mailto:galaxylappin@comcast.net]
Sent: Wednesday, March 06, 2002 4:25 PM
To: Raed Nashef
Cc: oberwetter, josh;
OpenLDAP-software@OpenLDAP.org;
owner-openldap-software@OpenLDAP.org
Subject:
Re: parent does not exist
Hi Raed,
I added the following based on your suggestion I
received. dn: ou=People
and o=University were
already defined in the ldif file. It still gives me
the same error. I've attached the complete ldif file for anyone
who's
interested to take a look at it. As I said
the files came with the
downloaded openldap-2.0.11
version. May be I'll just go to my local
bookstore and look for a book on ldap. (smiley here)
thanks again
<<<<<<<<<
>>>>>>>>>>>>>>>
dn: ou=Groups,o=University of Michigan,c=US
ou: Groups
objectclass:
organizationalUnit
<<<<<<<<>>>>>>>>>>>>>>>>>>
dn: ou=People and o=University as defined in the
file
<<<<<
<<<<<>>>>>>>
>>>>>>>>>
dn: ou=People, o=University of Michigan, c=US
objectclass: top
objectclass:
organizationalUnit
ou: People
dn: o=University of Michigan, c=US
objectclass: top
objectclass:
organization
objectclass: domainRelatedObject
l: Ann Arbor, Michigan
st:
Michigan
o: University of Michigan
o: UMICH
o: UM
o:
U-M
o: U of M
description: The
University of Michigan at Ann Arbor
postaladdress:
University of Michigan $ 535 W. William St. $ Ann Arbor, MI
481
09 $ US
telephonenumber: +1 313 764-1817
associateddomain: umich.edu
<<<<<<
>>>>>>>>>>>>>
----- Original Message -----
From:
"Raed Nashef" <rnashef@baxglobal.com>
To: "Leila
Lappin" <galaxylappin@comcast.net>
Cc:
"oberwetter, josh" <joberwetter@grownetwork.com>;
<OpenLDAP-software@OpenLDAP.org>;
<owner-openldap-software@OpenLDAP.org>
Sent:
Wednesday, March 06, 2002 9:29 AM
Subject: Re: parent
does not exist
> Leila,
>
> In your LDIF file I do not see where you're defining your
organization,
> and "organizationalUnit"s!!!
> I'm also new to LDAP, but I believe that you will need
to first define
your
> tree
structure before loading the ldif file that you show in your email.
> Something like the following first needs to be
done:
>
> dn:
o=University of Michigan, c=US
> o:
University of Michigan
> objectclass: top
> objectclass: organization
>
> dn: ou=Groups,o=University of
Michigan,c=US
> ou: Groups
> objectclass: organizationalUnit
>
> dn: ou=People,o=University of
Michigan,c=US
> ou: People
> objectclass: organizationalUnit
>
> dn: ou=Alumni
Association,ou=People,o=University of Michigan,c=US
> ou: Alumni Association
>
objectclass: organizationalUnit
>
>
> Once you load the above ldif, your
tree hierarchy is defined and you'll be
> able to
load the ldif file you mention in your email.
>
> Regards
>
> Raed Nashef
> Consultant Analyst
> Network Planning
Group
> BAX Global, Inc.
> Tel: 949.752.1212 x.2672
>
Email: rnashef@baxglobal.com
> http://www.baxglobal.com
>
>
>
>
Leila Lappin
>
<galaxylappin@comcast.n
To: "oberwetter,
josh"
<joberwetter@grownetwork.com>
>
et>
cc:
OpenLDAP-software@OpenLDAP.org
>
Subject: Re:
parent does not exist
>
Sent by:
>
owner-openldap-software
>
@OpenLDAP.org
>
>
>
03/05/2002 10:05 PM
>
>
>
>
>
>
>
>
> Hi
Josh,
>
> Thank you for
your answers. I didn't see a 'Michigan list', under the
> mailing list section. There's a 'general' list but it seems
to be
> closed.
>
> In regard to my question as you suggested I'm sending
the slapd.conf and
a
> part of the ldif file because it's very long.
>
>
<<<<<<<<<<<<< slapd.conf
>>>>>>>>>>
>
> # $OpenLDAP$
> #
> # stand-alone slapd config -- for testing
> # with indexing
> #
> include d:/openLDAP/schema/core.schema
> include d:/openLDAP/schema/cosine.schema
> include
d:/openLDAP/schema/inetorgperson.schema
>
schemacheck on
> pidfile
d:/openLDAP/test-db/slapd.pid
>
argsfile d:/openLDAP/test-db/slapd.args
>
>
#######################################################################
> # ldbm database definitions
>
#######################################################################
>
> database ldbm
> suffix "o=University of Michigan, c=US"
> directory d:/openLDAP/test-db
> rootdn "cn=Manager, o=University of Michigan,
c=US"
> rootpw secret
>
index objectclass eq
> index uid pres,eq,sub
> index cn,sn pres,eq,sub,subany
> dbnosync
> dbnolocking
>
>
>
<<<<<<<<<<<<<<<<<<
ldif file (partial) >>>>>>
>
> dn: cn=All
Staff,ou=Groups,o=University of Michigan,c=US
> member: cn=Manager, o=University of Michigan, c=US
> member: cn=Barbara Jensen, ou=Information
Technology Division, ou=People,
> o=Un
> iversity of Michigan, c=US
>
member: cn=Jane Doe, ou=Alumni Association, ou=People, o=University
of
> Michiga
> n,
c=US
> member: cn=John Doe, ou=Information
Technology Division, ou=People,
> o=Universi
> ty of Michigan, c=US
>
member: cn=Mark Elliot, ou=Alumni Association, ou=People, o=University
of
> Mich
> igan,
c=US
> member: cn=James A Jones 1, ou=Alumni
Association, ou=People,
o=University
> of
> Michigan, c=US
> member: cn=James A Jones 2, ou=Information Technology
Division,
ou=People,
>
o=U
> niversity of Michigan, c=US
> member: cn=Jennifer Smith, ou=Alumni Association,
ou=People, o=University
> of M
> ichigan, c=US
> member:
cn=Dorothy Stevens, ou=Alumni Association, ou=People,
o=University
> of
> Michigan, c=US
> member:
cn=Ursula Hampster, ou=Alumni Association, ou=People,
o=University
> of
> Michigan, c=US
> member: cn=Bjorn
Jensen, ou=Information Technology Division, ou=People,
> o=Univ
> ersity of Michigan,
c=US
> owner: cn=Manager, o=University of Michigan,
c=US
> cn: All Staff
> description: Everyone in the sample data
> objectclass: groupofnames
>
>
> -----
Original Message -----
> From: oberwetter,
josh
> To: 'Leila Lappin'
> Cc: OpenLDAP-software@OpenLDAP.org
>
Sent: Tuesday, March 05, 2002 9:21 AM
>
Subject: RE: parent does not exist
>
> See comments below.
>
-----Original Message-----
> From: Leila
Lappin [mailto:galaxylappin@comcast.net]
> Sent: Tuesday, March 05, 2002 3:28 PM
> To: OpenLDAP-software@OpenLDAP.org
> Subject: Fw: parent does not exist
>
>
>
> ----- Original Message -----
> From: Leila Lappin
> To:
openldap-devel@OpenLDAP.org
> Sent: Tuesday, March
05, 2002 11:12 AM
> Subject: parent does not
exist
>
> Hello
all,
>
> I'm new to
openLDAP (one week) and since I downloaded and installed the
> package on my NT machine I have been reading a lot
of the documents on
> openldap site. I'm running my
second test that came with the package and
>
have some question. If anyone could help me with the answers or where
to
> find comprehensive source of information
(a book for people new to the
> subject) I would
greately appreciate.
> [oberwetter, josh] For
a general intro to LDAP, I read "Understanding and
> Deploying LDAP Directory Services" by Timothy Howes et al,
and I often
> refer to the various RFCs. But you
should send general LDAP questions to
> the
Michigan list.
> Answers to OpenLDAP
questions can be found in the mailing list archives,
> the Admin guide, the FAQ, and whatever (mis)information is
lying around
> the web. There is no
comprehensive source of info for OpenLDAP, unless
>
you get to know the code :-)
>
> I'm working with openldap2.0.11. I am trying to
run one of the test under
>
(\openldap-2.0.11\tests\data\ ) and get the following error on
the
client:
>
> adding new entry "cn=All
Staff,ou=Groups,o=University of
>
Michigan,c=US"
> ldap_add: No such
object
> ldif_record() = 32
> [oberwetter, josh] Perhaps somebody else knows exactly what
tests you're
> running. The first tests that
I ran are described here
> http://www.openldap.org/doc/admin/quickstart.html
> Send us the contents of d:\openLDAP\test.ldif up
to & including the entry
> that fails
(cn=All Staff,...), so that people who aren't familiar with
the
> specific test can help debug this
common error.
> Or, you might be able to help
yourself using the FAQ
> http://www.openldap.org/faq/data/cache/343.html
>
> I am issuing the
command:
>
> ldapmodify
-a -x -v -D "cn=Manager, o=University of Michigan, c=US" -W
> -f d:\openLDAP\test.ldif
>
> Chasing through the diagnostics it
seems an attempt is made to add cn=All
>
since it's the parent level of cn=Manager. Then why am I getting
>
> parent does not
exist
>
> on the server
side?
>
> thanks in
advance for any help
>
>
>