Re: [389-users] Migration Issues With Admin Server LDIF Import

2010-03-15 Thread Brian Provenzano
My destination server's "/etc/dirsrv/admin-serv/local.conf" is empty, 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. On Mon, Mar 15, 2010 at 4:57 PM, Rich Megginson wrote: > Brian Pro

Re: [389-users] Migration Issues With Admin Server LDIF Import

2010-03-15 Thread Rich Megginson
Brian Provenzano wrote: > To answer your other questions: > > > Does the entry o=NetscapeRoot exist? > > Does ou=mcs.local, o=NetscapeRoot exist? > > Does cn=ldap.mcs.local, ou=mcs.local, o=NetscapeRoot exist? > Yes. All of those exist in the original (source) server's database > (o=N

Re: [389-users] Migration Issues With Admin Server LDIF Import

2010-03-15 Thread Brian Provenzano
To answer your other questions: > Does the entry o=NetscapeRoot exist? > Does ou=mcs.local, o=NetscapeRoot exist? > Does cn=ldap.mcs.local, ou=mcs.local, o=NetscapeRoot exist? Yes. All of those exist in the original (source) server's database (o=NetscapeRoot, etc). I can see these ea

Re: [389-users] Migration Issues With Admin Server LDIF Import

2010-03-15 Thread Brian Provenzano
The FQDN look the fine to me. I tried to be very careful about this pitfall. NEW server: # hostname --fqdn ldap.mcs.local OLD server: #hostname --fqdn ldap.mcs.local On Mon, Mar 15, 2010 at 12:38 PM, Rich Megginson wrote: > Brian Provenzano wrote: > > Exist in the destination you mean? > If it

Re: [389-users] Migration Issues With Admin Server LDIF Import

2010-03-15 Thread Rich Megginson
Brian Provenzano wrote: > Exist in the destination you mean? If it was migrated at all, yes. > or in the source on the original FDS 1.0.4 server? Yes, if the migration did not get to that point yet. > > This is a fresh install of 389 for the migration and I have not run > setup (per migration doc

Re: [389-users] Migration Issues With Admin Server LDIF Import

2010-03-15 Thread Brian Provenzano
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 [15/Mar/2010:10:42:44 -0600] conn=1 op=0 RE

Re: [389-users] Migration Issues With Admin Server LDIF Import

2010-03-15 Thread Rich Megginson
Brian Provenzano wrote: > 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 (presen