[Date Prev][Date Next]
Re: (ITS#7143) Assertion error (crash); using relay backend and translucent overlay
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#7143) Assertion error (crash); using relay backend and translucent overlay
- From: email@example.com
- Date: Tue, 31 Jan 2012 02:53:08 GMT
- Auto-submitted: auto-generated (OpenLDAP-ITS)
Mattias Andersson wrote:
> On Tue, 31 Jan 2012 02:27:05 +0100, Howard Chu<firstname.lastname@example.org> wrote:
>> email@example.com wrote:
>>> Full_Name: Mattias Andersson
>>> Version: 2.4.25
>>> OS: Linux
>>> URL: ftp://ftp.openldap.org/incoming/
>>> Submission from: (NULL) (188.8.131.52)
>> 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.
The assertion leads me to believe that one of the values received from the
remote server violated the attribute syntax, and so the value failed in the
normalizer on the local slapd. What is the remote server?
It's a bit strange that changing the configuration, but leaving the remote
server unchanged, avoids the problem.
> In any case, I have a different configuration now, that solves the problem
> in another way (by using two separate local databases -- one for the
> translucent overlay and one for the subordinate directory.) Another
> problem with the previous configuration was that I was getting "user
> modification of overlay database not permitted" errors when using
> ldapadd/ldapmodify (seems the translucent overlay can not be stacked with
> the rwm overlay.)
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/