Hi, > This message was off-topic on openldap-software and they suggested I > submit this question here instead: > > Trying to re-insert an object into the directory using slapadd -c -l > foo.ldif. This ldif was generated via slapcat -l foo.ldif. > > When I try to re-add the object, I get: > > slapadd: dn="cn=uidPool,dc=ebit,dc=ca" (line=319): (65) attribute > 'cn' not allowed
ObjectClass is organizationalUnit, try to put dn: ou=uidPool,dc=ebit,dc=ca in ldif. > > The object is below. > > dn: cn=uidPool,dc=ebit,dc=ca > objectClass: organizationalUnit > objectClass: top > cn: uidPool > entryUUID: eae956da-b251-1028-9b7e-f0d7ce1991b0 > creatorsName: cn=Manager,dc=ebit,dc=ca > createTimestamp: 20041014172624Z > ou: 10010 > entryCSN: 20041014172903Z#000001#00#000000 > modifiersName: cn=Manager,dc=ebit,dc=ca > modifyTimestamp: 20041014172903Z > > I don't understand why CN isn't allowed. From what I have read, I > can't seem to find any documentation suggesting that cn is dependent > on any specific objectClass, rather it's requisite to a DN. > > This object was initially created on OpenLDAP 2.2.15 and was re-added > using the above command on a few occasions without issue. Suddenly > in OpenLDAP 2.2.29 this isn't the case. I checked the release notes > and the CVS diffs between 2.2.15 and 2.2.29 to see if I could get > some indication of what changed, if anything but I'm not having much > luck. > > Any ideas? --- You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe send email to [EMAIL PROTECTED] with the word UNSUBSCRIBE as the SUBJECT of the message.
