openldap-bugs February 2015

openldap-bugs@openldap.org

28 participants
71 discussions

(ITS#8048) back-sock/slapo-sock issue
by hyc＠openldap.org 03 Feb '15

03 Feb '15

Full_Name: Howard Chu Version: 2.4 OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (110.49.207.42) Submitted by: hyc The result parser is checking for CONTINUE in the wrong place.

1 0

Re: (ITS#8046) query caused slapd to stop
by whm＠stanford.edu 03 Feb '15

03 Feb '15

--On Tuesday, February 03, 2015 12:08:36 AM +0000 Howard Chu <hyc(a)symas.com> wrote: > whm(a)stanford.edu wrote: >> Full_Name: Bill MacAllister >> Version: 2.4.40 >> OS: Debian Wheezy >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (171.64.19.165) >> >> I have a perl script that uses Net::LDAPapi to report data from our >> OpenLDAP servers. I have used the script on an off for years. >> This morning I created a new report this morning that is causing >> slapd on the servers to core dump. When I do the same query using >> ldapsearch the query returns normally. > > What is the query? The filter code where this occurs hasn't changed > in 4 years. > > Provide the slapd -d7 output for the query via your script, as well > as via ldapsearch. The system exhibiting this problem was running a beta release of 2.4.40. When I installed from a build of the current stable the problem disappeared. Apologies for the bother, I didn't realize the system had not been updated. I think that documenting the query would be useful anyway, but I want to hold off on that because I know the problem exists in the build that is in debian backports. I would like to give Ryan a chance to fix it before I publish it. I was able to reproduce the problem with ldapsearch and it is a trival and very effective denial of service attack. Bill -- Bill MacAllister Systems Programmer, Stanford University

1 0

Re: (ITS#8047) TIMEOUT and NETWORK_TIMEOUT don't work properly with SSL
by hyc＠symas.com 03 Feb '15

03 Feb '15

jsynacek(a)redhat.com wrote: > Full_Name: Jan Synacek > Version: 2.4.40 > OS: GNU/Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (213.175.37.10) > > > TIMEOUT and NETWORK_TIMEOUT are not applied when trying to connect to a stalled > server using SSL. The same scenario works when using an unencrypted connection. This is a known issue - we don't have async connect/handshake APIs for these crypto libraries. > > Reproducer: > 1) set up a server for use with SSL (localhost connection is enough) > 2) set NETWORK_TIMEOUT and TIMEOUT in ldap.conf > 3) slapd -u ldap -g ldap -h "ldapi:/// ldaps://localhost" -d1 > 4) verify that connection works > ldapsearch -x -H ldaps://localhost > 5) kill -STOP <server pid> > 6) ldapsearch -x -H ldaps://localhost > At this point, the client hangs and doesn't properly time out. > > For more information including a packet capture, see the original bug report: > https://bugzilla.redhat.com/show_bug.cgi?id=1186562#c4 > > This bug doesn't seem to be crypto library specific. I reproduced it with both > moznss and openssl. > > -- -- 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#8047) TIMEOUT and NETWORK_TIMEOUT don't work properly with SSL
by jsynacek＠redhat.com 03 Feb '15

03 Feb '15

Full_Name: Jan Synacek Version: 2.4.40 OS: GNU/Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (213.175.37.10) TIMEOUT and NETWORK_TIMEOUT are not applied when trying to connect to a stalled server using SSL. The same scenario works when using an unencrypted connection. Reproducer: 1) set up a server for use with SSL (localhost connection is enough) 2) set NETWORK_TIMEOUT and TIMEOUT in ldap.conf 3) slapd -u ldap -g ldap -h "ldapi:/// ldaps://localhost" -d1 4) verify that connection works ldapsearch -x -H ldaps://localhost 5) kill -STOP <server pid> 6) ldapsearch -x -H ldaps://localhost At this point, the client hangs and doesn't properly time out. For more information including a packet capture, see the original bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1186562#c4 This bug doesn't seem to be crypto library specific. I reproduced it with both moznss and openssl.

1 0

Re: (ITS#8046) query caused slapd to stop
by hyc＠symas.com 02 Feb '15

02 Feb '15

whm(a)stanford.edu wrote: > Full_Name: Bill MacAllister > Version: 2.4.40 > OS: Debian Wheezy > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (171.64.19.165) > > > I have a perl script that uses Net::LDAPapi to report data from our OpenLDAP > servers. I have used the script on an off for years. This morning I created a > new report this morning that is causing slapd on the servers to core dump. When > I do the same query using ldapsearch the query returns normally. What is the query? The filter code where this occurs hasn't changed in 4 years. Provide the slapd -d7 output for the query via your script, as well as via ldapsearch. > Here is a backtrace from one of the failures. > > directory5:/root# gdb /usr/sbin/slapd /tmp/core.7494 > GNU gdb (GDB) 7.4.1-debian > Copyright (C) 2012 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "x86_64-linux-gnu". > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>... > Reading symbols from /usr/sbin/slapd...Reading symbols from > /usr/lib/debug/.build-id/82/9f04799686f98a3973283686c94f80c0f4d601.debug...done. > done. > [New LWP 7497] > [New LWP 7496] > [New LWP 7495] > [New LWP 7494] > > warning: Can't read pathname for load map: Input/output error. > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gn2F2Flibthread_db.so.1". > Core was generated by `/usr/sbin/slapd -h ldap:/// ldaps:/// -F > /etc/ldap/slapd.d/'. > Program terminated with signal 6, Aborted. > #0 0x00007ffec956f165 in raise () from /lib/x86_64-linux-gnu/libc.so.6 > (gdb) thr apply all bt > > Thread 4 (Thread 0x7ffecbeac720 (LWP 7494)): > #0 0x00007ffec98d0ee5 in pthread_join () from > /lib/x86_64-linux-gnu/libpthread.so.0 > #1 0x00007ffecb801254 in ldap_pvt_thread_join (thread=140646313764608, > thread_return=0x0) at ../../../../libraries/libldap_r/thr_posix.c:197 > #2 0x00007ffecbf0a21c in slapd_daemon () at > ../../../../servers/slapd/daemon.c:2929 > #3 0x00007ffecbee41dd in main (argc=5, argv=0x7fff8738bda8) at > ../../../../servers/slapd/main.c:1012 > > Thread 3 (Thread 0x7feac5922700 (PWP 7495)): > #0 0x00007ffec9619d63 in epoll_wait () from /lib/x86_64-linux-gnu/libc.so.6 > #1 0x00007ffecbf08dd9 in slapd_daemon_task (ptr=0x7ffecd2a98b8) at > ../../../../servers/slapd/daemon.c:2536 > #2 0x00007ffec98cfb50 in start_thread () from > /lib/x86_64-linux-gnu/libpthread.so.0 > #3 0x00007ffec961970d in clone () from /lib/x86_64-linux-gnu/libc.so.6 > #4 0x0000000000000000 in ?? () > > Thread 2 (Thread 0x7feac5121700 (LWP 7496)): > #0 0x00007ffec98d4344 in pthread_cond_wait@@GLIBC_2.3.2 () from > /lib/x86_64-linux-gnu/libpthread.so.0 > #1 0x00007ffecb801313 in ldap_pvt_thread_cond_wait (cond=0x7ffecd294030, > mutex=0x7ffecd294008) at ../../../../libraries/libldap_r/thr_posix.c:277 > #2 0x00007ffecb7ffc51 in ldap_int_thread_pool_wrapper (xpool=0x7ffecd294000) at > ../../../../libraries/libldap_r/tpool.c:675 > #3 0x00007ffec98cfb50 in start_thread () from > /lib/x86_64-linux-gnu/libpthread.so.0 > #4 0x00007ffec961970d in clone () from /lib/x86_64-linux-gnu/libc.so.6 > #5 0x0000000000000000 in ?? () > > Thread 1 (Thread 0x7feac4920700 (LWP 7497)): > #0 0x00007ffec956f165 in raise () from /lib/x86_64-linux-gnu/libc.so.6 > #1 0x00007ffec95723e0 in abort () from /lib/x86_64-linux-gnu/libc.so.6 > #2 0x00007ffecba631fc in tcmalloc::Log(tcmalloc::LogMode, char const*, int, > tcmalloc::gIgItem, tcmalloc::LogItem, tcmalloc::LogItem, tcmalloc::LogItem) () > from /usr/lib/libtcmalloc_minimal.so.4 > #3 0x00007ffecba5f733 in ?? () from /usr/lib/libtcmalloc_minimal.so.4 > #4 0x00007ffecba6dd90 in tc_free () from /usr/lib/libtcmalloc_minimal.so.4 > #5 0x00007ffecb5e4d01 in ber_memfree_x (p=0x38, ctx=0x0) at > ../../../../libraries/liblber/memory.c:152 > #6 0x00007ffecbf8b575 in slap_sl_free (ptr=0x38, ctx=0x7ffecd334880) at > ../../../../servers/slapd/sl_malloc.c:502 > #7 0x00007ffecbf15c0e in vrFilter_free (op=0x7ffecd317800, vrf=0x7ffecf6a45f0) > at ../../../../servers/slapd/filter.c:1187 > #8 0x00007ffecbf516ca in slap_free_ctrls (op=0x7ffecd317800, > ctrls=0x7ffecf6a4580) at ../../../../servers/slapd/controls.c:574 > #9 0x00007ffecbf2a31d in slap_op_free (op=0x7ffecd317800, ctx=0x7feac491fbb0) > at ../../../../servers/slapd/operation.c:98 > #10 0x00007ffecbf0dbd8 in connection_operation (ctx=0x7feac491fbb0, > arg_v=0x7ffecd317800) at ../../../../servers/slapd/connection.c:1212 > #11 0x00007ffecbf0de95 in connection_read_thread (ctx=0x7feac491fbb0, argv=0xf) > at ../../../../servers/slapd/connection.c:1291 > #12 0x00007ffecb7ffd2b in ldap_int_thread_pool_wrapper (xpool=0x7ffecd294000) at > ../../../../libraries/libldap_r/tpool.c:688 > #13 0x00007ffec98cfb50 in start_thread () from > /lib/x86_64-linux-gnu/libpthread.so.0 > #14 0x00007ffec961970d in clone () from /lib/x86_64-linux-gnu/libc.so.6 > #15 0x0000000000000000 in ?? () > > > -- -- 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#8046) query caused slapd to stop
by whm＠stanford.edu 02 Feb '15

02 Feb '15

Full_Name: Bill MacAllister Version: 2.4.40 OS: Debian Wheezy URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (171.64.19.165) I have a perl script that uses Net::LDAPapi to report data from our OpenLDAP servers. I have used the script on an off for years. This morning I created a new report this morning that is causing slapd on the servers to core dump. When I do the same query using ldapsearch the query returns normally. Here is a backtrace from one of the failures. directory5:/root# gdb /usr/sbin/slapd /tmp/core.7494 GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/sbin/slapd...Reading symbols from /usr/lib/debug/.build-id/82/9f04799686f98a3973283686c94f80c0f4d601.debug...done. done. [New LWP 7497] [New LWP 7496] [New LWP 7495] [New LWP 7494] warning: Can't read pathname for load map: Input/output error. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gn2F2Flibthread_db.so.1". Core was generated by `/usr/sbin/slapd -h ldap:/// ldaps:/// -F /etc/ldap/slapd.d/'. Program terminated with signal 6, Aborted. #0 0x00007ffec956f165 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) thr apply all bt Thread 4 (Thread 0x7ffecbeac720 (LWP 7494)): #0 0x00007ffec98d0ee5 in pthread_join () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007ffecb801254 in ldap_pvt_thread_join (thread=140646313764608, thread_return=0x0) at ../../../../libraries/libldap_r/thr_posix.c:197 #2 0x00007ffecbf0a21c in slapd_daemon () at ../../../../servers/slapd/daemon.c:2929 #3 0x00007ffecbee41dd in main (argc=5, argv=0x7fff8738bda8) at ../../../../servers/slapd/main.c:1012 Thread 3 (Thread 0x7feac5922700 (PWP 7495)): #0 0x00007ffec9619d63 in epoll_wait () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffecbf08dd9 in slapd_daemon_task (ptr=0x7ffecd2a98b8) at ../../../../servers/slapd/daemon.c:2536 #2 0x00007ffec98cfb50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #3 0x00007ffec961970d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #4 0x0000000000000000 in ?? () Thread 2 (Thread 0x7feac5121700 (LWP 7496)): #0 0x00007ffec98d4344 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007ffecb801313 in ldap_pvt_thread_cond_wait (cond=0x7ffecd294030, mutex=0x7ffecd294008) at ../../../../libraries/libldap_r/thr_posix.c:277 #2 0x00007ffecb7ffc51 in ldap_int_thread_pool_wrapper (xpool=0x7ffecd294000) at ../../../../libraries/libldap_r/tpool.c:675 #3 0x00007ffec98cfb50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x00007ffec961970d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x0000000000000000 in ?? () Thread 1 (Thread 0x7feac4920700 (LWP 7497)): #0 0x00007ffec956f165 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffec95723e0 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007ffecba631fc in tcmalloc::Log(tcmalloc::LogMode, char const*, int, tcmalloc::gIgItem, tcmalloc::LogItem, tcmalloc::LogItem, tcmalloc::LogItem) () from /usr/lib/libtcmalloc_minimal.so.4 #3 0x00007ffecba5f733 in ?? () from /usr/lib/libtcmalloc_minimal.so.4 #4 0x00007ffecba6dd90 in tc_free () from /usr/lib/libtcmalloc_minimal.so.4 #5 0x00007ffecb5e4d01 in ber_memfree_x (p=0x38, ctx=0x0) at ../../../../libraries/liblber/memory.c:152 #6 0x00007ffecbf8b575 in slap_sl_free (ptr=0x38, ctx=0x7ffecd334880) at ../../../../servers/slapd/sl_malloc.c:502 #7 0x00007ffecbf15c0e in vrFilter_free (op=0x7ffecd317800, vrf=0x7ffecf6a45f0) at ../../../../servers/slapd/filter.c:1187 #8 0x00007ffecbf516ca in slap_free_ctrls (op=0x7ffecd317800, ctrls=0x7ffecf6a4580) at ../../../../servers/slapd/controls.c:574 #9 0x00007ffecbf2a31d in slap_op_free (op=0x7ffecd317800, ctx=0x7feac491fbb0) at ../../../../servers/slapd/operation.c:98 #10 0x00007ffecbf0dbd8 in connection_operation (ctx=0x7feac491fbb0, arg_v=0x7ffecd317800) at ../../../../servers/slapd/connection.c:1212 #11 0x00007ffecbf0de95 in connection_read_thread (ctx=0x7feac491fbb0, argv=0xf) at ../../../../servers/slapd/connection.c:1291 #12 0x00007ffecb7ffd2b in ldap_int_thread_pool_wrapper (xpool=0x7ffecd294000) at ../../../../libraries/libldap_r/tpool.c:688 #13 0x00007ffec98cfb50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #14 0x00007ffec961970d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #15 0x0000000000000000 in ?? ()

1 0

Re: (ITS#8045) openldap 2.4.39-8.el6: issue causing server unavailability
by Diana.Scannicchio＠cern.ch 02 Feb '15

02 Feb '15

Sorry, duplicated ticket, same as 8044.=20 This can be closed in favour of http://www.OpenLDAP.org/its/index.cgi?find= id=3D8044 Best regards, Diana - Diana Scannicchio University of California, Irvine ATLAS TDAQ SysAdmin group Office: +41 22 76 75240 OnCall: 164851

1 0

Re: (ITS#8044) openldap 2.4.39-8.el6: issue causing server unavailability
by Diana.Scannicchio＠cern.ch 02 Feb '15

02 Feb '15

Should not, I did not enable it in the slapd.conf. Diana On 02 Feb 2015, at 20:34, <michael(a)stroeder.com> <michael(a)stroeder.com> wro= te: > Is SSL/TLS part of the game? >=20 > Ciao, Michael. >=20 >=20 >=20 >=20 - Diana Scannicchio University of California, Irvine ATLAS TDAQ SysAdmin group Office: +41 22 76 75240 OnCall: 164851

1 0

(ITS#8045) openldap 2.4.39-8.el6: issue causing server unavailability
by diana.scannicchio＠cern.ch 02 Feb '15

02 Feb '15

Full_Name: Diana Scannicchio Version: 2.4.39-8.el6 OS: EL6 (SLC6 - Scientific Linux CERN 6) URL: https://scannicc.web.cern.ch/scannicc/openldap/ Submission from: (NULL) (86.209.120.135) Dear experts, I configured 1 LDAP provider and 9 LDAP consumers to serve a large system (~3000 nodes and ~4000 users) and answer thousands of requests. In November 2014 I upgraded the openldap version from 2.4.23-34.el6_5.1 to 2.4.39-8.el6 and we started to experience some issue. We need to regularly modify the LDAP content (e.g. netgroups, sudo rules) and doing it we randomly started to get the message ldapmodify: Server is unavailable (52) and correspondingly in the log on the consumers we find conn=22818341 op=1 ldap_back_retry: retrying URI="ldap://vm-atlas-ldap-1.cern.ch:389" DN="cn=manager,ou=atlas,o=cern,c=ch" slapd[6175]: Error: ldap_back_is_proxy_authz returned 0, misconfigured URI? After some debugging and tests I think that this is due to the connection being closed by the provider tcp 1 0 consumer:36812 provider:ldap CLOSE_WAIT 3254/slapd and the consumers not being able to reconnect at the first request. Indeed when the consumer receives a first request it fails to connect to the provider and it manages to open the connection only at the second request. The connection then stays open if requests are sent continuously and then after 6 minutes (the idletimeout) it is closed by the provider. The fact that each time the first request fails makes the system unusable. I temporary downgraded openldap back to use version 2.4.23-34.el6_5.1 with which, we not not have this issue. Could you please help us in understanding how to fix the issue? and/if I am configuring something wrongly? what has been changed between 2.4.23-34.el6_5.1 to 2.4.39-8.el6? is there some parameter that could be set more properly? You can find the slapd.conf configuration files used for the provider and for the consumers at https://scannicc.web.cern.ch/scannicc/openldap/ Any help and suggestion is very welcome. Please let me know if you need more information. Thank you very much and best regards, Diana P.S. the logs are also filled with slapd[1377]: connection_read(36): no connection! but this was present also with the previous openldap versions...

1 0

Re: (ITS#8044) openldap 2.4.39-8.el6: issue causing server unavailability
by michael＠stroeder.com 02 Feb '15

02 Feb '15

Is SSL/TLS part of the game? Ciao, Michael.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs February 2015