On Tue, Feb 01, 2005 at 04:23:43PM -0500, Matt wrote: > The issue seems to be with the database setup.... I'm setting up my > database with the following: > > dn: dc=chilitech,dc=net > objectClass: top > objectClass: dcObject > objectClass: organization > o: chilitech.net > dc: chilitech > structuralObjectClass: organization >
Why are you using dc in the dn but then still supply a o field? Especially because you are using ou=accounts later in the dn. > dn: dc=accounts,dc=chilitech,dc=net > dc: accounts > o: accounts.chilitech.net > objectClass: top > objectClass: organization > objectClass: dcObject > Same here. > > which when added via slapadd I get: > added: "dc=chilitech,dc=net" (00000001) > added: "dc=accounts,dc=chilitech,dc=net" (00000002) > > so all is well with that.. when I try to add a user account (see > previous email for example I get:) > > User ldif is: > dn: x500uniqueIdentifier=15067, ou=accounts, dc=chilitech,dc=net This dn does not exist. A dn is like a path and there is no ou=accounts in your path. Either you use dn: x500uniqueIdentifier=15067,dc=accounts,dc=chilitech,dc=net or use some different top nodes. > mailMessageStore: ./15067/ > sn: Sanders > userPassword:: <obscured> > mail: [EMAIL PROTECTED] > deliveryMode: normal > objectClass: person > objectClass: organizationalPerson > objectClass: inetOrgPerson > objectClass: qmailUser > uid: [EMAIL PROTECTED] > x500UniqueIdentifier:: MTUwNjc= > cn: Robert Sanders > > I get: > [EMAIL PROTECTED] ~]# slapadd -v < user > slapadd: could not parse entry (line=14) > > > I used that ldif of a user above in an older version of open-ldap and > all I'm trying to do is setup another server with a newer version of > open-ldap but am having an aweful time. -- :wq Claudio
