Yes, ou=sv.powerset.com,o=netscaperoot exists. Underneath it are other existing 1.04
servers for that administration domain. The script isn't creating
cn=aa0-002-6-v2.u.powerset.com,ou=sv.powerset.com,o=NetscapeRoot (or anything below that)
before trying to create the entry I listed below.
[mailto:firstname.lastname@example.org] On Behalf Of Rich Megginson
Sent: Wednesday, January 30, 2008 2:27 PM
To: General discussion list for the Fedora Directory server project.
Subject: Re: [Fedora-directory-users] How to transfer existing server FDS
Richard Hesse wrote:
It pretty much confirms what we speculated; the script isn't
checking for, nor creating the parent objects before trying to create the children:
+++check_and_add_entry: Entry not found cn=Fedora Directory Server,
+++cn=Server Group, cn=aa0-002-6-v2.u.powerset.com
+++ou=sv.powerset.com, o=NetscapeRoot error No such object
+ERROR: adding an entry cn=Fedora Directory Server, cn=Server Group,
+failed, error: No such object
dn: cn=Fedora Directory Server, cn=Server Group,
That's the first operation after adding the SIE ACI's and a few monitor entries.
Look at 10dsdata.ldif.tmpl and you'll see what we're talking about. It looks like
this script and template were never tested in a clean build environment. I'm ok
correcting that template file as long as I'm putting the right information in. Should
I use the existing 1.04 entries as a guideline?
Well, yes, but I'm curious - if cn=Fedora Directory Server, cn=Server Group,
, o=NetscapeRoot is not there, then what
is under o=NetscapeRoot? Is ou=sv.powerset.com
, o=NetscapeRoot? Is