Re: OpenLDAP-2.0alpha2 bind problem (more info)

["Kurt D. Zeilenga" <Kurt@OpenLDAP.org>]

At 12:27 PM 8/27/99 +0200, Frédéric Poels wrote:
>OK I finally got the trace when the server "hangs" (I hope it helps):

send the server a SIGABRT.  This should cause a core dump
which you can use to obtain a stack backtrace.  You might
also try running with a little more logging (-d 1 -d 4 -d 8).
(note: changing logging may change behavior, you might have
to toy with it a bit to get reasonable logging).

>do_bind: version=2 dn="cn=manager" method=128
>==> ldbm_back_bind: dn: CN=MANAGER
>dn2entry_r: dn: "CN=MANAGER"
>=> dn2id( "CN=MANAGER" )
>=> ldbm_cache_open( "/ccncsi/LDAP/DB/dn2id.dbb", 7, 600 )
><= ldbm_cache_open (cache 0)
><= dn2id NOID
>dn2entry_r: dn: ""
>=> dn2id( "" )
>=> ldbm_cache_open( "/ccncsi/LDAP/DB/dn2id.dbb", 7, 600 )
><= ldbm_cache_open (cache 0)
><= dn2id NOID
>do_bind: bound "cn=manager" to "cn=Manager"
>send_ldap_result: conn=927 op=0 p=2
>send_ldap_result: 0::
>send_ldap_response: msgid=1 tag=97 err=0
>connection_resched: attempting closing conn=920 sd=9
>connection_close: conn=920 sd=9
>daemon: removing 9
>connection_resched: attempting closing conn=923 sd=12
>connection_close: conn=923 sd=12
>daemon: removing 12
>connection_resched: attempting closing conn=925 sd=14
>connection_close: conn=925 sd=14
>connection_resched: attempting closing conn=917 sd=5
>connection_close: conn=917 sd=5
>daemon: removing 5
>connection_resched: attempting closing conn=922 sd=11
>connection_close: conn=922 sd=11
>daemon: removing 11
>daemon: removing 14
>connection_resched: attempting closing conn=924 sd=13
>connection_close: conn=924 sd=13
>daemon: removing 13
>connection_resched: attempting closing conn=919 sd=8
>connection_close: conn=919 sd=8
>daemon: removing 8
>
>
>