Re: [nssldap] Segmentation Faults for Ldap Accounts
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
Re: [nssldap] Segmentation Faults for Ldap Accounts
- From: Andrew Morgan <morgan [at] orst.edu>
- To: Jim Summers <jsummers [at] bachman.cs.ou.edu>
- Cc: nssldap [at] padl.com
- Subject: Re: [nssldap] Segmentation Faults for Ldap Accounts
- Date: Fri, 11 Apr 2008 15:17:43 -0700 (PDT)
On Fri, 11 Apr 2008, Jim Summers wrote:
What about turning off SSL in nss-ldap temporarily? That could narrow the
problem down. Also, you could run strace on pjm and see which system call
actually segfaults it.
I turned off ssl and the pjm program worked. Turned it back on and the pjm
segfaults.
Here is my ldap.conf, which is also the same as the one on the FC5 and FC6
clients:
uri ldaps://server1 ldaps://server2
base dc=ou,dc=edu
binddn cn=bind0,ou=profile,dc=ou,dc=edu
bindpw ++++++++
port 636
#port 389
#idle_timelimit 3600
ssl on
tls_checkpeer no
pam_password crypt
pam_lookup_policy yes
#debug 1
I am not sure what to look for in my ssl/tls setup. The whole thing is
running off of self-signed certificates.
Can you run your pjm program under strace? Something like:
strace -ff -o /tmp/trace pjm <args>
I can help look at the trace files, if you don't know what to look for.
Andy
- Re: [nssldap] Segmentation Faults for Ldap Accounts, (continued)
Re: [nssldap] Segmentation Faults for Ldap Accounts,
Buchan Milne