openldap-bugs

openldap-bugs@openldap.org

1 participants
21003 discussions

Re: (ITS#8620) GCC error undeclared PTHREAD_MUTEX_ROBUST
by blissend＠gmail.com 17 Mar '17

17 Mar '17

--94eb2c184874dd3bec054af90cab Content-Type: text/plain; charset=UTF-8 Ahah, it compiles if you remove lines 277-279 which was... #if defined(MDB_OWNERDEAD) && (MDB_USE_ROBUST) #define MDB_ROBUST_SUPPORTED 1 #endif However, I'm not sure that's what one should do. --94eb2c184874dd3bec054af90cab Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Ahah, it compiles if you remove lines 277-279 which was...= <div><br></div><div><div>#if defined(MDB_OWNERDEAD) && (MDB_USE_ROB= UST)</div><div>#define MDB_ROBUST_SUPPORTED<span class=3D"gmail-Apple-tab-s= pan" style=3D"white-space:pre"> </span>1</div><div>#endif</div></div><div><= br></div><div>However, I'm not sure that's what one should do.</div= ></div> --94eb2c184874dd3bec054af90cab--

1 0

(ITS#8620) GCC error undeclared PTHREAD_MUTEX_ROBUST
by blissend＠gmail.com 17 Mar '17

17 Mar '17

Full_Name: Adam Carlin Version: lmdb 0.9.20 OS: Windows 10 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (108.27.217.230) I'm using Windows 10 with msys2 64bit (http://www.msys2.org/) which utilizes mingw-w64. When I compile lmdb (https://github.com/LMDB/lmdb/tree/mdb.RE/0.9) v0.9.20 it spits out the error message below... blissend@shockedloris MSYS /c/Compile/lmdb/libraries/liblmdb $ make gcc -pthread -O2 -g -W -Wall -Wno-unused-parameter -Wbad-function-cast -Wuninitialized -c mdb.c mdb.c: In function mdb_env_setup_locks: mdb.c:4853:17: warning: implicit declaration of function pthread_mutexattr_setrobust [-Wimplicit-function-declaration] if (!rc) rc = pthread_mutexattr_setrobust(&mattr, PTHREAD_MUTEX_ROBUST); ^~~~~~~~~~~~~~~~~~~~~~~~~~~ mdb.c:4853:53: error: PTHREAD_MUTEX_ROBUST undeclared (first use in this function) if (!rc) rc = pthread_mutexattr_setrobust(&mattr, PTHREAD_MUTEX_ROBUST); ^~~~~~~~~~~~~~~~~~~~ mdb.c:4853:53: note: each undeclared identifier is reported only once for each function it appears in mdb.c: In function mdb_mutex_failed: mdb.c:362:37: warning: implicit declaration of function pthread_mutex_consistent [-Wimplicit-function-declaration] #define mdb_mutex_consistent(mutex) pthread_mutex_consistent(mutex) ^ mdb.c:10220:10: note: in expansion of macro mdb_mutex_consistent rc2 = mdb_mutex_consistent(mutex); ^~~~~~~~~~~~~~~~~~~~ make: *** [Makefile:83: mdb.o] Error 1 Anyway to fix this? If this helps, I've noticed that line 4853 for above error has an if check for MDB_ROBUST_SUPPORTED which gets defined on line 278. However the missing declaration of pthread_mutexattr_setrobust is in another if check above line 278.

1 0

Re: (ITS#8506) Authentication issue in ldap client machine after successfully integrating ldap in freenas OS
by quanah＠symas.com 17 Mar '17

17 Mar '17

Hello, There is no evidence of a bug with OpenLDAP based on your report. The OpenLDAP ITS is for bug reports. Usage/configuration questions such as this report should be directed to the OpenLDAP Technical mailing list. <http://www.openldap.org/lists/mm/listinfo/openldap-technical> This ITS will be closed. --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#8614) Test suite fails when using --with-threads=no
by quanah＠symas.com 17 Mar '17

17 Mar '17

--On Friday, March 10, 2017 9:43 PM +0000 bwright(a)intacct.com wrote: > If you plan on retaining --with-threads=no feature, someone might want to > update the test suite to properly test LDAP when threads are disabled. Or > alternatively, inform the user that 'make test' doesn't support testing > LDAP when threads are disabled. Thanks for the report and great suggestion. --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#8500) typo in slapo-ppolicy(5)
by quanah＠symas.com 17 Mar '17

17 Mar '17

--On Monday, September 12, 2016 3:39 PM +0000 michael(a)stroeder.com wrote: Thanks for the report. This was fixed as part of the work on ITS#8185. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

(ITS#8619) Enhancement request: Nested group support using dynlist recursion
by christ.klinge＠web.de 17 Mar '17

17 Mar '17

Full_Name: Christopher Klinge Version: 2.4.44 OS: Debian URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (93.193.142.51) As of right now, dynlist can be used to expand one level of nesting: overlay dynlist dynlist-attrset parentGroup childGroup dn: cn=Parent Group,ou=Groups,dc=example,dc=com objectClass: parentGroup cn: Parent Group childGroupURL: ldap:///cn=Child Group,ou=Groups,dc=example,dc=com?member?sub? dn: cn=Child Group,ou=Groups,dc=example,dc=com objectClass: childGroup cn: Child Group member: cn=User A,ou=People,dc=example,dc=com member: cn=User B,ou=People,dc=example,dc=com member: cn=User B,ou=People,dc=example,dc=com Querying the parent group will return: dn: cn=Parent Group,ou=Groups,dc=example,dc=com objectClass: parentGroup cn: Parent Group childGroupURL: ldap:///cn=Child Group,ou=Groups,dc=example,dc=com?member?sub? member: cn=User A,ou=People,dc=example,dc=com member: cn=User B,ou=People,dc=example,dc=com member: cn=User C,ou=People,dc=example,dc=com If cn=Child Group were to be a parent group itself, no further expansion would take place. I propose enabling dynlist recursion and adding a new configuration directive: dynlist-rec-attrset <group-oc> [<URI>] <URL-ad> <rec-ad> [[<mapped-ad>:]<member-ad>] Except for rec-ad, all parameters behave exactly like those of dynlist-attrset. The attribute rec-ad is mandatory. It is a comma separated list of attributes for which dynlist recursion is enabled. By adding a new directive, backwards compatibility is guaranteed. I suggest using a depth counter to prevent infinite loops. A configurable threshold with a fairly small default value is both light weight and sufficiently rigorous. Logging a suitable warning message upon reaching the threshold would inform the administrator about possible loops.

1 0

Re: (ITS#8465) ldapsearch & slapcat : different output
by quanah＠symas.com 17 Mar '17

17 Mar '17

--On Friday, July 15, 2016 4:15 PM +0000 norbert.massa(a)yopmail.com wrote: > Full_Name: Norbert MASSA > Version: 2.4.40 > OS: CentOS 7.1 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (62.240.254.57) Hi Norbert, There's virtually nothing to go on in this bug report. I.e. no configuration information, etc. What backend were you using (bdb? hdb? mdb?) etc. I'd also note that the ldapsearch you provided would not give a complete backup (It's missing dumps of the operational attributes). --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#8470) LastBind Module Issue
by quanah＠symas.com 17 Mar '17

17 Mar '17

--On Thursday, July 28, 2016 12:59 PM +0000 avijeett007(a)gmail.com wrote: Hello, This does not sound like a report for a bug in the OpenLDAP Software. OpenLDAP does not distribute startup scripts. I would suggest following up with your OS provider, since running slapd manually works as expected. 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#8477) OpenLDAP.org has a broken TLS certificate
by quanah＠symas.com 17 Mar '17

17 Mar '17

--On Thursday, August 11, 2016 5:53 AM +0000 demiobenour(a)gmail.com wrote: > Also, why the self-signed certificate at all? ??Let's Encrypt is > providing free certificates. This should now be fixed. --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#8617) Seg-fault while using meta database and rwm overlay together
by quanah＠symas.com 17 Mar '17

17 Mar '17

--On Wednesday, March 15, 2017 11:51 PM +0000 jaroslaw.wencel(a)gmail.com wrote: > Full_Name: Jaroslaw Wencel > Version: 2.4.42 > OS: Ubuntu 16.04.1 > URL: > Submission from: (NULL) (46.227.243.233) > > > Hi > > I'm trying to develop configuration which includes Active Directory > catalogue into main LDAP tree I have in my configuration. Everything > works well while using slapd-meta as long as I do not try to combine it > with rwm overlay. > > LDAP crashes while invoking modrdn change (refer to attached > crashme.ldif) with the configuration as in config.ldif. > > modrdn change works well until I add dn: > olcOverlay={0}rwm,olcDatabase={1}meta,cn=config to the configuration. > > I'm using OpenLDAP 2.4.42 installed from Ubuntu repositories (latest > version from 16.04.01). > I have uploaded > ftp://ftp.openldap.org/incoming/Jaroslaw-Wencel-170315.tgz to the ftp > server, archive file contains: > - config.ldif - dump of ldap configuration from the moment modrdn > operation crashes the server > - crashme.ldif - the ldif file I'm using for invoking modrdn operation > - crash.logs - slapd daemon log > > Please let me know if you have any further questions Hi, Thanks for the report! There are a number of known existing issues with slapo-rwm, so the detail provided here is quite useful. Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

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