[Date Prev][Date Next] [Chronological] [Thread] [Top]

seg faults with 2.12 slapd and GSSAPI bind

I've been working on an openldap installation on a Red Hat 7.3 machine.

slapd's been giving me seg faults when I try to bind with GSSAPI.  

I'm using cyrus-sasl-2.1.12 with MIT krb5-1.2.4.

Looking at the list archives I have to start wondering if some of this
is related to the krb5 libs not being thread safe.

For what it's worth, I get the same results (seg faults) whether I
compile openldap with --with-threads or --without-threads

I'd be happy to try out any suggestions.  I don't know much about using
gdb, but here's what I get when I run:

ldapsearch -H ldap://MYSERVERFQDN/ -Y gssapi -b "" -s base -LLL supportedSASLMechanisms

(gdb) set follow-fork child
(gdb) next
Single stepping until exit from function sigsuspend,
which has no line number information.
[New Thread 2051 (LWP 26741)]
[New Thread 3076 (LWP 26742)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 3076 (LWP 26742)]
0x0819c953 in ?? ()
(gdb) bt
#0  0x0819c953 in ?? ()
#1  0x400b6673 in _sasldb_getdata () from /usr/lib/sasl2/libsasldb.so.2
#2  0x400b503a in sasldb_auxprop_lookup () from
#3  0x080dbe20 in _sasl_auxprop_lookup ()
#4  0x080e6472 in _sasl_canon_user ()
#5  0x4045b733 in gssapi_server_mech_step ()
   from /usr/lib/sasl2/libgssapiv2.so.2
#6  0x080e3a68 in sasl_server_step ()
#7  0x0808de55 in slap_sasl_bind ()
#8  0x0806c7e1 in do_bind ()
#9  0x08053191 in connection_operation ()
#10 0x080b1d06 in ldap_int_thread_pool_wrapper ()
#11 0x40275f77 in pthread_start_thread () from /lib/libpthread.so.0
(gdb) Quit

GSSAPI binds (on this server) completely kill slapd.  Have other people
seen this behavior?  Workarounds?


Ben Poliakoff                                       email: <benp@reed.edu>
Reed College                                          tel:  (503)-788-6674
Unix System Administrator      PGP key: http://www.reed.edu/~benp/key.html
0x6AF52019 fingerprint = A131 F813 7A0F C5B7 E74D  C972 9118 A94D 6AF5 2019