Kiran, Okay so config.ldif is not for loading initial directory data. I'm automating installation of a development LDAP server so I guess I'll just load the LDIF file via ldapadd during configuration instead appending the data to config.ldif. Thank you for clearing that up for me.
V/r, Brad Crosby On Wed, Oct 30, 2013 at 1:57 AM, Kiran Ayyagari <[email protected]> wrote: > On Wed, Oct 30, 2013 at 12:58 AM, Brad Crosby Jr. > <[email protected]>wrote: > >> Hello, >> >> I'm having problems setting up some initial data in my directory via >> config.ldif. I've distilled the problem by taking an untouched 2.0.0 >> instance in Directory Studio and (while the server is stopped) adding >> the following entry to the config.ldif for the server: >> >> config.ldif should contain configuraton related data, the below entry > should > not be added to config.ldif > > dn: ou=People,dc=example,dc=com >> ou: People >> objectclass: top >> objectclass: organizationalUnit >> >> Trying to then start the server fails with the following two >> exceptions in the log (abridged): >> >> org.apache.directory.api.ldap.model.exception.LdapOtherException: >> ERR_216_ID_FOR_PARENT_NOT_FOUND Id for parent 'dc=example,dc=com' not >> found! >> Caused by: >> org.apache.directory.api.ldap.model.exception.LdapNoSuchObjectException: >> ERR_216_ID_FOR_PARENT_NOT_FOUND Id for parent 'dc=example,dc=com' not >> found! >> >> I can add the same entry manually through Directory Studio and it >> works just fine. What's going on here? Disclaimer: I'm new to LDAP in >> general, and ApacheDS in particular. >> >> this is the right way to add that > >> Thanks in advance, >> Brad Crosby >> > > > > -- > Kiran Ayyagari > http://keydap.com
