[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: [JunkMail] LDAP Server bug?



No bug, works as designed.

As documented here
http://www.openldap.org/doc/admin24/slapdconf2.html#cn=schema
the contents of "cn=schema,cn=config" are hardcoded. That means you can't modify them. And it looks like you're just trying to add a value that already exists anyway, so the operation you're doing is totally pointless.


openldap wrote:
Hi
i tried the following:

[myuser@deskhost ~]$ ldapmodify -H "ldaps://ldaphost.mydom.com" -x
-D"cn=config" -W -f klein.ldapmodify.ldif
Enter LDAP Password:
modifying entry "cn=schema,cn=config"
ldapmodify: Internal (implementation specific) error (80)
          additional info:<olcAttributeTypes>  handler exited with 1

[myuser@deskhost ~]$

and the LDAP log says:

Feb 11 11:32:11 ldaphost slapd[8575]: conn=75 fd=31 ACCEPT from
IP=xx.xx.xx.xx:60593 (IP=0.0.0.0
:636)
Feb 11 11:32:12 ldaphost slapd[8575]: conn=75 fd=31 TLS established
tls_ssf=256 ssf=256
Feb 11 11:32:12 ldaphost slapd[8575]: conn=75 op=0 BIND dn="cn=config"
method=128
Feb 11 11:32:12 ldaphost slapd[8575]: conn=75 op=0 BIND dn="cn=config"
mech=SIMPLE ssf=0
Feb 11 11:32:12 ldaphost slapd[8575]: conn=75 op=0 RESULT tag=97 err=0 text=
Feb 11 11:32:12 ldaphost slapd[8575]: conn=75 op=1 MOD
dn="cn=schema,cn=config"
Feb 11 11:32:12 ldaphost slapd[8575]: conn=75 op=1 MOD
attr=olcAttributeTypes
Feb 11 11:32:12 ldaphost slapd[8575]: conn=75 op=1 RESULT tag=103 err=80
text=<olcAttributeTypes>  handler exited with 1
Feb 11 11:32:12 ldaphost slapd[8575]: conn=75 op=2 UNBIND
Feb 11 11:32:12 ldaphost slapd[8575]: conn=75 fd=31 closed



the ldif file:

dn: cn=schema,cn=config
changetype: modify
add: olcAttributeTypes
olcAttributeTypes: ( 2.5.4.0 NAME 'olcObjectClasses' DESC 'RFC2256
object classes of the entity' EQUALITY objectIdentifierMatch SYNTAX
1.3.6.1.4.1.1466.115.121.1.38 )

what can i do now? does this say "wait for version 2.4.x of openldap"?

i need these attributes and obejctclasses on an LDAP installation for a
customer.

suomi


openldap wrote: > Hi every > > OpenBSD myserver.mydomain.tld 4.2 GENERIC#375 i386 > > openldap-server-2.3.33p1-bdb > > a week ago, i introduced a new schema, the horde.schema, adding it to > the new cn=config subtree using ldapadd...

Hm, that's a bug that ldapadd succeeded. olcIncludeFile objects are only
supposed to be in the cn=config tree when it was converted from a slapd.conf
file. For a pure cn=config installation, you should be creating a olcSchema
entry instead.



--
  -- Howard Chu
  Chief Architect, Symas Corp.  http://www.symas.com
  Director, Highland Sun        http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP     http://www.openldap.org/project/