nslcd.conf (sanitized): admin@it-home:/etc$ sudo egrep -v '(^$|^\s*#)' nslcd.conf uid nslcd gid nslcd uri ldap://ldap1.mydomain.com base dc=mydomain,dc=com ssl start_tls tls_ciphers TLSv1 tls_cacertfile /etc/ssl/certs/ldapca.cert tls_cert /etc/ssl/certs/it-home.cert tls_key /etc/ssl/private/it-home.key uri ldap://ldap2.mydomain.com
I have triple checked that the cert and key paths are correct and that they are readable by the nslcd user (by adding it to the ssl-cert group). As for the gdb, I'm not sure how to get the dbg symbols for nslcd, there is no nslcd-dbg package. When print the bt I just get hex addresses. Do you want those anyways? Not sure if they'll do you any good... Or I can attach a core dump to the bug or upload it somewhere. -- Isaac Freeman - Systems Administrator IBM Information Protection Services is...@us.ibm.com 919-254-0245 From: Arthur de Jong <adej...@debian.org> To: Isaac Freeman/Raleigh/Contr/IBM@IBMUS, 638...@bugs.debian.org Date: 08/22/2011 02:41 PM Subject: Re: Bug#638872: nslcd: segfault when tls_ciphers is declared On Mon, 2011-08-22 at 12:05 -0400, Isaac Freeman wrote: > Whenever "tls_ciphers" is delcared in /etc/nslcd.conf, the daemon > segaults on start. Thanks for your bugreport. I cannot easily reproduce this. What is the contents of your /etc/nslcd.conf? > I am attaching an strace of the daemon in debug mode showing the > segfault. Can you try running nslcd under gdb: # gdb nslcd [...] (gdb) r -d [...] (gdb) bt [...] (gdb) bt full If the bottom item on the stack is in a library having the -dbg package for that library installed will reveal lots of useful information. Thanks for your bugreport. -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong -- [attachment "signature.asc" deleted by Isaac Freeman/Raleigh/Contr/IBM]
<<inline: graycol.gif>>
