openldap-bugs

openldap-bugs@openldap.org

1 participants
20963 discussions

(ITS#6453) OpenLDAP memory leak on LDAP_TIMEOUT
by alinachegalati＠yahoo.com 13 Jan '10

13 Jan '10

Full_Name: Alin Vasile Version: 2.4.19 OS: Solaris 10 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (194.237.142.7) Hi, We have a memory leak LDAP_TIMEOUT is encountered on ldap_search_ext_invocation and we are unable to determine if it is related to OpenLdap or not. The following summarizes our code in case the LDAP_TIMEOUT response is returned : LDAPMessage *res ; // acquire connection // perform search if(rc == LDAP_TIMEOUT) { ldap_msgfree(res); // return connection } Is ldap_msgfree(res) enough in this case ? We tested our program by enabling a low timeout and hence all ldap calls resulting in timeout. The memory leak is about 9 Megs in several minutes, at a load of 5 req/ sec. dmalloc sees the following not allocated pointers 6642692 bytes : Line 640 of "io.c" starts at address 0xff2659c4 <ber_get_next+468> and ends at 0xff2659cc <ber_get_next+476>. 2019876 bytes : Line 277 of "memory.c" starts at address 0xff26676c <ber_memcalloc_x+132> and ends at 0xff266774 <ber_memcalloc_x+140>.

1 0

Re: (ITS#6452) Able to crash slapd when using identity assertion
by j＠gropefruit.com 12 Jan '10

12 Jan '10

Nevermind, commented out the following in my relay database config area: rwm-rewriteEngine on rwm-normalize-mapped-attrs yes rwm-rewriteContext searchAttrDN rwm-rewriteRule "(.+,)?dc=example,dc=com$" "$1,dc=public,dc=com" No longer crashes. You may close. J On Jan 12, 2010, at 21:39 , openldap-its(a)OpenLDAP.org wrote: > > *** THIS IS AN AUTOMATICALLY GENERATED REPLY *** > > Thanks for your report to the OpenLDAP Issue Tracking System. Your > report has been assigned the tracking number ITS#6452. > > One of our support engineers will look at your report in due course. > Note that this may take some time because our support engineers > are volunteers. They only work on OpenLDAP when they have spare > time. > > If you need to provide additional information in regards to your > issue report, you may do so by replying to this message. Note that > any mail sent to openldap-its(a)openldap.org with (ITS#6452) > in the subject will automatically be attached to the issue report. > > mailto:openldap-its@openldap.org?subject=(ITS#6452) > > You may follow the progress of this report by loading the following > URL in a web browser: > http://www.OpenLDAP.org/its/index.cgi?findid=6452 > > Please remember to retain your issue tracking number (ITS#6452) > on any further messages you send to us regarding this report. If > you don't then you'll just waste our time and yours because we > won't be able to properly track the report. > > Please note that the Issue Tracking System is not intended to > be used to seek help in the proper use of OpenLDAP Software. > Such requests will be closed. > > OpenLDAP Software is user supported. > http://www.OpenLDAP.org/support/ > > -------------- > Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved. >

1 0

(ITS#6452) Able to crash slapd when using identity assertion
by j＠gropefruit.com 12 Jan '10

12 Jan '10

Full_Name: J Version: 2.4.20 OS: Debian-Lenny/amd64 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (68.15.14.98) Able to do all necessary identity assertion when using command-line tools (ldapsearch, ldapmodify, etc) against my server. Server is running back_ldap, back_relay, pcache and back_hdb. But when I point one of my test hosts (Debian Lenny) against this seemingly healthy server and I try to login, I get this while running slapd -d -1: [rw] searchEntryDN: "uid=jay,cn=plain,cn=auth,dc=example,dc=com" -> "uid=jay,cn=plain,cn=auth,dc=example,dc=com" slapd: /usr/src/openldap-src-2.4.20/openldap-2.4.20/servers/slapd/entry.c:483: entry_clean: Assertion `e->e_private == ((void *)0)' failed. Aborted Why?

1 0

(ITS#6449) roadmap update
by quanah＠OpenLDAP.org 12 Jan '10

12 Jan '10

Full_Name: Quanah Gibson-Mount Version: NA OS: NA URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (75.111.29.239) http://www.openldap.org/software/roadmap.html needs to be updated to note that OpenLDAP 2.3 is no longer maintained, same as 2.2 and prior.

1 0

(ITS#6448) BUS Error on Multi Master Mode
by acirulli＠gmail.com 12 Jan '10

12 Jan '10

Full_Name: Andrea Cirulli Version: 2.4.21 OS: Solaris 9 SPARC URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (62.77.56.181) Hi, I have setted up two multimasters in mirror mode. After launching in debug mode with -d 16384 once I stop the slapd ( by CTRL+c ) I obtain a bus error. below the analysis of the core: [New Thread 1 (LWP 1)] Loaded symbols for /usr/lib/64//libthread.so.1 warning: Can't read pathname for load map: I/O error. warning: Can't read pathname for load map: I/O error. Core was generated by `libexec/slapd -f etc/openldap/slapd.conf -h ldap://:379 -d 16384'. Program terminated with signal 10, Bus error. #0 0x00000001001fb8f4 in avl_free () (gdb) thread apply all bt full Thread 2 (Thread 1 (LWP 1)): #0 0x00000001001fb8f4 in avl_free () No symbol table info available. #1 0x0000000100185ef0 in ?? () No symbol table info available. #2 0x0000000100185ef0 in ?? () No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 1 (LWP 1 ): #0 0x00000001001fb8f4 in avl_free () No symbol table info available. #1 0x0000000100185ef0 in ?? () No symbol table info available. #2 0x0000000100185ef0 in ?? () No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?)

1 0

RE: (ITS#6447) Can't compile openldap with --enable-dynamic on solari sparc 10
by Biren.Patel＠directbrands.com 11 Jan '10

11 Jan '10

Please close this issue, it has been resolved. Thanks -----Original Message----- From: openldap-its(a)OpenLDAP.org [mailto:openldap-its@OpenLDAP.org]=20 Sent: Monday, January 11, 2010 10:31 AM To: Patel, Biren - Direct Brands Subject: Re: (ITS#6447) Can't compile openldap with --enable-dynamic on so= lari sparc 10 *** THIS IS AN AUTOMATICALLY GENERATED REPLY *** Thanks for your report to the OpenLDAP Issue Tracking System. Your report has been assigned the tracking number ITS#6447. One of our support engineers will look at your report in due course. Note that this may take some time because our support engineers are volunteers. They only work on OpenLDAP when they have spare time. If you need to provide additional information in regards to your issue report, you may do so by replying to this message. Note that any mail sent to openldap-its(a)openldap.org with (ITS#6447) in the subject will automatically be attached to the issue report. =09mailto:openldap-its@openldap.org?subject=3D(ITS#6447) You may follow the progress of this report by loading the following URL in a web browser: http://www.OpenLDAP.org/its/index.cgi?findid=3D6447 Please remember to retain your issue tracking number (ITS#6447) on any further messages you send to us regarding this report. If you don't then you'll just waste our time and yours because we won't be able to properly track the report. Please note that the Issue Tracking System is not intended to be used to seek help in the proper use of OpenLDAP Software. Such requests will be closed. OpenLDAP Software is user supported. =09http://www.OpenLDAP.org/support/ -------------- Copyright 1998-2007 The OpenLDAP Foundation, All Rights Reserved. ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email=20 ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email=20 ______________________________________________________________________

1 0

Re: (ITS#6444) OpenLDAP 2.5 RoadMap Question
by michael＠stroeder.com 11 Jan '10

11 Jan '10

j(a)gropefruit.com wrote: > Please clarify this statement in your 2.5 roadmap: Any reason why you didn't simply post this to the openldap-software mailing list? > LDAPv3 extensions: > *LDAP Transaction support AFAIK this means implementing draft-zeilenga-ldap-txn http://tools.ietf.org/draft/draft-zeilenga-ldap-txn/ Ciao, Michael.

1 0

Re: (ITS#6444) OpenLDAP 2.5 RoadMap Question
by quanah＠zimbra.com 11 Jan '10

11 Jan '10

--On Wednesday, January 06, 2010 11:49 PM +0000 j(a)gropefruit.com wrote: > Full_Name: J > Version: 2.4.20 > OS: Debian/Lenny-AMD64 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (207.67.92.30) > > > Please clarify this statement in your 2.5 roadmap: This is not a bug report. If you have development questions, please send them to openldap-devel(a)openldap.org for discussion. Thanks! This ITS will be closed. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#6447) Can't compile openldap with --enable-dynamic on solari sparc 10
by biren.patel＠directbrands.com 11 Jan '10

11 Jan '10

Full_Name: Biren Patel Version: openldap-2.4.19 OS: SPARC Solaris 10 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (216.223.34.13) I can't compile openldap with option --enable-dynamic on SPARC Solaris 10. Receiving the error provided below. It complies fine without the --enable-dynamic but when complie PHP 5 with ldap, PHP gives me the same error. I have norrowed down to Openldap not able to compile all the libs as dynamic loadable. Please help Using gcc. Reading specs from /usr/local/lib/gcc/sparc-sun-solaris2.10/3.4.6/specs Configured with: ../configure --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --enable-shared --enable-languages=c,c++,f77 Thread model: posix gcc version 3.4.6 /bin/sh ../../libtool --mode=link gcc -D_AVL_H -L/usr/local/openssl/lib/ -L/usr/local/BerkeleyDB/lib -L/usr/local/lib/ -R/usr/local/BerkeleyDB/lib -R/usr/local/lib -o apitest apitest.o libldap.la ../../libraries/liblber/liblber.la ../../libraries/liblutil/liblutil.a -lsasl -lssl -lcrypto -lresolv -lgen -lnsl -lsocket gcc -D_AVL_H -o .libs/apitest apitest.o -L/usr/local/openssl/lib/ -L/usr/local/BerkeleyDB/lib -L/usr/local/lib/ ./.libs/libldap.so /u/bpatel/openldap-2.4.21/libraries/liblber/.libs/liblber.so ../../libraries/liblber/.libs/liblber.so ../../libraries/liblutil/liblutil.a -lsasl -lssl -lcrypto -lresolv -lgen -lnsl -lsocket -Wl,--rpath -Wl,/usr/local/openldap/lib -Wl,--rpath -Wl,/usr/local/BerkeleyDB/lib -Wl,--rpath -Wl,/usr/local/lib /usr/ccs/bin/ld: ./.libs/libldap.so: dlclose: invalid version 13 (max 0) ./.libs/libldap.so: could not read symbols: Bad value collect2: ld returned 1 exit status make[2]: *** [apitest] Error 1 make[2]: Leaving directory `/u/bpatel/openldap-2.4.21/libraries/libldap' make[1]: *** [all-common] Error 1 make[1]: Leaving directory `/u/bpatel/openldap-2.4.21/libraries' make: *** [all-common] Error 1

1 0

Re: (ITS#6446) Quickstart guide only uses slapd.conf
by gavin.henry＠gmail.com 07 Jan '10

07 Jan '10

Will update. Thanks! On 07/01/2010, quanah(a)openldap.org <quanah(a)openldap.org> wrote: > Full_Name: Quanah Gibson-Mount > Version: RE24 > OS: NA > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (75.111.29.239) > > > The quickstart guide on the OpenLDAP home page only references using > slapd.conf. > It has no references to the new config backend. Since slapd.conf is > deprecated, it would be good to have a quickstart guide that reflected this. > -- Sent from my mobile device http://www.suretecsystems.com/services/openldap/ http://www.suretectelecom.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