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

Re: Segmentation Fault with SASL DIGEST-MD5 authentication

Hi!

Just some help: If you've compiled OpenLDAP to use e.g. SleepyCat BDB 4.1.25 and you're running an older version of BDB on your system, you should compile BDB with the configure-option --with-uniquenames and supply OpenLDAP with the correct include-files which have to be installed in another place than the ones of the old BDB.

So there won't be a symbol-clash which results in a segmentation fault as it was stated by Tony.

Hope this helps. :)


Chris


Tony Earnshaw schrieb: 
tor, 24.04.2003 kl. 10.17 skrev Chee Wai Yeung:


Now when I run:

ldapsearch -d100 -U user@example.com -b
'dc=example,dc=com' -h localhost 'uid=user'

I got:

request 1 done
SASL/DIGEST-MD5 authentication started
request 2 done
Segmentation fault

The slapd is *still* running. Now if I simply run

ldapsearch -D 'cn=Manager,dc=example,dc=com' -b
'dc=example,dc=com' -x -h localhost -W 'uid=user'

(after supplying the password) I got the search
results.



Do ldd on the slapd binary and double check that it's not linked with
conflicting libraries. This happened to me a couple of versions back,
and it was due to conflicting BDB libraries, but it could just as well
be the SASL libraries or Openssl (the latter especially if you've
upgraded from 0.9.6 to 0.9.7.)

Best,

Tony