(ITS#5599) slapd dies on erroneous MOD input

[suomi@ayni.com]

Full_Name: suomi hasler
Version: 2.4.8-3
OS: fedora 9
URL: http://www.ayni.com/slap-prob.txt
Submission from: (NULL) (194.158.243.162)


use perl-LDAP-0.34-4.fc9.noarch to communicate with the ldap server

bind to the cn=config subtree

in this configuration, change this entry:
dn="olcDatabase={-1}frontend,cn=config"
which is an olcAccess with the original value of: 
{10}to dn.subtree="ou=postfix,dc=mydom,dc=com"  by
dn.base="cn=myname,ou=pam-ldap,dc=mydom,dc=com" write  by
dn.base="cn=postfix,ou=postfix,dc=mydom,dc=com" read  by self write  by
anonymous auth  by users none

to the following (erroneous) value (note the missing opening brace at the
start)

10}to dn.subtree="ou=postfix,dc=mydom,dc=com"  by
dn.base="cn=myname,ou=pam-ldap,dc=mydom,dc=com" write  by
dn.base="cn=postfix,ou=postfix,dc=mydom,dc=com" read  by self write  by
anonymous auth  by users none

on the interface you get:
<snip>
Modifying Attributes of DN: olcDatabase={-1}frontend,cn=config

Modify-Result-Code: 80

Modify Attribute Error: ResultCode: 80, ErrorMessage: <olcAccess> handler exited
with 1


Return Code from Modify Attribute: 80
Message: LDAP_OTHER: An unknown error has occurred

MessageID: 4
</snip>

some seconds later, slapd fails, that is, it does not reply to requests any
more, and must be stopped using kill -9 pid.
thereafter, the db is garbled but can be recovered by

slapd -d255 -uldap

after that you may start slapd using the normal procedures:
/etc/init.d/ldap start


reproduceability: always