openldap-bugs

openldap-bugs@openldap.org

1 participants
20967 discussions

Re: (ITS#7578) delta-sync multimaster replication issue
by quanah＠symas.com 16 Nov '18

16 Nov '18

--On Friday, April 26, 2013 8:07 PM +0000 afrunning(a)gmail.com wrote: > Full_Name: Al F > Version: 2.4.35 > OS: Redhat 6.4 - x64 > URL: https://dl.dropboxusercontent.com/u/982376/its/al-f-130426.zip > Submission from: (NULL) (74.123.146.10) > > > Hi, I have a multimaster system utilizing delta-sync for replication. The > system is utilizing mdb for both the user and the accesslog data. I have > ppolicy & memberof overlays enabled as well. all of my writes are > directed at a single server using a load balancer. I have found that > when a user has a pwdFailureTime attribute set on their entry, if an > administrator resets the password, "null_callback : error code 0x10" is > produced in the log on the secondary system and the secondary system goes > into refresh mode. Hello, I believe this is the same as ITS#8927, which has been fixed for the upcoming OpenLDAP 2.4.47 release. Warm 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#8928) Reproducibility: Remove user, hostname, pwd from version string
by hyc＠symas.com 16 Nov '18

16 Nov '18

douglas.royds(a)taitradio.com wrote: > URL: ftp://ftp.openldap.org/incoming/douglas-royds-181026.patch > > This updated patch also sets the date and time strings to the > SOURCE_DATE_EPOCH. Are you intending a SOURCE_DATE_EPOCH to be a Unix time value? I.e., an integer? This value format needs to be documented. Unfortunately, your use of date -d is nonportable, it appears that only the GNU tools understand this option. It will fail on other platforms like *BSD, Solaris, that aren't using a GNU userland. Why can't you simply provide an already formatted date & time that can be used directly, instead of needing to be reformatted here? > The WHOWHERE string will now be set to simply "openldap" in the case > that a SOURCE_DATE_EPOCH is set. > > Tait Communications Ltd hereby place the following modifications to > OpenLDAP Software (and only these modifications) into the public domain. > Hence, these modifications may be freely used and/or redistributed for > any purpose with or without attribution and/or other notice. > > > > > -- -- 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

Re: (ITS#8887) doc/guide/admin/backends.sdf: is is
by quanah＠symas.com 16 Nov '18

16 Nov '18

--On Wednesday, August 01, 2018 2:44 AM +0000 dpa-bugs(a)aegee.org wrote: > Full_Name: &#1044;&#1080;&#1083;&#1103;&#1085; > &#1055;&#1072;&#1083;&#1072;&#1091;&#1079;&#1 > 086;&#1074; Version: 2.4 documentation > OS: Linux > URL: > Submission from: (NULL) (103.252.202.53) > > > Consider this change (remove doubled " is is " Thanks for the report! This patch has been applied. --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#8899) SLAPD failed to start after updating openldap 2.4.46
by quanah＠symas.com 16 Nov '18

16 Nov '18

--On Friday, August 17, 2018 12:56 PM +0000 muthaiyan1991(a)gmail.com wrote: > Full_Name: Muthaiyan Vel > Version: 2.4.46 > OS: Solaris 10 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (116.197.184.12) > > > I have recently updated openldap to version 2.4.46. After upgrading SLAPD > is failed to start. Its showing an error "slap_sasl_init: auxprop add > plugin failed". > I have compiled the openldap with mdb. > > Please help to solve this problem. Hello Muthaiyan, The ITS system is for reporting software bugs. Usage questions such as this belong on the openldap-technical mailing list (<http://www.openldap.org/lists/mm/listinfo/openldap-technical>) and would receive a much quicker response time. I would note that your log was not "full debug" mode as you stated (which would be -d -1), and the warning you encountered is common and not indicative of an actual problem. 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>

1 0

Re: (ITS#8902) man page update for slapadd(5)
by quanah＠symas.com 16 Nov '18

16 Nov '18

--On Friday, November 16, 2018 8:26 PM +0000 quanah(a)symas.com wrote: > The note for the -w argument does not apply to back-mdb, since back-mdb > uses an isolated snapshot of the database when performing the slapcat. > Thus the out of order "hot change" issue does not apply (which is the > problem with using -w with back-bdb/hdb). <https://github.com/quanah/openldap-scratch/tree/its8902> -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: (ITS#8902) man page update for slapadd(5)
by quanah＠symas.com 16 Nov '18

16 Nov '18

The note for the -w argument does not apply to back-mdb, since back-mdb uses an isolated snapshot of the database when performing the slapcat. Thus the out of order "hot change" issue does not apply (which is the problem with using -w with back-bdb/hdb). -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

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

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