The debug in Openldap 2.3.19:
dnPrettyNormal: <cn=schema,cn=config>
=> ldap_bv2dn(cn=schema,cn=config,0) <= ldap_bv2dn(cn=schema,cn=config)=0 => ldap_dn2bv(272) <= ldap_dn2bv(cn=schema,cn=config)=0 => ldap_dn2bv(272) <= ldap_dn2bv(cn=schema,cn=config)=0 <<< dnPrettyNormal: <cn=schema,cn=config>, <cn=schema,cn=config> modifications: add: olcAttributeTypes one value, length 141 conn=0 op=1 MOD dn="cn=schema,cn=config" conn=0 op=1 MOD attr=olcAttributeTypes oc_check_required entry (cn=schema,cn=config), objectClass "olcSchemaConfig" oc_check_allowed type "objectClass" oc_check_allowed type "cn" oc_check_allowed type "olcObjectIdentifier" oc_check_allowed type "olcAttributeTypes" oc_check_allowed type "olcObjectClasses" oc_check_allowed type "structuralObjectClass" oc_check_allowed type "entryUUID" oc_check_allowed type "creatorsName" oc_check_allowed type "createTimestamp" oc_check_allowed type "entryCSN" oc_check_allowed type "modifiersName" oc_check_allowed type "modifyTimestamp" slapd: line 0: Unexpected token before SYNTAX 1.3.6.1.4.1.1466.115.121.1.15SIN GLE-VALUE ) AttributeTypeDescription = "(" whsp numericoid whsp ; AttributeType identifier [ "NAME" qdescrs ] ; name used in AttributeType [ "DESC" qdstring ] ; description [ "OBSOLETE" whsp ] [ "SUP" woid ] ; derived from this other ; AttributeType [ "EQUALITY" woid ] ; Matching Rule name [ "ORDERING" woid ] ; Matching Rule name [ "SUBSTR" woid ] ; Matching Rule name [ "SYNTAX" whsp noidlen whsp ] ; see section 4.3 [ "SINGLE-VALUE" whsp ] ; default multi-valued [ "COLLECTIVE" whsp ] ; default not collective [ "NO-USER-MODIFICATION" whsp ]; default user modifiable [ "USAGE" whsp AttributeUsage ]; default userApplications ; userApplications ; directoryOperation ; distributedOperation ; dSAOperation whsp ")" olcAttributeTypes: value #-1: <olcAttributeTypes> handler exited with 1! send_ldap_result: conn=0 op=1 p=3 send_ldap_result: err=80 matched="" text="<olcAttributeTypes> handler exited wit h 1" send_ldap_response: msgid=2 tag=103 err=80 ber_flush: 55 bytes to sd 12 <olcAttributeTypes > handler exited with 1 ldap_write: want=55, written=55 0000: 30 35 02 01 02 67 30 0a 01 50 04 00 04 29 3c 6f 05...g0..P...)<o
0010: 6c 63 41 74 74 72 69 62 75 74 65 54 79 70 65 73 lcAttributeTypes 0020: 3e 20 68 61 6e 64 6c 65 72 20 65 78 69 74 65 64 > handler exited 0030: 20 77 69 74 68 20 31 with 1 conn=0 op=1 RESULT tag=103 err=80 text=<olcAttributeTypes> handler exited with 1 daemon: activity on 1 descriptor daemon: activity on: 12r daemon: read active on 12 connection_get(12) connection_get(12): got connid=0
When the new attribute is add, is being added a value "1" in the end of the olcAttributeType, for example, olcAttributeType1. But I do not know because.
2007/6/11, Quanah Gibson-Mount quanah@zimbra.com:
--On Monday, June 11, 2007 6:35 AM +0200 Dieter Kluenter dieter@dkluenter.de wrote:
"Eugenia Candida Oliveira de Moura" < eugeniacandida@gmail.com> writes:
Hi,
I'm using openldap 2.3.19 and when I try to add to a new attribute in the entry cn= schema,cn=config I have the following error: <olcAttributeTypes> handler exited with 1
Why this error occurs? Some ideia?
Could you please be a bit more verbose on the error? Something like debugging -d-1 would probabely be of help.
And get the debug info from a recent version of OpenLDAP. 2.3.19 is quite old.
--Quanah
-- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc
Zimbra :: the leader in open source messaging and collaboration
--On Monday, June 11, 2007 12:03 PM -0300 Eugenia Candida Oliveira de Moura eugeniacandida@gmail.com wrote:
The debug in Openldap 2.3.19:
Apparently you missed the part where I said UPGRADE. Don't use 2.3.19.
And, go read what Howard wrote.
Finally:
1.3.6.1.4.1.1466.115.121.1.15 SIN GLE-VALUE )
The word is "SINGLE-VALUE" not "SIN GLE-VALUE"
not surprised it is having a parsing problem. Hope that helps. :)
--Quanah
-- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
openldap-software@openldap.org