Hi Binoy,
Sorry that this dropped off the radar for so long. Are you still seeing
this issue in Windows with the current OpenLDAP release?
Thanks,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Hi Priyesh,
The back-ndb backend is entirely experimental (as noted in the manpage) and
the work on it was never completed. It should not be used nor should it be
expected to work. Hope that helps!
This ITS will be closed.
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Hi Frank,
Do you still encounter this issue with current OpenLDAP builds?
Thanks,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Hello,
Can you report back on whether or not you still see this behavior with
current OpenLDAP 2.4.44? Significant fixes (Such as for ITS#8281) have
occurred since this report for 2.4.23.
Thanks!
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Hi Frank,
I believe this is a duplicate of ITS#8281. Can you test with current RE24
and see if you can still produce this problem?
Thanks,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Hello,
The patch provided in the URL is no longer available. Do you still have a
copy of this patch? I would also note that the preferred destination for
patches is the OpenLDAP FTP server, as noted in the submission process.
Thanks,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--On Tuesday, March 28, 2017 12:10 AM +0000 etc(a)nol2ter.org wrote:
> Full_Name: Jaiho Lee
> Version: 2.4.44
> OS: Gentoo
> URL: ftp://ftp.openldap.org/incoming/Jaiho-Lee-170327.patch
> Submission from: (NULL) (61.96.190.143)
>
>
> * slapd.conf
> Postgresql returns error when you try to add first entry if ldap_entries
> is empty.
>
> * testdb_drop.sql
> It won't delete a table, certs.
>
Thanks for the report! We will review this for the upcoming 2.4.45 release.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Full_Name: Jaiho Lee
Version: 2.4.44
OS: Gentoo
URL: ftp://ftp.openldap.org/incoming/Jaiho-Lee-170327.patch
Submission from: (NULL) (61.96.190.143)
* slapd.conf
Postgresql returns error when you try to add first entry if ldap_entries is
empty.
* testdb_drop.sql
It won't delete a table, certs.
--On Monday, March 13, 2017 5:16 PM +0000 quanah(a)symas.com wrote:
> --On Monday, March 13, 2017 12:55 PM -0400 Matthew Berg
> <mberg(a)synacor.com> =
>
> wrote:
>
>> "After investigating the server setup, there are a few problems here.
>> The new server was being configured with sid=3D001 which was already
>> assigned to=C2=A0the original master. That's clearly going to screw =
> things
>> up."
>
> I'm aware of what Howard's original response was. That has nothing to
> do=20 with what the problem was, or the later 100% reproducible test I
> provided=20 him that did not have that problem.
Hi Matt,
Just wanted to let you know I followed up with Howard on this, and he's
going to look at tweaking it somewhat to ensure that it doesn't have the
potential to cause follow on problems. I've reopened and moved it to
software bugs. I'll let you know once the code change is available.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
On Fri, Mar 24, 2017 at 12:07:32PM -0700, Paul B. Henson wrote:
> Ah, more confusion, sorry; I confirmed with Quanah the ITS 8432 patch
> I applied is identical to the one applied upstream, however, the line
> I referred to is in the patch applied to 2.4.44 release code, whereas
> I see you are referring to the current head of the 2.4 branch, which
> I'm sure has had numerous other changes applied to it that have
> probably shuffled things around a bit.
Hi Paul,
yes it did, I should have checked for that and would have if the wrong
line didn't line up so well.
> If I could reliably reproduce this issue :(, I would definitely test
> it on our dev systems with whatever code you requested. Unfortunately,
> it only randomly occurs every 2-4 weeks in production, and I don't
> think I could get management approval to run the unreleased
> development branch of code in production for that long to see what
> happens. The 2.4.45 testing call came out last month, is there a
> timeline yet on getting that out? I should be able to push that into
> production fairly soon after it is released and see what happens
> there.
I've had a look whether I could reproduce the issue somehow and there is
a potential crasher if the accesslog entry contained "reqmod:
eduPersonAffiliation:+". Can you confirm whether you have entries like
this in your logdb? There shouldn't be a way to have this kind of entry
generated that I could see but processing one can sometimes cause
a crash like the one you've been seeing.
The following patch should fix an issue where an invalid accesslog entry
of this sort is encountered. It should help you if that is the issue.
ftp://ftp.openldap.org/incoming/Ondrej-Kuznik-20170327-ITS8609-ignore-inval…
Regards,
Ondrej