On Wed, 2002-07-10 at 23:40, Alexander Skwar wrote: > So sprach Alexander Skwar am 2002-07-05 um 18:37:42 +0200 : > > Hmm, there seems to be some problem with libsasl. mysql SIGSEGV's right > > No ideas? >From what I've understood from your strace file: - mysql is dynamically linked with libnss_ldap.so (something in /etc/nsswitch.conf might have triggered the loading of this library). - libnss_ldap.so needs libldap.so (it seems rather normal) - libldap.so needs libsasl.so because LDAP is authenticated using SASL (which is a general authentication scheme, not only bounded to SMTP, even if it is more used with SMTP). - after loading several libs needed both for ldap and sasl (like libcrypto...), mysql tries to find teich.garten.digitalprojects.com IP with the resolver (connecting to /var/run/.nscd_socket). This particular point seems to trigger the reading of /etc/ldap.conf. It then reads the liblogin SASL plugin, and it find it, but is not able to do something with it.
The strace report is not sufficient to get exactly what has happened. Maybe you should use ltrace, or gdb directly mysql. What I can see is that something in the ldap.conf is triggering the use of sasl. And that something in nssswitch.conf is triggering the loading of ldap. Send us your nsswitch.conf to see what's the problem. I hope this will help you. Brice
