Thanks for your comments and your time. The problem is not processing Windows ldif files because I can load the basic database structure from an ldif file without any problems. I'm beginning to think it is something in the schema definitions that's the problem. OpenLDAP changed the schemas between the two versions I'm using, and I always seem to have an error on inetOrgPerson and account no matter how I use them. I've posted this question on the OpenLDAP forum, as it may be related to how I've set up the config for this particular server.
Thanks again for your help, it's most interesting to see that you can load what I can't. It points to the problem being something other than the ldif file itself. JFE. Quanah Gibson-Mount <[EMAIL PROTECTED]> 06/19/2007 12:01 PM To Jack Emmerichs <[EMAIL PROTECTED]>, [email protected] cc Subject Re: [ldap] syntax for posixAccount --On June 19, 2007 9:40:44 AM -0400 Jack Emmerichs <[EMAIL PROTECTED]> wrote: > We are upgrading from OpenLDAP 2.2.29 to the current 2.3.32. The build > seems to work, and the basic database structure seems okay and displays > The problem is that I cannot find a syntax for posixAccount entries the > LDAP will accept without throwing an error such as: > > LDAP error code 21 - objectClass: value #1 invalid per syntax > > The ldif format exported by the old version looks like this (it's a > Windows system with dummy data for Unix items uid#, gid#, homeDirectory, > etc.): > > > dn: cn=AWS User 1,ou=people, dc=my-domain,dc=com > gidNumber: 100 > userPassword:: e1NIQX1pK1BKUTdGZ24vKy94UnF0Wm0wS0JLMzRQSjA9 > uidNumber: 100 > uid: awsuser1 > objectClass: top > objectClass: account > objectClass: posixAccount > homeDirectory: notUsed > cn: AWS User 1 > > I've looked at and tried lots of examples containing from 3 to 5 > objectClass entries, but I always get the same error on some objectClass > value #. In this example, objectClass #1 is account, not posixAccount. So please confirm which objectClass is actually the problem. In any case, I can add your example entry to a database with no error. I think the key here is the fact that you mention Windows. Is the data perhaps in Windows LF format? /tmp# cat test.ldif # example.com dn: dc=example,dc=com dc: example objectClass: top objectClass: dcObject objectClass: organization o: OrgName # people, example.com dn: ou=people,dc=example,dc=com ou: people objectClass: top objectClass: organizationalUnit dn: cn=AWS User 1,ou=people, dc=example,dc=com gidNumber: 100 userPassword:: e1NIQX1pK1BKUTdGZ24vKy94UnF0Wm0wS0JLMzRQSjA9 uidNumber: 100 uid: awsuser1 objectClass: top objectClass: account objectClass: posixAccount homeDirectory: notUsed cn: AWS User 1 /tmp# slapadd -l test.ldif -f /usr/local/etc/openldap/slapd.conf.qbdb_db_open: Warning - No DB_CONFIG file found in directory /var/lib/ldap/qtest: (2) Expect poor performance for suffix dc=example,dc=com. Exited success. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration --- 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.
