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

Re: (ITS#7143) Assertion error (crash); using relay backend and translucent overlay



On Fri, 03 Feb 2012 20:26:01 +0100, Quanah Gibson-Mount  
<quanah@zimbra.com> wrote:

> --On Tuesday, January 31, 2012 10:41 AM +0000 mattias@centaurix.com  
> wrote:
>
>> On Tue, 31 Jan 2012 03:56:06 +0100, Howard Chu <hyc@symas.com> wrote:
>>
>>> Mattias Andersson wrote:
>>>> On Tue, 31 Jan 2012 02:27:05 +0100, Howard Chu<hyc@symas.com>  wrote:
>>>>
>>>>> Please provide a full gdb backtrace from the assertion failure. I've
>>>>> reproduced this configuration locally but see no crash using
>>>>> ldapsearch.
>>>>> I don't have the Softerra browser.
>>>>
>>>> Ok, see attachment. The problem is not reproducible with ldapsearch.
>>>
>>> Please see if the attached patch alters the behavior. Thanks.
>>
>> I'm getting an error that MozNSS is not found when I run ./configure.
>>
>> Mattias
>
> Hi Mattias,
>
> Any update?  We would like to get a fix for this into OpenLDAP 2.4.29 if  
> possible.

Ok, I didn't apply the patch yet, but now I'm getting a different error  
than before (before I was using OpenLDAP 2.4.25 from the Ubuntu package  
repository):

cornelian build_unix # /usr/local/libexec/slapd -d 256 -f  
/etc/ldap/slapd.conf
4f2c5a69 @(#) $OpenLDAP: slapd 2.4.28 (Feb  1 2012 02:31:50) $
	root@cornelian:/root/openldap/openldap-2.4.28/servers/slapd
4f2c5a69 hdb_db_open: database "dc=rss,dc=chalmers,dc=se": unclean  
shutdown detected; attempting recovery.
4f2c5a69 hdb_monitor_db_open: monitoring disabled; configure monitor  
database to enable
4f2c5a69 slapd starting
4f2c5ac2 conn=1000 fd=12 ACCEPT from IP=127.0.0.1:39354 (IP=0.0.0.0:389)
4f2c5ac2 conn=1000 op=0 BIND dn="" method=128
4f2c5ac2 conn=1000 op=0 RESULT tag=97 err=0 text=
4f2c5ac2 conn=1000 op=1 SRCH base="dc=chalmers,dc=se" scope=2 deref=0  
filter="(objectClass=*)"
4f2c5ac2 conn=1000 op=1 SRCH attr=1.1
/usr/local/libexec/slapd: symbol lookup error:  
/usr/local/libexec/openldap/back_ldap-2.4.so.2: undefined symbol:  
ldap_get_message_ber

This error also happens with ldapsearch.

Mattias