openldap-bugs

openldap-bugs@openldap.org

1 participants
20959 discussions

Re: (ITS#6334) hang during ldapmodify
by hyc＠symas.com 26 Oct '09

26 Oct '09

Mark Dieterich wrote: > Howard, > >> Please try with the latest include/ldap_pvt.h (1.113) and libldap/sasl.c >> (1.74) from CVS, thanks. > > I couldn't get the 2.4.19 stable release to compile with just these few > changes, so I just pulled the entire CVS HEAD. I'm happy to report that > my test case no longer hangs! It looks like you changed the logic to > catch partial writes and this appears to have fixed the error I was seeing. > > So it looks like my issue and the Stanford issue were linked after all. > > Thanks! You're welcome, thanks for your help digging into the problem. -- -- 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#6334) hang during ldapmodify
by mkd＠cs.brown.edu 26 Oct '09

26 Oct '09

Howard, > Please try with the latest include/ldap_pvt.h (1.113) and libldap/sasl.c > (1.74) from CVS, thanks. I couldn't get the 2.4.19 stable release to compile with just these few changes, so I just pulled the entire CVS HEAD. I'm happy to report that my test case no longer hangs! It looks like you changed the logic to catch partial writes and this appears to have fixed the error I was seeing. So it looks like my issue and the Stanford issue were linked after all. Thanks! Mark

1 0

Re: (ITS#6310) Slapd with pcache crashes under load
by hyc＠symas.com 26 Oct '09

26 Oct '09

karavelov(a)spnet.net wrote: > Hello, > The bug seems to be in the new code in pcache overlay handling cache > refreshes. When I switched configuration with only TTL/negTTL (without > TTR) the crashes have disappeared from both scenarios I have used: > > 1. One process with back-sql + pcache (crashed with segmentation failt > when using TTR) > > 2. Two processes, first with back-sql, second with back-ldap + pcache, > that communicate over unix domain socket (crashed on assertion in > entry_clean when using TTR) > > So the bug is not fixed but is located in pcache> consistency_check> > refresh_query A fix was committed to CVS HEAD a few days ago, please test, thanks. -- -- 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#6334) hang during ldapmodify
by hyc＠symas.com 26 Oct '09

26 Oct '09

mkd(a)cs.brown.edu wrote: > Quanah, > > A quick correction... I should have said the operation hangs when I use > SSL. However, I just did a quick test and it also hangs when using TLS > as well. I'm not sure if the underlying mechanism (once security is > enabled with TLS) is actually the same, it appears to be from the packet > dumps, but wanted to make sure I was clear about this. > >> From my testing, the operation needs to utilize TLS or SSL and > SASL/GSSAPI. If I turn off TLS/SSL or use simple binding, everything > works. It's only when I combine all of these mechanisms and use an ldif > file of a certain size (apparently) things start to hang. Please try with the latest include/ldap_pvt.h (1.113) and libldap/sasl.c (1.74) from CVS, thanks. -- -- 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#6327) ldapsearch hangs
by quanah＠zimbra.com 26 Oct '09

26 Oct '09

--On Saturday, October 24, 2009 12:25 AM +0000 quanah(a)zimbra.com wrote: > --On Thursday, October 22, 2009 11:31 PM +0000 quanah(a)zimbra.com wrote: > >> --On Thursday, October 22, 2009 6:16 PM +0000 quanah(a)zimbra.com wrote: >> >>> There's obviously some flaw in length generation somewhere. > > > With changes in HEAD, 3 attr query works, 2 attr query fails. > > SASL/DIGEST-MD5 works regardless. SASL/GSSAPI seems to be the problem > mechanism. Got slapd to output at loglevel 2 today with a freeze: sasl_generic_write: want=78, written=53 0000: 00 00 00 4a 05 04 07 ff 00 00 00 1c 00 00 00 00 ...J............ 0010: e2 10 36 3d 1c 17 41 0e 79 2d 8e b7 a3 19 d3 5c ..6=..A.y-.....\ 0020: 71 b0 7a 94 ab 5a 9d ff b9 31 c3 89 54 18 e6 ab q.z..Z...1..T... 0030: f1 da 10 39 22 ...9" ldap_write: want=14, written=14 0000: 30 0c 02 01 05 65 07 0a 01 00 04 00 04 00 0....e........ --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

[Fwd: Re: [Lam-public] LDAP sizelimit exceeded, not all entries are shown.]
by Roland Gruber 26 Oct '09

26 Oct '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I am the developer of "LDAP Account Manager". One of our users reported a strange problem, maybe you can help here. The application runs the same LDAP search two times. But the second time OpenLDAP returns an error 4 - sizelimit exeeded. The user reported that he removed all sizelimits from slapd.conf and ldap.conf and still gets the error. The log files are attached. These are the two queries: conn=3 op=3 SRCH base="ou=People,dc=example,dc=com" scope=2 deref=3 filter="(&(&(!(uid=*$))(|(objectClass=inetOrgPerson)(objectClass=posixAccount))))" conn=3 op=3 SRCH attr=uid givenname sn uidnumber gidnumber conn=3 op=3 SEARCH RESULT tag=101 err=0 nentries=15 text= conn=4 op=1 SRCH base="ou=People,dc=example,dc=com" scope=2 deref=0 filter="(&(&(!(uid=*$))(|(objectClass=inetOrgPerson)(objectClass=posixAccount))))" conn=4 op=1 SRCH attr=uid givenname sn uidnumber gidnumber conn=4 op=1 SEARCH RESULT tag=101 err=4 nentries=12 text= Any ideas? Thanks a lot for your help. Best regards Roland - -------- Original-Nachricht -------- Betreff: Re: [Lam-public] LDAP sizelimit exceeded, not all entries are shown. Datum: Mon, 12 Oct 2009 15:18:02 +0200 Von: Sou Smith <smith.sou(a)gmail.com> An: Roland Gruber <post(a)rolandgruber.de> Referenzen: <b9082d9f0910070307q7f234632uee4ffa2836c15a04(a)mail.gmail.com> <4ACCD310.50708(a)rolandgruber.de> <b9082d9f0910090227y6d1d0b61k996bbae626426fb3(a)mail.gmail.com> <4ACF4E4B.3010202(a)rolandgruber.de> Hi Roland, I have debugged slapd using loglevel 256. I send you two log files in the attachment. First, slapd.log contains starting slapd, logging in LAM and the first page that LAM shows (User list - showing 15 users). The second file, slapd2.log is extended slapd.log with my click on "Users" (shows only 12 users and the message about sizelimit exceeded) and click on "Groups" (same problem, same number of entries). I have looked into those files, but still don't know where is the problem. Thank you for your time. Best regards, Sou Smith 2009/10/9 Roland Gruber <post(a)rolandgruber.de> > Hi Sou, > > Sou Smith schrieb: >> I have tried to debug slapd, >> while I have tested LAM. I have clicked on "Users" link and after that I >> have looked into log file. I have tried to debug step by step 1- trace >> function calls, 2- debug packet handling, 4- heavy trace debugging, 8- >> connection management, 32- search filter processing, 64- configuration >> processing, 256- stats log connections/operations/results, 512- stats log >> entries sent, 1024- print communication with shell backends, 2048- print >> entry parsing debugging = 10 log files. But I couldn't locate that error > in >> anyone of them. I have tried to debug everything (-d-1 parameter), but > the >> log file was so large and blind, that I haven't found the problem (if > there >> was any). > > you can set slapd to debug mode: > > In /etc/ldap/slapd.conf turn logging on with the line "loglevel 256". > OpenLDAP uses /var/log/syslog for log output. slapd needs to be restarted. > > This should give you all searches done by LAM and the return codes from > slapd. > > - -- Best regards Roland Gruber LDAP Account Manager http://www.ldap-account-manager.org/ Want more? Get LDAP Account Manager Pro! http://www.ldap-account-manager.org/lamcms/lamPro -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkrUw+wACgkQq/ywNCsrGZ43awCfWOWAe49jWNSHW1S3i1rq6V04 YB4AmQH/vVTOOJ8P94nuA6C5aOzJk3cS =h4QQ -----END PGP SIGNATURE-----

3 3

Re: (ITS#6334) hang during ldapmodify
by mkd＠cs.brown.edu 26 Oct '09

26 Oct '09

Quanah, A quick correction... I should have said the operation hangs when I use SSL. However, I just did a quick test and it also hangs when using TLS as well. I'm not sure if the underlying mechanism (once security is enabled with TLS) is actually the same, it appears to be from the packet dumps, but wanted to make sure I was clear about this. >From my testing, the operation needs to utilize TLS or SSL and SASL/GSSAPI. If I turn off TLS/SSL or use simple binding, everything works. It's only when I combine all of these mechanisms and use an ldif file of a certain size (apparently) things start to hang. Clear as mud? Mark Quanah Gibson-Mount wrote: > --On Monday, October 26, 2009 10:49 AM -0400 Mark Dieterich > <mkd(a)cs.brown.edu> wrote: > >> Quanah, >> >> As expected, the 2.4.19 version with the encode.c from HEAD hangs if TLS >> is enabled as well. Not sure where to go from here. > > Does it happen with TLS only, no SASL/GSSAPI? > > --Quanah

1 0

Re: (ITS#6334) hang during ldapmodify
by quanah＠zimbra.com 26 Oct '09

26 Oct '09

--On Monday, October 26, 2009 10:49 AM -0400 Mark Dieterich <mkd(a)cs.brown.edu> wrote: > Quanah, > > As expected, the 2.4.19 version with the encode.c from HEAD hangs if TLS > is enabled as well. Not sure where to go from here. Does it happen with TLS only, no SASL/GSSAPI? --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#6351) memrchr
by quanah＠zimbra.com 26 Oct '09

26 Oct '09

--On Monday, October 26, 2009 1:40 PM +0000 P.Haering(a)gmx.net wrote: > Full_Name: Peter H?ring > Version: 2.4.16 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (95.208.246.19) As noted in ITS#6349, please build a current version of OpenLDAP. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#6334) hang during ldapmodify
by mkd＠cs.brown.edu 26 Oct '09

26 Oct '09

Quanah, As expected, the 2.4.19 version with the encode.c from HEAD hangs if TLS is enabled as well. Not sure where to go from here. Thanks! Mark Quanah Gibson-Mount wrote: > --On Friday, October 23, 2009 4:34 PM +0000 mkd(a)cs.brown.edu wrote: > >> I sure hope these make more sense to you than they do to me! Let me >> know if you need anything else. > > If you can rebuild 2.4.19 with the libraries/liblber/encode.c from HEAD > in place, and then generate the same logs for me (using -d 2 for both > ldapmodify and slapd), but please only use SASL/GSSAPI, not > TLS+SASL/GSSAPI, that would be great. > > Thanks, > Quanah

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