[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:23:38 -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=ZG5yN8g7T+M5paFa95SMJVRCcaA=; b=ryqIPyb b6pxqu2BUEaXnvqBS1PYi/TCv9BPleRpQvIwDkV8pD+7JvQPXg2DRbQNR8aN4iz9 SL63Em9te70TEVNs9qj65DDYtVABIUZDGmI872Or0+QQwaNy3gNvBxvmxVeDDIQy 95rIqLFwvWeJA59iP8DW0ZaPdewppAXZCL6A=
- 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=Py9vmxydQIqftN6YwHpkahriLcMxVmiTo UeOpO4sje+C9oFWgbtoVhYeV/8ptesgZVvV/132v3n36+6yZ6Q62mbKOrhCJl7kb XRsGTHd8QVkMZL3tLqx+dY6e8hxxSn4v+gntLMB7fUyN3LvRQ97SLKQzCnlqVyLX 8mr/kL0xdo=
- In-reply-to: <CBA76C1CD75E77DA93DA7919@[192.168.1.30]>
- References: <20170831143650.vctur3ayukox37rx@iniquitous.heresiarch.ca> <WM!31fa149c60601d0fe4c1d4f39388dd86a14daf5e8b123edc1c1826f320fd1b16f8f3300513d5ffaad8bc92f20d511b32!@mailstronghold-2.zmailcloud.com> <0ef3c529-0ff4-b419-808c-2e40080ca9f2@symas.com> <WM!6e00e1eb47c4b448f824016850321cb0a2a4060f8ec43780aa71d1f0cd35c61a84224ea0962ae791a83b1dee9f3d7898!@mailstronghold-1.zmailcloud.com> <CBA76C1CD75E77DA93DA7919@[192.168.1.30]>
- User-agent: NeoMutt/20170113 (1.7.2)
On Thu, Aug 31, 2017 at 07:59:00AM -0700, Quanah Gibson-Mount wrote:
> --On Thursday, August 31, 2017 4:49 PM +0100 Howard Chu <hyc@symas.com>
> 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.
>
> There are a number of errors with that LDIF file, outside of what Howard
> already pointed out. ;)
>
> The objects in 54 & 62 are also missing their RDN as a value too.
I've been finding the errors as I go along.
Slapadd has been adding the RDNs in to the generated cn=config database for me. I've found that happens when using ldapadd too. I didn't worry about doing it myself after seeing that because it's another place to typo something. (Not that this helped overmuch, obviously.)
> --Quanah
>
>
>
> --
>
> Quanah Gibson-Mount
> Product Architect
> Symas Corporation
> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
> <http://www.symas.com>
>