Re: segmentation fault when attempting to delete olcOverlay={0}syncprov

On Thu, Jul 22, 2010 at 2:06 AM, Ralf Haferkamp <rhafer@suse.de> wrote:

Am Mittwoch 21 Juli 2010, 20:02:43 schrieben Sie:

> Hi Ralf,
> Sorry for not replying to the entire list, but I have 2 reasons:
>
> 1) I am working on adding the bug report to bugzilla (got my account,
> ect.) ... wasn't sure what product to file the bug under.

openSUSE 11.3 should be fine in your case. (BTW, which product did you
install the 2.4.21 package on?)

> 2) While searching around other "openLdap" bug reports I found this
> one: *Bug 384787 - OpenLDAP packages do not contain overlays (
> https://bugzilla.novell.com/show_bug.cgi?id=384787 )
> *Which is EXACTLY my other issue I am trying to figure out ;o) ...
> Before I submit a detailed report at OpenLDAP.org, maybe you can
> answer this question for me (I can then post in a new email thread as
> not to mess up the current "delete issue" thread).
>
> In 384787, you say that all the overlays are "compiled statically into
> the slapd daemon". How do I fill in the olcModulePath value? I have
> this, and it doesn't seem to be working:
>
> dn: cn=module{0}
> objectClass: olcModuleList
> cn: module{0}
> olcModulePath: ../../../servers/slapd/overlays
> olcModuleLoad: {0}syncprov.la

As the overlays are compiled statically into the slapd binary there is no
need to load any module. So you can just leave out the cn=module object.

> I still get this error message on both my servers ("do_syncrep2: got
> search entry withour Sync State control"). How do I configure the

> syncprov.laproperly in cn=config ... It works just fine the old way
> using slapd.conf
> files ...
It's a bit hard to tell, what got wrong there. But it could be e.g. that
you try to replicate a database which doesn't have the syncprov overlay
configured. Take a look at your provider's configuration and check that
each database that you want to replicate has the syncprov overlay
configured. If that doesn't help. Open a new thread on openldap-technical
containing the complete configuration (excluding the Schema) for the
provider and the consumer.

regards,
Ralf

> On Wed, Jul 21, 2010 at 11:54 AM, Ralf Haferkamp <rhafer@suse.de>
wrote:
> > Am Mittwoch 21 Juli 2010, 18:26:58 schrieb jon brandt:
> > > Thanks for the reply Ralf!
> > >
> > > I got the RPMs for SUSE I believe (i.e. I didn't build the server
> > > myself), so I'm assuming the DSLAP_CONFIG_DELETE flag was used.
> >
> > Yes, probably. Might I ask you to open a bug report at
> > bugzilla.novell.com? So we can fix it and probably release an
> > updated RPM.
> >
> > > All
> > > the other deletes work fine (I'm adding then deleting other
> > > directives, for example olcMirrorMode or olcDbIndex and those
> > > delete just fine from cn=config).
> >
> > Yes. The problematic thing is deleting complete objects (e.g.
> > overlays, databases). Deleting single Attributes should work just
> > fine and doesn't require -DSLAP_CONFIG_DELETE.
> >
> > > I will try to upgrade to a newer version
> > > and see if that helps.
> >
> > It'll probably just deny to execute the operations (e.g. when
> > removing overlay entries from the frontend or config db). But I
> > consider that better than crashing the server :).
> >
> > regards,
> >
> > Ralf
> > >
> > > What is strange is that this fails on most of
> > > the servers I have setup, but there there is one server that has a
> > > bit more horsepower that doesn't have the issue, so this leads me
> > > to believe it is a timing related issue.
> > >
> > > On Wed, Jul 21, 2010 at 9:18 AM, Ralf Haferkamp <rhafer@suse.de>
wrote:
> > > > Am Dienstag 20 Juli 2010, 20:25:46 schrieb jon brandt:
> > > > > I looked but couldn't find a match to this issue, so was
> > > > > wondering if anyone else has seen something like it or can
> > > > > tell what might be wrong in my configuration. Thanks in
> > > > > advance!
> > > > >
> > > > > I'm using OpenLDAP version 2.4.21-47.1 (here is the relevant
> > > > > output from "rpm -qa | grep ldap" on my server):
> > > > >
> > > > > openldap2-client-2.4.21-51.1
> > > > > openldap2-2.4.21-47.1
> > > > > openldap2-back-meta-2.4.21-51.1
> > > > >
> > > > > I'm trying to get Multi-master replication working between 2
> > > > > servers. In my testing, I have discovered that when I try to
> > > > > reset the server (remove the configuration and start again) it
> > > > > crashes when trying to remove the
> > > > > olcOverlay={0}syncprov,olcDatabase={0}config,cn=config entry
> > > > > in the cn=config tree. I attached a screen shot of the
> > > > > output from tracing with slapd -d -1 when the fault happened
> > > > > in the attached file called * segFaultOutput.bmp.*
> > > > >
> > > > > If I restart the server, I can run the test again (which
> > > > > configures the olcOverlay={0}syncprov entry and then removes
> > > > > it) and it will work the first time, but if I run it a second
> > > > > time it will crash.
> > > >
> > > > Hm, did you build your server with -DSLAP_CONFIG_DELETE? If yes,
> > > > please note that delete support in cn=config is still
> > > > experimental. So please test again with cvs HEAD if it works
> > > > there. There have been some changes/fixes in that area
> > > > recently.
> > > >
> > > > If you didn't compile with -DSLAP_CONFIG_DELETE please make a
> > > > bugreport slapd should have rejected the delete operation in
> > > > that case.

Re: segmentation fault when attempting to delete olcOverlay={0}syncprov entry in cn=config (Runtime) Configuration