[Date Prev][Date Next]
Re: Dumb(?) schema problem
You didn't include a sample entry, but based on the DN starting with
"mail=", I'm assuming that the second entry you added was of type
Note that your schema defines that objectclass as being auxiliary. An
entry needs to have at least one structural objectclass and that's why
you got the error you did. I'm assuming that JammMailAccount is a local
schema addition and that perhaps you intend the objectclass to be
structural instead. If not, you'll have to make the entry a member of
multiple classes, with one of them being structural.
On Wednesday, December 4, 2002, at 05:56 PM, Keith T. Garner wrote:
I'm writing an application that uses its own schema to store some
data. With OpenLDAP 2.0.x everything was smooth sailing. With
OpenLDAP 2.1.x, I'm getting an error with the one structural object
I've created. Looking in gq it appears to be structural as far as
openldap is concerned, but once I try to add something to do, it
From my attempts:
Dec 4 17:52:47 zorak slapd: conn=13 op=12 ADD
Dec 4 17:52:47 zorak slapd: conn=13 op=12 RESULT tag=105 err=0
Dec 4 17:52:47 zorak slapd: conn=13 op=13 ADD
Dec 4 17:52:47 zorak slapd: conn=13 op=13 RESULT tag=105 err=65
text=no structural object classes provided
Here's what JVM/JammVirualDomain looks like:
objectclass ( 22.214.171.124.4.1.124126.96.36.199 NAME 'JammVirtualDomain'
SUP top STRUCTURAL
DESC 'Virtual Domain entry to be used with postfix
MUST ( jvd $ accountActive $ lastChange $ delete $
MAY ( postfixTransport $ description ) )
Here's what the JammMailAccount object (that is trying to be added)
objectclass ( 188.8.131.52.4.1.124184.108.40.206 NAME 'JammMailAlias' SUP top
DESC 'Mail aliasing/forwarding entry'
MUST ( mail $ maildrop $ accountActive $ lastChange )
MAY ( mailsource $ cn $ description $ userPassword ) )
Is there anything really obvious that I'm missing?
Keith T. Garner
The whole problem with the world is that fools and fanatics are
certain of themselves, and wiser people so full of doubts.