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, 
cn=aa0-002-6-v2.u.powerset.com, ou=sv.powerset.com, o=NetscapeRoot failed, 
error: No such object
dn: cn=Fedora Directory Server, cn=Server Group, 
cn=aa0-002-6-v2.u.powerset.com, ou=sv.powerset.com, o=NetscapeRoot

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, cn=aa0-002-6-v2.u.powerset.com, ou=sv.powerset.com, o=NetscapeRoot is not there, then what is under o=NetscapeRoot? Is ou=sv.powerset.com, o=NetscapeRoot? Is cn=aa0-002-6-v2.u.powerset.com, ou=sv.powerset.com, o=NetscapeRoot?


-richard

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rich Megginson
Sent: Wednesday, January 30, 2008 12:27 PM
To: General discussion list for the Fedora Directory server project.
Subject: Re: [Fedora-directory-users] How to transfer existing server FDS

Сафонов Алексей wrote:
Greetings!

At me the infrastructure with use FDS 1.0.4 is deploymented. There was a necessity to replace a server with 
FDS. Whether I can in any way to transfer FDS on a new server with preservation of all adjustments. For 
example, make archive the catalogue /opt/fedora-fs on a "old" server. Then to install rpm 
(fedora-ds--1.0.4-1. FC6.i386.opt.rpm) on "new" server. And, at last, to unpack archive in 
/opt/fedora-fs on a "new" server.
Whether this algorithm will approach? Whether there will be problems provided 
that existing server FDS is synchronized with server ADS?

If the hostname of the old server is the same as the new server, you can just 
archive /opt/fedora-ds/admin-serv, /opt/fedora-ds/slapd-*, 
/opt/fedora-ds/clients/dsgw/context,
/opt/fedora-ds/clients/orgchart/config.txt, and unarchive them on the 
destination machine.
I Ask the help

--
Fedora-directory-users mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/fedora-directory-users




--
Fedora-directory-users mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/fedora-directory-users


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

--
Fedora-directory-users mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/fedora-directory-users

Reply via email to