On Mon, Jul 14, 2008 at 12:18, John Oliver <[EMAIL PROTECTED]> wrote:
> I have a Fedora Directory Server here providing LDAP authentication to > lab machines. I've exported the LDIFs and want to import them into an > OpenLDAP server. I'm getting: > > [EMAIL PROTECTED] ~]# slapadd -l /tmp/people.ldif > <= str2entry: str2ad(parentid): attribute type undefined > slapadd: could not parse entry (line=1321) > > Even using -v -d 9 isn't helping: > > entryid: 91 > entryd>>> dnPrettyNormal: <ou=People, dc=vcs, dc=verimatrix, dc=com> > <<< dnPrettyNormal: <ou=People,dc=vcs,dc=verimatrix,dc=com>, > <ou=people,dc=vcs,dc=verimatrix,dc=com> > <= str2entry: str2ad(parentid): attribute type undefined > slapadd: could not parse entry (line=1321) > > I'm not surprised that Netscape/Fedora DS has stuff that OpenLDAP > doesn't like. But I'm not finding any scripts to convert, or any docs > that say "If you're trying to do this, here are the lines that need to > be deleted or edited to something else". > > Does anyone know what I need to do to convert my Fedora-DS LDIF to a > format that OpenLDAP will accept? > > There are no easy ways on this one. I would do an ldapsearch to dump the records without the all the operational attributes. Then import using the ldapadd/ldapmodify command to import them. This should work, since the operation attributes are most likely what is causing the problems. There will likely be some information lost, like aci/acl information will have to be created again. It looks like it is the parentID attribute giving you trouble right now. If parentID isn't operational, then you will need to remove it, or add a schema that includes it. I believe the objectclass is userApplications. -- Henny Youngman - "I told the doctor I broke my leg in two places. He told me to quit going to those places." -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
