[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: qmailControl.schema
Hi all,
I've upgraded to 2.1.17, which solved the problem, had nothing to do with missing structuralObjectclasses, db versions whatsoever, just a bug in 2.1.16
Be well,
Jeroen.
On Wed, 23 Apr 2003 15:48:26 +0200
Luca Scamoni <luca.scamoni@sys-net.it> wrote:
> Please take a look at the faq:
>
> http://www.openldap.org/faq/data/cache/807.html
>
> AFAIK, OpenLDAP 2.1.x requires BerkeleyDB-4.1 (so it shouldn't work with
> previous releases).
> The fact you could add your ldif through slapadd is due to the lack of
> schema checking that the server normally performs when up and running.
>
> Jeroen Vriesman wrote:
>
> >Hi, if you see my previous mail, you can see that I also have problems with 'structural objectclass', for as far as I know, there are more people with these kind of problems with 2.1.16, I compiled it with db3 in stead of db4, what dbd version do you use?
> >
> >At the moment I'm just trying to make a 2.1.17 rpm of openldap, see if that helps.
> >
> >I can add ldif files by stopping the ldap server and using slapadd, and then it works fine.
> >
> >No clue yet, I tried to add the structural objectClass in local.schema, but that was a bad idea.
> >
> >Any further ideas?
> >
> >
> >On Wed, 23 Apr 2003 14:10:00 +0200
> >Michael Dosser <mic@nethack.at> wrote:
> >
> >
> >
> >>Hello dear list members, hello turbo,
> >>
> >>we have a small problem at our site. We are running OpenLDAP 2.1.16 on
> >>FreeBSD 4.8-RELEASE. We want to use Qmail with the LDAP- and the
> >>qmailControl patch. I added the two schemas (qmail.schema and
> >>qmailControl.schema) and they are being included (this show slapd
> >>running with -d 255).
> >>
> >>Problem description:
> >>====================
> >>
> >>$ cat qmailControl.ldif
> >>dn: ou=users, dc=testdomain, dc=at
> >>objectclass: top
> >>objectclass: organizationalUnit
> >>ou: users
> >>
> >>dn: cn=mail.testdomain.at, ou=QmailLDAP, dc=testdomain, dc=at
> >>objectclass: top
> >>objectclass: qmailControl
> >>cn: mail.testdomain.at
> >>locals: localhost
> >>locals: testdomain.at
> >>ldapbasedn: dc=testdomain,dc=at
> >>ldapuid: 3000
> >>ldapgid: 3000
> >>ldapdefaultquota: 10000
> >>ldapMessageStore: /var/qmail/ustorage
> >>$ ldapadd -h localhost -x -D "cn=Manager,dc=testdomain,dc=at" \
> >>
> >>
> >>>-W -f qmailControl.ldif
> >>>
> >>>
> >>Enter LDAP Password:
> >>
> >>Gives me the error:
> >>===================
> >>adding new entry "cn=mail.testdomain.at, ou=QmailLDAP, dc=testdomain, dc=at"
> >>ldapadd: update failed: cn=mail.testdomain.at, ou=QmailLDAP, dc=testdomain, dc=at
> >>ldap_add: Object class violation (65)
> >> additional info: no structural object class provided
> >>
> >>This worked with OpenLDAP 2.0.x - is there anything wrong with
> >>qmailControl.schema? Because if I add to ``dn: cn=mail.testdomain.at,
> >>ou=QmailLDAP, dc=testdomain, dc=at'':
> >>
> >>objectclass: person
> >>sn: blabla
> >>
> >>everything works.
> >>
> >>My qmailControl.schema is located here:
> >>http://daemon.nethack.at/~mic/qmailControl.schema
> >>
> >>This file is a result of the patching with qmail-ldap-control_20030306.gz
> >>from http://qmail.bayour.com/patches_ldap/
> >>
> >>thank you for helping,
> >>mic
> >>
> >>--
> >><Insert your favourite quote here.>
> >>
> >>
>
>
>