openldap-bugs

openldap-bugs@openldap.org

1 participants
20967 discussions

(ITS#5508) slapd process consumes all of CPU
by whm＠stanford.edu 12 May '08

12 May '08

Full_Name: Bill MacAllister Version: 2.3.41-1su2 OS: debian etch kernel 2.6.18-4-amd64 URL: http://www.stanford.edu/~whm/ldap-test1-bt.txt Submission from: (NULL) (171.64.19.165) The slapd process will sometimes consume all of available CPU. We observed this when we upgraded our production servers from 2.3.35-2su2 to 2.3.41-1su2. The problem was bad enough that we downgraded the production servers to 2.3.35-2su2. We have been trying to provoke the problem in our test environment and have not been successful in making it happen on demand. Today, we noticed that one of our test servers went completely CPU bound. I took a backtrace. It is available at the URL below. The interesting thing about the problem is that although top shows a pinned CPU and a high load the server is still responsive and continues to answer LDAP searches. The test server that exhibits the problem is still CPU bound and has been for 2-3 hours now. We will leave this server in this state in case there is other information that we should harvest in resolving the problem.

1 0

Re: (ITS#5506) syncprov crash with RE24 CVS
by hyc＠symas.com 12 May '08

12 May '08

mark.cave-ayland(a)siriusit.co.uk wrote: > Full_Name: Mark Cave-Ayland > Version: 2.4.8cvs-RE24-2008-05-06 > OS: RHEL4, x86 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (217.207.197.142) > > > Hi there, > > We've located another segfault in openldap 2.4.8cvs RE24 branch when using > syncprov, possibly similar in nature to ITS#5486. 2.4.9 was released on May 6; that's the base version you should be using at this point. > Details from the slapd log and the gdb core file can be found here: > http://pastebin.siriusit.co.uk/openldap-bug-20080512.txt A patch is now in HEAD for this. Please test. -- -- 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

(ITS#5507) Ldap clients leak file descriptors
by jsafrane＠redhat.com 12 May '08

12 May '08

Full_Name: Jan Safranek Version: 2.4.9 OS: Linux (Fedora 8) URL: Submission from: (NULL) (62.40.79.66) On system protected by SELinux, when an application with active LDAP connection tries to exec() binary with different security context, SELinux inspects all opened filedescriptors, including the ldap one, and denies access to the ones, which do not conform active policy (the executed binary is not authorized to contact LDAP servers). Users are then annoyed by security warnings in the logs. There is simple fix - set CLOEXEC flag on the socket, which will force the filedescriptor to close on exec(), see patch below. --- a/libraries/libldap/os-ip.c +++ b/libraries/libldap/os-ip.c @@ -36,6 +36,9 @@ #ifdef HAVE_IO_H #include <io.h> #endif /* HAVE_IO_H */ +#ifdef HAVE_FCNTL_H +#include <fcntl.h> +#endif #include "ldap-int.h" @@ -110,6 +113,9 @@ ldap_int_socket(LDAP *ld, int family, int type ) { ber_socket_t s = socket(family, type, 0); osip_debug(ld, "ldap_new_socket: %d\n",s,0,0); +#ifdef _GNU_SOURCE + fcntl(s, F_SETFD, FD_CLOEXEC); +#endif return ( s ); }

1 0

(ITS#5506) syncprov crash with RE24 CVS
by mark.cave-ayland＠siriusit.co.uk 12 May '08

12 May '08

Full_Name: Mark Cave-Ayland Version: 2.4.8cvs-RE24-2008-05-06 OS: RHEL4, x86 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (217.207.197.142) Hi there, We've located another segfault in openldap 2.4.8cvs RE24 branch when using syncprov, possibly similar in nature to ITS#5486. Details from the slapd log and the gdb core file can be found here: http://pastebin.siriusit.co.uk/openldap-bug-20080512.txt More information from the gdb core file can be obtained upon request. Many thanks, Mark.

1 0

Re: (ITS#5505) Attribute value for 'modifiersName' in case of overlays
by ando＠sys-net.it 10 May '08

10 May '08

> Just a feature request for convenience: > > Would it be possible to set the value of attribute 'modifiersName' to the > DN of > the overlays' configuration entry under cn=config if an entry was modified > by an > overlay? In this case one would have a direct link to the configuration if > needed. Currently 'cn=<overlay name>' (e.g cn=Referential Integrity > Overlay) is > added which does not refer to an existing entry at all. Technically, I don't see any problem, except that overlays (and software modules, in general) do not hold a direct reference to their config entry's DN, if any (e.g. when back-config is not in use, the data structure is in place, but not in LDIF form; please correct me if I'm wrong). I wonder whether exposing such detail makes sense, or risks breaking any security. Probably I'm getting paranoid... p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

(ITS#5505) Attribute value for 'modifiersName' in case of overlays
by michael＠stroeder.com 10 May '08

10 May '08

Full_Name: Michael Ströder Version: HEAD OS: OpenSUSE Linux 10.2 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (84.163.119.62) HI! Just a feature request for convenience: Would it be possible to set the value of attribute 'modifiersName' to the DN of the overlays' configuration entry under cn=config if an entry was modified by an overlay? In this case one would have a direct link to the configuration if needed. Currently 'cn=<overlay name>' (e.g cn=Referential Integrity Overlay) is added which does not refer to an existing entry at all. Ciao, Michael.

1 0

Re: (ITS#5503) Openldap segmentation fault when running syncrepl.
by hyc＠symas.com 10 May '08

10 May '08

chuck.short(a)canonical.com wrote: > Howard Chu wrote: >> zulcss(a)ubuntu.com wrote: >>> Full_Name: Chuck Short >>> Version: 2.4.9 >>> OS: Linux >>> URL: ftp://ftp.openldap.org/incoming/ >>> Submission from: (NULL) (99.224.150.216) >>> >>> >>> When running the following scripts openldap crashes when trying to run a >>> syncrepl from a slave server. The original bug report can be found at: >>> http://bugs.launchpad.net/bugs/227178. >>> >>> Steps to reproduce it: >>> >>> 1. Download the attachment in the bug report. >>> 2. mkdir /home/amg1127/ >>> 3. Unpack the attachment in the just created directory. >>> 4. Run the ./create-master-base.sh script. >>> 5. In one terminal run the run-master-slapd.sh script. >>> 6. In another terminal create the run-slave-slapd.sh script. >>> 7. The result will be a segmentation fault in the slave server. >>> >>> Thanks >>> chuck >> Thanks for the report, too bad you didn't forward it to us sooner. >> This is now fixed in CVS HEAD. >> > I backported the patch and was still able to reproduce the crash. Backported to 2.4.7? I see no crash with the patch applied to 2.4.9. If you're using 2.4.9, please post your backtrace. -- -- 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#5503) Openldap segmentation fault when running syncrepl.
by chuck.short＠canonical.com 10 May '08

10 May '08

Howard Chu wrote: > zulcss(a)ubuntu.com wrote: >> Full_Name: Chuck Short >> Version: 2.4.9 >> OS: Linux >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (99.224.150.216) >> >> >> When running the following scripts openldap crashes when trying to run a >> syncrepl from a slave server. The original bug report can be found at: >> http://bugs.launchpad.net/bugs/227178. >> >> Steps to reproduce it: >> >> 1. Download the attachment in the bug report. >> 2. mkdir /home/amg1127/ >> 3. Unpack the attachment in the just created directory. >> 4. Run the ./create-master-base.sh script. >> 5. In one terminal run the run-master-slapd.sh script. >> 6. In another terminal create the run-slave-slapd.sh script. >> 7. The result will be a segmentation fault in the slave server. >> >> Thanks >> chuck > > Thanks for the report, too bad you didn't forward it to us sooner. > This is now fixed in CVS HEAD. > I backported the patch and was still able to reproduce the crash. Thanks chuck

1 0

Re: (ITS#5504) ldapsearch hangs retrieving info
by hyc＠symas.com 09 May '08

09 May '08

Javier.Fernandez(a)cern.ch wrote: > Full_Name: Javier Fernandez > Version: 2.2.13 > OS: SL4 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (156.35.192.4) OpenLDAP 2.2 was moved to Historical status a few years ago. Upgrade to a current supported release if you want anyone to look into this. > > Hi, > ldapsearch gets stuck retrieving info and after some minutes the following error > message is thrown: > ldap_result: Can't contact LDAP server (-1) > > I'm using: > ldapsearch -V > ldapsearch: @(#) $OpenLDAP: ldapsearch 2.2.13 (May 3 2007 03:01:11) $ > root@lxcert-amd64:/scratch/rpmbuild.7430.xx7460/openldap-2.2.13/openldap-2.2.13/build-clients/clients/tools > (LDAP library: OpenLDAP 20213) > > under > Linux 2.6.9-55.EL.cernsmp #1 SMP Thu May 10 18:09:56 CEST 2007 x86_64 x86_64 > x86_64 GNU/Linux > > Things used to work until one day when it began to give problems, so it could be > a site network port filtering problem, but our network administrator does not > know how to debug, so we would need any hint on how to trace back the problem. > > The command, which starts working but after some time gets stuck, is: > > ldapsearch -p 2170 -h exp-bdii.cern.ch -x -LLL -b "o=grid" -d -1 > > Of course, we CAN do a telnet on that port and that host. Any help is really > welcome and apreciated. Here is a snippet from the output of the command: -- -- 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#5503) Openldap segmentation fault when running syncrepl.
by hyc＠symas.com 09 May '08

09 May '08

zulcss(a)ubuntu.com wrote: > Full_Name: Chuck Short > Version: 2.4.9 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (99.224.150.216) > > > When running the following scripts openldap crashes when trying to run a > syncrepl from a slave server. The original bug report can be found at: > http://bugs.launchpad.net/bugs/227178. > > Steps to reproduce it: > > 1. Download the attachment in the bug report. > 2. mkdir /home/amg1127/ > 3. Unpack the attachment in the just created directory. > 4. Run the ./create-master-base.sh script. > 5. In one terminal run the run-master-slapd.sh script. > 6. In another terminal create the run-slave-slapd.sh script. > 7. The result will be a segmentation fault in the slave server. > > Thanks > chuck Thanks for the report, too bad you didn't forward it to us sooner. This is now fixed in CVS HEAD. -- -- 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