Brian Provenzano wrote: > Looks like that presence file does exist in my old server's schema dir > "/opt/fedora-ds/slapd-ldap/config/schema/". Maybe I should remove it > from there in my source tarball and THEN rerun the migration? Yes. > > I did notice that if I rerun the migration script on the new server > (hit the same error), and then check "/etc/dirsrv/slapd-ldap/schema/" > in the newly created instance, the '"10presense.ldif" DOES exist. Right. Migration thinks it needs to add it since it is missing from the target. > > I guess maybe the correct thing to do is remove it from the old server > source and then re-run the migration(?) Any input or best course of > action would be great. Thanks again for the help. Right. > > > > On Wed, Mar 10, 2010 at 3:04 PM, Brian Provenzano <bproven@xxxxxxxxx > <mailto:bproven@xxxxxxxxx>> wrote: > > Well, I just took a look in /etc/dirsrv/schema on my new > (pre-migration snapshot) server and there is no "10presence.ldif " > file there (nothing with 'presense' at all). Maybe I need to run > the migration in order to create my instance, get the failure > again and take another look? > > > > > On Wed, Mar 10, 2010 at 2:27 PM, Rich Megginson > <rmeggins@xxxxxxxxxx <mailto:rmeggins@xxxxxxxxxx>> wrote: > > Brian Provenzano wrote: > > OK, I'll give that a try. > > > > Oh, should I just make this change and just restart the > server or > > would it be better to rerun the migration again after making > this > > change? I can start over fresh since I run this server > virtualized. I > > have a snapshot before I executed the migration script. > Better to start over fresh. > > > > BTW thanks for the quick response :) > Sure - please file a bug - this is indeed a bug. > > > > > > On Wed, Mar 10, 2010 at 2:04 PM, Rich Megginson > <rmeggins@xxxxxxxxxx <mailto:rmeggins@xxxxxxxxxx> > > <mailto:rmeggins@xxxxxxxxxx <mailto:rmeggins@xxxxxxxxxx>>> > wrote: > > > > Brian Provenzano wrote: > > > I'm hoping someone can help me with this, but I am > getting an error > > > attempting a cross migration from an old version of > FDS (FDS > > 1.0.4) on > > > CentOS 4 32bit to current 389 Directory server (via > yum repos) on > > > centOS 5.4 64bit. I used the following in order to > install 389 DS on > > > my new CentOS server 5.4 64bit : > > > > http://directory.fedoraproject.org/wiki/Download#Enterprise_Linux_5 > > > > > > I've exported my databases to LDIF as directed in the > > documentation as > > > well and am performing the migration on the new server > from a > > tarball > > > of the original install taken from the old server. > > > > > > Anyway, when I run the migration script here is the > output error I > > > get. How do I correct this (I'm no LDAP expert that > is certain)? > > > ------------- > > > # /usr/sbin/./migrate-ds-admin.pl > <http://migrate-ds-admin.pl> <http://migrate-ds-admin.pl> > > <http://migrate-ds-admin.pl> --cross > > > --oldsroot /home/brian/LDAPmigration/fedora-ds > --actualsroot > > > /opt/fedora-ds > General.ConfigDirectoryAdminPwd='mypassword' > > > Beginning migration of Directory and Administration > servers from > > > /home/brian/LDAPmigration/fedora-ds . . . > > > Beginning migration of directory server instances in > > > /home/brian/LDAPmigration/fedora-ds . . . > > > Your new DS instance 'slapd-ldap' was successfully > created. > > > Could not import the LDIF file > '/tmp/nsrootJMtOFK.ldif' for the > > > migrated database. Error: 256. Output: importing > data ... > > > [10/Mar/2010:13:12:44 -0700] dse - The entry cn=schema > in file > > > /etc/dirsrv/slapd-ldap/schema/60mozilla.ldif is > invalid, error > > code 20 > > > (Type or value exists) - attribute type nsAIMid: Does > not match the > > > OID "1.3.6.1.4.1.13769.2.4". Another attribute type is > already using > > > the name or OID > > > [10/Mar/2010:13:12:44 -0700] dse - Please edit the file to > > correct the > > > reported problems and then restart the server. > > > > > > Exiting . . . > > > Log file is '/tmp/migrateEjdYZw.log' > > > -------------- > > > > > > I'm not sure how to troubleshoot this. Any help would > be great. > > Try removing 10presence.ldif from the schema directory > (save a copy > > first though) > > > > > > Thanks brian > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------ > > > > > > -- > > > 389 users mailing list > > > 389-users@xxxxxxxxxxxxxxxxxxxxxxx > <mailto:389-users@xxxxxxxxxxxxxxxxxxxxxxx> > > <mailto:389-users@xxxxxxxxxxxxxxxxxxxxxxx > <mailto:389-users@xxxxxxxxxxxxxxxxxxxxxxx>> > > > https://admin.fedoraproject.org/mailman/listinfo/389-users > > > > -- > > 389 users mailing list > > 389-users@xxxxxxxxxxxxxxxxxxxxxxx > <mailto:389-users@xxxxxxxxxxxxxxxxxxxxxxx> > > <mailto:389-users@xxxxxxxxxxxxxxxxxxxxxxx > <mailto:389-users@xxxxxxxxxxxxxxxxxxxxxxx>> > > https://admin.fedoraproject.org/mailman/listinfo/389-users > > > > > > > ------------------------------------------------------------------------ > > > > -- > > 389 users mailing list > > 389-users@xxxxxxxxxxxxxxxxxxxxxxx > <mailto:389-users@xxxxxxxxxxxxxxxxxxxxxxx> > > https://admin.fedoraproject.org/mailman/listinfo/389-users > > -- > 389 users mailing list > 389-users@xxxxxxxxxxxxxxxxxxxxxxx > <mailto: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 -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
