Forum OpenACS Development: Re: "received fatal signal 11" during ldap login

Collapse
Posted by Nathan Lunt on

The URL you posted doesn't show any of the configuration required for ns_ldap's pools in config.tcl, so can you confirm that you've set it up as specified at http://home.galileo.edu/~obonilla/software/nsldap?

My expectation is that ns_ldap will likely crash if there is ever any issue with a connection (I mean anything) to the LDAP server. It's unlikely that it's an issue with openldap, but ns_ldap, itself. Obviously the ns_ldap logging isn't very helpful (the exception handling is dismal), but you may get more beneficial information from openldap, which is probably logging to syslog. One day soon, I'll be fixing up TCLLIB's LDAP package so we can drop ns_ldap completely, but until then it's really going to be a lot of trial and error to determine what ns_ldap doesn't like.

NJL

Collapse
Posted by David Spanberger on
Thank you for your fast response.

To complete my message:

The Server is running as CentOS release 5.2 with Postgresql 8.2.9. from RPM, aolserver 4.5 from source and openacs 5.4.

I'm using openldap-devel-2.3.43. For ns_ldap I tried the version from Malte Sussdorff (http://www.sussdorff.de/ressources/nsldap.tgz) and the newest (from 2002) from sourceforge (v0r8)