Connections established using SASL die after search

[Mark Roach]

On Sun, 2004-12-12 at 01:28 +0100, Michael Ströder wrote:

> Upgrading would be good. AFAIK the MIT Kerberos implementation is not 
> thread-safe. This can lead to very weird effects depending how 
> OpenLDAP's slapd is built. Use a recent heimdal release instead.

Hi, Michael. Thanks for your assistance with this. I have upgraded my
openldap server to 2.2.19 and replaced the mit kerberos sasl module with
the heimdal one and the problem seems to be the same.

I have no idea if it's useful, but I am including the tail of the debug
output of slapd process while causing a failure.

Any additional suggestions are much appreciated.

Thanks,

Mark Roach



        Slapd debug info:
-----------------------------------
=> access_allowed: search access granted by read(=rscx)
<= test_filter 5
<= test_filter_and 5
<= test_filter 5
bdb_search: 110 does not match filter
send_ldap_result: conn=6 op=2 p=3
send_ldap_result: err=0 matched="" text=""
send_ldap_response: msgid=3 tag=101 err=0
ber_flush: 14 bytes to sd 10
  0000:  30 0c 02 01 03 65 07 0a  01 00 04 00 04 00
0....e........
ldap_write: want=14, written=14
  0000:  30 0c 02 01 03 65 07 0a  01 00 04 00 04 00
0....e........
conn=6 op=2 SEARCH RESULT tag=101 err=0 nentries=0 text=
daemon: activity on 1 descriptors
daemon: activity on: 10r
daemon: read activity on 10
connection_get(10)
connection_get(10): got connid=6
connection_read(10): checking for input on id=6
ber_get_next
ldap_read: want=8, got=0

ber_get_next on fd 10 failed errno=0 (Success)
connection_read(10): input error=-2 id=6, closing.
connection_closing: readying conn=6 sd=10 for close
connection_close: conn=6 sd=10
daemon: removing 10
conn=6 fd=10 closed
daemon: select: listen=6 active_threads=0 tvp=NULL
daemon: select: listen=7 active_threads=0 tvp=NULL
daemon: activity on 1 descriptors
daemon: select: listen=6 active_threads=0 tvp=NULL
daemon: select: listen=7 active_threads=0 tvp=NULL