[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: 2.4.45 slapadd segfault
- To: openldap-technical@openldap.org
- Subject: Re: 2.4.45 slapadd segfault
- From: Christopher Wood <christopher_wood@pobox.com>
- Date: Thu, 31 Aug 2017 11:13:04 -0400
- Content-disposition: inline
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=date:from:to :subject:message-id:references:mime-version:content-type :in-reply-to; s=sasl; bh=HNOJV+pfNWUa7nS4zpzfIw6c0Lw=; b=mDfBwBm rlicezIMR6P9UAMbd7mxT3ut1VaIRjF6Gg4d1sq+7inKXveQMgE2FlsEp/fvM3SB Qg3Pd1khtNtzs8/ZBhiL2XKJYUQPSxqosBP/ZXTVZyLJ5UqbB26pNzBnPSrCMsE0 WOsEjX5qf/ZUXXkgJ/mEAD79CTkPItebQzaU=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=pobox.com; h=date:from:to :subject:message-id:references:mime-version:content-type :in-reply-to; q=dns; s=sasl; b=g2yqLxeBzRiuC/vEVlYHpFFdbF41Id3XL Y7kMcL8LQkKChTGIWOTkg3DYu8r54uYTidrBLCe5d+FqaHBcMBYw8fIyMDkYkN3I ANA7LLk5gJQDhWS1t/7vkY2Po2+nVAgZSR/x9Mza1Yp/gzxKVtT4YnfeLapNe4/A aA095bIGgQ=
- In-reply-to: <0ef3c529-0ff4-b419-808c-2e40080ca9f2@symas.com>
- References: <20170831143650.vctur3ayukox37rx@iniquitous.heresiarch.ca> <WM!31fa149c60601d0fe4c1d4f39388dd86a14daf5e8b123edc1c1826f320fd1b16f8f3300513d5ffaad8bc92f20d511b32!@mailstronghold-2.zmailcloud.com> <0ef3c529-0ff4-b419-808c-2e40080ca9f2@symas.com>
- User-agent: NeoMutt/20170113 (1.7.2)
On Thu, Aug 31, 2017 at 03:49:44PM +0100, Howard Chu wrote:
> Christopher Wood wrote:
> > Good morning, long time no list.
> >
> > For backstory, I downloaded the 2.4.45 source tarball from https://www.openldap.org/software/download/, compiled, ran "make test" (which was fine as near as I can tell), but doing a slapadd of cn=config caused a segfault.
> >
> > I used the points on http://www.openldap.org/faq/data/cache/59.html to create the following backtrace:
> >
> > https://gist.github.com/christopherwood/701fbc70ef352a3bf2d2893a9ae0a65e
> >
> > And this is the ldif (temporary password is fakepass333):
> >
> > https://gist.github.com/christopherwood/2cf46f5a3384f9edc89e7eabbefc465e
> >
> > Does anything jump out at you as obviously wrong or a good place to look? I've chopped the ldif down from the original with confidential data and am still reducing, but it's still segfaulting.
>
> Yes. Look at your LDIF line 62 more carefully. Compare it to line 65 if it's
> still not obvious to you.
>
> Granted it shouldn't SEGV but the backtrace shows it was shutting itself
> down already because it (correctly) rejected your input.
Oh ouch, that is obvious now. Nothing like typo'ing in front of the internet first thing in the morning. Thank you, ahem.
(For posterity: The accesslog overlay configuration at line 62 specifies the syncprov overlay in the DN, which won't work. When I specify olcOverlay={1}accesslog in the DN line, it works without a segfault.)
> --
> -- Howard Chu
> CTO, Symas Corp. http://www.symas.com
> Director, Highland Sun http://highlandsun.com/hyc/
> Chief Architect, OpenLDAP http://www.openldap.org/project/
>