openldap-bugs

openldap-bugs@openldap.org

1 participants
21001 discussions

Re: (ITS#8907) Memory leak on mass adding users to ldap
by quanah＠symas.com 16 Nov '18

16 Nov '18

Hi Alexey, If you are using standard syncrepl (rather than delta-syncrepl), I'm not sure what you're reporting is out of the ordinary and is not indicative of a memory link. This is also why the issue "resolves" when ldap2 is stopped. I.e., the issue is related to how syncrepl functions and what it stores in memory while the lagging consumer is pulling down the database. I suggest switching to using delta-syncrepl and seeing if you see the same issue. Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: (ITS#8921) Content Sync Refresh Required when provider accesslog is empty
by quanah＠symas.com 16 Nov '18

16 Nov '18

--On Wednesday, September 26, 2018 8:40 PM +0000 au(a)hcsd.de wrote: > Full_Name: Stephan Austerm.hle > Version: 2.4.46 > messages when the provider has an empty accesslog (because it was freshly > setup and nothing has been added/updated since then). Hi Stephan, Are you positive you tested this with the OpenLDAP 2.4.46 Release? I already reported this issue via ITS#8100, which was explicitly fixed in 2.4.46. Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: (ITS#8934) Openldap get crashing
by quanah＠symas.com 16 Nov '18

16 Nov '18

--On Thursday, November 15, 2018 6:51 AM +0000 raghavendra.gadiga(a)capgemini.com wrote: Hello, The ITS system is for bug reports. Usage questions, such as how to properly tune OpenLDAP and its data backends belong on the openldap-technical(a)openldap.org project list. Please redirect your questions there. <http://www.openldap.org/lists/mm/listinfo/openldap-technical> Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

(ITS#8934) Openldap get crashing
by raghavendra.gadiga＠capgemini.com 14 Nov '18

14 Nov '18

Full_Name: Raghavendra Version: 2.4.44 OS: Debian GNU/Linux 9 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (203.191.35.25) Hi Team, We have noticed the ldap getting crash. Even the ldap process is running, we cant fetch the data in it, After debugging it we noticed that by removing the DB_CONFIG and restarting the service it started to work. 1) Can you let us know what was the cause. 2) Whats the ideal memory\cpu to be kept for ldap server. 3) Can you suggest tool which we can install to debug more. 4) More details about log setup for ldap. -Raghavendra.Gadiga

1 0

(ITS#8932) Fix slapd-config to honor rdnNormalize return code
by quanah＠openldap.org 09 Nov '18

09 Nov '18

Full_Name: Quanah Gibson-Mount Version: 2.4.46 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (47.208.148.239) When adding a new entry to cn=config, the code path currently does not check the value returned by rdnNoramlize. This needs to be fixed in case of a normalization error.

1 0

Re: (ITS#8878) PBKDF2 Is Broken (1 in 64 hashes)
by quanah＠symas.com 08 Nov '18

08 Nov '18

--On Tuesday, July 17, 2018 5:35 AM +0000 jroose(a)gmail.com wrote: > This is a significant bug in this module, because it causes the hash > algorithm to fail to be replicable by outside hash implementations 1 out > of every 64 hashes on average. Thanks for the report. This is now fixed in git master: - Log ----------------------------------------------------------------- commit d40a832db011985d6a6b787a88dd802b02d5d5dc Author: Ond??ej Kuzn??k <ondra(a)openldap.org> Date: Thu Nov 8 11:09:38 2018 +0000 ITS#8878 Include the first character in the transformation ----------------------------------------------------------------------- --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: (ITS#8914) OpenLDAP and OpenSSL v1.1.1
by quanah＠symas.com 07 Nov '18

07 Nov '18

--On Friday, September 21, 2018 9:59 PM +0000 quanah(a)symas.com wrote: >>> OpenLDAP will not configure for building against OpenSSL v1.1.1 due to >>> SSLv3 being disabled. Hi Neal, OpenSSL v1.1.1 does not in fact disable SSLv3. I would surmise from your experience that you are using Fedora, which has its own custom build of OpenSSL v.1.1.1 where the developers have disabled SSLv3. You will need to file a bug with them, since this is not an OpenLDAP issue but rather an issue with how Fedora is changing OpenSSL. Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: (ITS#8927) slapo-ppolicy is destructive to delta-sync replication
by quanah＠symas.com 07 Nov '18

07 Nov '18

--On Tuesday, October 16, 2018 6:59 PM +0000 quanah(a)symas.com wrote: > --On Tuesday, October 16, 2018 1:30 PM +0200 Ond=C5=99ej Kuzn=C3=ADk=20 > <ondra(a)mistotebe.net> wrote: > >>> - test we're a replicated op, not just on shadow >> >> The patch is available here: >> https://github.com/mistotebe/openldap/tree/its8927 > > I still get err 16 with this patch and the servers fall back to REFRESH. Note: Finally fixed with 04a52cef40560b9edec8037b23e444c460fe0d40 in master --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: (ITS#8931) deref'ing non-existent attributes should not result in protocolError
by michael＠stroeder.com 04 Nov '18

04 Nov '18

On 11/4/18 12:16 AM, hyc(a)symas.com wrote: > I don't see this in the deref code. It only returns protocolError if there is > any type of error when parsing the control itself. It was my fault. Sorry for the noise. Please close this ITS. Ciao, Michael.

1 0

Re: (ITS#8931) deref'ing non-existent attributes should not result in protocolError
by hyc＠symas.com 03 Nov '18

03 Nov '18

michael(a)stroeder.com wrote: > Full_Name: > Version: RE24 > OS: > URL: > Submission from: (NULL) (46.183.103.8) > > > In aehostd I try to limit the number of required search requests. Therefore I'm > using the deref control to read group and sudoers entries referenced in service > groups. > > If there are no such references (yet) slapd currently returns protocolError. I don't see this in the deref code. It only returns protocolError if there is any type of error when parsing the control itself. It knows nothing about any referenced entries when it's parsing the control. There are no other instances of protocolError in the overlay. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs