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

Re: slapd: attr.c:481: attr_merge: Assertion

To: Michael StrÃder <michael@stroeder.com>
Subject: Re: slapd: attr.c:481: attr_merge: Assertion
From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
Date: Fri, 16 Mar 2012 13:41:24 +0100
Cc: Howard Chu <hyc@symas.com>, openldap-devel@openldap.org
In-reply-to: <4F6326AF.3030606@stroeder.com>
References: <4F630711.2020308@stroeder.com> <4F631B26.60800@symas.com> <4F6326AF.3030606@stroeder.com>
User-agent: Roundcube Webmail/0.4.2

On Fri, 16 Mar 2012 12:40:31 +0100, Michael StrÃder wrote:

We saw this assertion in a production server during processing amodify of anentry. My co-worker said he could reproduce it. Does it mean the BDBfiles
were corrupt?

Maybe, in particular if you upgraded without doing slapcat/slapadd.Buta FIXME followed by an assert looks suspiciously like "Shouldn'thappen,

but who knows if it does" - which doesn't belong in production code.
Can you provide a gdb 'backtrace full' which also does 'print **a'?

--
Hallvard

Follow-Ups:
- Re: slapd: attr.c:481: attr_merge: Assertion
  - From: Michael StrÃder <michael@stroeder.com>

References:
- slapd: attr.c:481: attr_merge: Assertion
  - From: Michael Ströder <michael@stroeder.com>
- Re: slapd: attr.c:481: attr_merge: Assertion
  - From: Howard Chu <hyc@symas.com>
- Re: slapd: attr.c:481: attr_merge: Assertion
  - From: Michael Ströder <michael@stroeder.com>

Prev by Date: Re: slapd: attr.c:481: attr_merge: Assertion
Next by Date: Re: slapd: attr.c:481: attr_merge: Assertion
Index(es):
- Chronological
- Thread