I am wondering if I need to migrate my NetscapeRoot at all? Can I just
convert userRoot to LDIF run the migration and then maybe run setup script
afterwards to create the NetscapeRoot? Since I am stuck on migration and
the problem seems to be in NetscapeRoot (I'm guessing - I have no idea now
to
Additionally, in my source (from FDFS 1.0.4) NetscapeRoot.ldif (near the
beginning) I see this entry which appears to be the one choking?
# entry-id: 15
dn: cn=Tasks, cn=slapd-ldap, cn=Fedora Directory Server, cn=Server Group,
cn=l
dap.mcs.local, ou=mcs.local, o=NetscapeRoot
objectClass: top
Brian Provenzano wrote:
Thanks for the tip. I have the following in my
/var/log/dirsrv/slapd-ldap/access log:
[15/Mar/2010:10:42:44 -0600] conn=1 fd=64 slot=64 connection from
192.168.1.20 to 192.168.1.20
[15/Mar/2010:10:42:44 -0600] conn=1 op=0 BIND dn= method=128 version=3
Exist in the destination you mean? or in the source on the original FDS
1.0.4 server?
This is a fresh install of 389 for the migration and I have not run setup
(per migration docs), so I assume it does not exist yet? Should it? Should
I run setup first to create and then run migrate? I did
I ran the migrate with the debug flag as requested. It spits out about
2000+ lines of debug. Is this list OK with me posting/emailing that many
lines? I can gladly post it.
On Mon, Mar 15, 2010 at 1:21 PM, Rich Megginson rmegg...@redhat.com wrote:
Brian Provenzano wrote:
To answer your
Brian Provenzano wrote:
I ran the migrate with the debug flag as requested. It spits out
about 2000+ lines of debug. Is this list OK with me posting/emailing
that many lines? I can gladly post it.
Just send it to me directly.
On Mon, Mar 15, 2010 at 1:21 PM, Rich Megginson
That definitely gets me a bit farther along. I replaced the occurrences in
the NetscapeRoot.ldif and reran the process, but I hit another error. Looks
there is another location (another ldif?) that is being read in for
migration and it has a bad ref to the 'Fedora' cn as well. The fun never
Brian Provenzano wrote:
That definitely gets me a bit farther along. I replaced the
occurrences in the NetscapeRoot.ldif and reran the process, but I hit
another error. Looks there is another location (another ldif?) that
is being read in for migration and it has a bad ref to the 'Fedora'
Brian Provenzano wrote:
My destination server's /etc/dirsrv/admin-serv/local.conf is empty,
Right.
so I'll check the source server's
/opt/fedora-ds/admin-serv/config and /opt/fedora-ds/shared/config
make the necessary changes and try the migration again.
Right.
On Mon, Mar 15, 2010 at 4:57
Rich,
We finally got it (or should I say you did). I updated the following to
change references to Fedora to 389 and the migration completed
successfully:
/tmp/fedora-ds/admin-serv/config/adm.conf
/tmp/fedora-ds/admin-serv/config/local.conf
Now, to confirm everything looks OK after the
Brian Provenzano wrote:
Rich,
We finally got it (or should I say you did). I updated the following
to change references to Fedora to 389 and the migration completed
successfully:
/tmp/fedora-ds/admin-serv/config/adm.conf
/tmp/fedora-ds/admin-serv/config/local.conf
Now, to confirm
I'm still on the road to trying to migrate from FDS 1.0.4 to 389 DS 1.2.5.
Thanks to Rich's help yesterday in a previous thread (Cross Migration
Problem From FDS 1.0.x to 386 Directory Server) I was able to fix an import
issue with an existing ldif schema (presense.ldif).
Anyway, I am now running
12 matches
Mail list logo
