Hi, I'm running slapd 2.4.9 on Solaris10. I searched with no result: does anyone know if there is a bug on 2.4.9 regarding password changes? I'd like to know if newer releases have bug fixes specifically for this issue
This is what happened to me. I have a client performing many password changes, which usually results in my logs like this: ... Feb 19 12:17:33 db1 slapd[49]: [ID 848112 local4.debug] conn=591 fd=22 ACCEPT from IP=192.168.2.253:49108 (IP=0.0.0.0:12312) Feb 19 12:17:33 db1 slapd[49]: [ID 215403 local4.debug] conn=591 op=0 BIND dn="uid=mario.rossi@unipd.it,ou=people,dc=unipd,dc=it" method=128 Feb 19 12:17:33 db1 slapd[49]: [ID 600343 local4.debug] conn=591 op=0 BIND dn="uid=mario.rossi@unipd.it,ou=people,dc=unipd,dc=it" mech=SIMPLE ssf=0 Feb 19 12:17:33 db1 slapd[49]: [ID 588225 local4.debug] conn=591 op=0 RESULT tag=97 err=0 text= Feb 19 12:17:33 db1 slapd[49]: [ID 270379 local4.debug] conn=591 op=1 EXT oid=1.3.6.1.4.1.4203.1.11.1 Feb 19 12:17:33 db1 slapd[49]: [ID 461300 local4.debug] conn=591 op=1 PASSMOD new Feb 19 12:17:33 db1 slapd[49]: [ID 875301 local4.debug] conn=591 op=1 RESULT oid= err=0 text= Feb 19 12:17:33 db1 slapd[49]: [ID 218904 local4.debug] conn=591 op=2 UNBIND Feb 19 12:17:33 db1 slapd[49]: [ID 952275 local4.debug] conn=591 fd=22 closed ... Always went fine, but yesterday this happened: ... Feb 18 22:45:41 db1 slapd[21872]: [ID 848112 local4.debug] conn=3186 fd=22 ACCEPT from IP=192.168.2.253:49820 (IP=0.0.0.0:12312) Feb 18 22:45:41 db1 slapd[21872]: [ID 215403 local4.debug] conn=3186 op=0 BIND dn="uid=maria.verdi@unipd.it,ou=people,dc=unipd,dc=it" method=128 Feb 18 22:45:41 db1 slapd[21872]: [ID 600343 local4.debug] conn=3186 op=0 BIND dn="uid=maria.verdi@unipd.it,ou=people,dc=unipd,dc=it" mech=SIMPLE ss f=0 Feb 18 22:45:41 db1 slapd[21872]: [ID 588225 local4.debug] conn=3186 op=0 RESULT tag=97 err=0 text= Feb 18 22:45:41 db1 slapd[21872]: [ID 270379 local4.debug] conn=3186 op=1 EXT oid=1.3.6.1.4.1.4203.1.11.1 Feb 18 22:45:41 db1 slapd[21872]: [ID 461300 local4.debug] conn=3186 op=1 PASSMOD new ... that is, no "RESULT" for PASSMD and the client performing the password change received no answer (hung), and this has caused us many problems.
Could it possibly be an openldap bug? Thank you very much, Stefano