Gerrard Geldenhuis wrote: >>> +ERROR: There was an error processing entry cn=replica,cn="o=NetscapeRoot",cn=mapping tree,cn=config >>> +Cannot continue processing entries. >>> Error adding entry 'cn=replica,cn="o=NetscapeRoot",cn=mapping tree,cn=config'. Error: No such object >>> Error: Could not create directory server instance '389-master01'. >>> Exiting . . . >>> >>> >> This means the parent entry cn="o=NetscapeRoot",cn=mapping >> tree,cn=config does not exist - yes, this is a problem because, when >> setting up the server to be a configuration directory server, the >> o=NetscapeRoot suffix and database are added later, after the initial >> instance creation, when the ConfigFile directives are processed. I >> suppose you could add those as well - use the file >> /usr/share/dirsrv/data/template-suffix-db.ldif - make a copy - replace >> %ds_bename% with NetscapeRoot and %ds_suffix% with o=NetscapeRoot - use >> that file as the first ConfigFile directive. Then, when >> setup-ds-admin.pl tries to add those, it should be ok if they already exist. >> >> > > I used the modified template file: > dn: cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config > objectclass: top > objectclass: extensibleObject > objectclass: nsBackendInstance > nsslapd-suffix: o=NetscapeRoot > cn: NetscapeRoot > > dn: cn=encrypted attribute keys,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config > objectClass: top > objectClass: extensibleObject > cn: encrypted attributes keys > > dn: cn=encrypted attributes,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config > objectClass: top > objectClass: extensibleObject > cn: encrypted attributes > > dn: cn="o=NetscapeRoot",cn=mapping tree,cn=config > objectclass: top > objectclass: extensibleObject > objectclass: nsMappingTree > cn: o=NetscapeRoot > cn: "o=NetscapeRoot" > nsslapd-state: backend > nsslapd-backend: NetscapeRoot > > > The creation goes fine: ( I have copied the template file so I am not using the original one ) > > +Processing template-suffix-db.ldif ... > +++check_and_add_entry: Entry not found cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config error No such object > +Entry cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config is added > +++check_and_add_entry: Entry not found cn=encrypted attribute keys,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config error No such object > +Entry cn=encrypted attribute keys,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config is added > +++check_and_add_entry: Entry not found cn=encrypted attributes,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config error No such object > +Entry cn=encrypted attributes,cn=NetscapeRoot,cn=ldbm database,cn=plugins,cn=config is added > +++check_and_add_entry: Entry not found cn="o=NetscapeRoot",cn=mapping tree,cn=config error No such object > +Entry cn="o=NetscapeRoot",cn=mapping tree,cn=config is added > > > But when the script has finished running I get the following error: > > Your new DS instance '389-master01' was successfully created. > Creating the configuration directory server . . . > The suffix 'o=NetscapeRoot' already exists. Config entry DN 'cn=o\3DNetscapeRoot,cn=mapping tree,cn=config'. > > Failed to create the configuration directory server > > What is also frustrating is that the script is so quiet about why it failed. I was running setup-ds-admin with -ddd It appears that the script used to configure the admin server does net get passed the debug flags. > > Any further ideas? > I was afraid of that. The admin server part doesn't like it that NetscapeRoot already exists, and instead of just continuing, it errors and exits. If you are a perl hacker, I suppose you could hack the AdminUtil.pm and/or AdminServer.pm. > Regards > > ________________________________________________________________________ > In order to protect our email recipients, Betfair Group use SkyScan from > MessageLabs to scan all Incoming and Outgoing mail for viruses. > > ________________________________________________________________________ > -- > 389 users mailing list > 389-users@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/389-users > -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
