openldap-bugs February 2008

openldap-bugs@openldap.org

42 participants
207 discussions

RE: (ITS#5336)
by quanah＠zimbra.com 15 Feb '08

15 Feb '08

A similar bug has been reported in the debian bug tracking system, with some debugging information and reproducibility steps. <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465915> --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#5381) ldap_result error
by hyc＠symas.com 15 Feb '08

15 Feb '08

fabio.ubaldi(a)coritel.it wrote: > Full_Name: Fabio Ubaldi > Version: 2.3.27 > OS: Linux kernel 2.6.18 > URL: > Submission from: (NULL) (194.237.142.11) > It seems that the error happens only if the two process runs > simultaneously (I use a dual core PC). Thinking of a race condition > error , I used the libldap_r library to build process, but the error > still remains. Processes are completely separate (unless you happen to be using explicitly shared memory). It's pretty much impossible for any code in libldap to be directly responsible for the behavior you're reporting. If you're using a new socket for each request and not closing them when done, it's likely that you're running out of free ports in your system. > The openldap version is 2.3.27 both for slapd servers and the libraries. > > Have anyone encountered a similar error ? > > Thanks in advance for the reply There is no indication of a bug in OpenLDAP Software here. This ITS will be closed. Since it's most likely an issue in how you coded your application, you can followup to the OpenLDAP-software mailing list if you want to discuss this further. -- -- Howard Chu Chief Architect, 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#5369) GSSAPI support for client library
by kurt＠OpenLDAP.org 15 Feb '08

15 Feb '08

I note that the patch appears to be incomplete. No gssapi.c included. -- Kurt On Feb 14, 2008, at 8:26 PM, kurt(a)openldap.org wrote: > You've only included one of the two required statements. You need > also need to include either a copyright + license statement, or a > public domain release statement. -- Kurt > > On Feb 14, 2008, at 9:12 AM, mimir(a)samba.org wrote: > >> >> --OgqxwSJOaUobr8KG >> Content-Type: text/plain; charset=iso-8859-2 >> Content-Disposition: inline >> Content-Transfer-Encoding: quoted-printable >> >> Kurt, >> >> On Mon, Feb 11, 2008 at 09:06:19AM -0800, Kurt Zeilenga wrote: >>>> Full_Name: Rafal Szczesniak >>>> Version: HEAD >>>> OS: GNU/Linux >>>> URL: http://www.samba.org/~mimir/gssapi-head.diff >>> >>> The submitted patch file does not contain (at the top of the file, >>> not = >> =20 >>> as part of the diffs) the required notices. Please review=20 >>> http://www.openldap.org/devel/contributing.html and insert >>> appropriate=20 >>> notices. Also, please don't include in the diffs derived files >>> (e.g.,=20 >>> configure). >> >> I've updated the patch file with necessary changes. Please take a >> look >> if it's fine now. >> >> >> cheers, >> --=20 >> Rafal Szczesniak >> Samba Team member http://www.samba.org >> Likewise Software http://www.likewisesoftware.com >> >> >> --OgqxwSJOaUobr8KG >> Content-Type: application/pgp-signature; name="signature.asc" >> Content-Description: Digital signature >> Content-Disposition: inline >> >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.6 (GNU/Linux) >> >> iD8DBQFHtJLCHvdfyv3qiKkRArL0AJ9ZazJE3LUduZb3A8rz21KheW/EYQCfQt8z >> F7AnIDF5EkJ7ssDwHStryEo= >> =tIVf >> -----END PGP SIGNATURE----- >> >> --OgqxwSJOaUobr8KG-- >> >> > >

1 0

(ITS#5382) JLDAP
by jim＠willeke.com 15 Feb '08

15 Feb '08

Full_Name: Jim Willeke Version: N/A OS: Several URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (67.76.26.2) This code: String o1="cn=admin, ou=marketing, o=corporation"; String o2="ou=marketing, o=corporation"; DN dn1 = new DN(o1.toString()); DN dn2 = new DN(o2.toString()); if(dn1.isDescendantOf(dn2)) { System.out.println(dn1 + " isDescendantOf "+ dn2); } if(dn2.isDescendantOf(dn1)) { System.out.println(dn2 + " isDescendantOf "+ dn1); } o1="ou=marketing, o=corporation"; o2="cn=admin, ou=marketing, o=corporation"; dn1 = new DN(o1.toString()); dn2 = new DN(o2.toString()); if(dn1.isDescendantOf(dn2)) { System.out.println(dn1 + " isDescendantOf "+ dn2); } if(dn2.isDescendantOf(dn1)) { System.out.println(dn2 + " isDescendantOf "+ dn1); } Yields these results: ou=marketing,o=corporation isDescendantOf cn=admin,ou=marketing,o=corporation ou=marketing,o=corporation isDescendantOf cn=admin,ou=marketing,o=corporation Sure looks wrong to me.

1 0

Re: (ITS#5380) master slapd hangs when writing
by quanah＠zimbra.com 15 Feb '08

15 Feb '08

--On Friday, February 15, 2008 10:34 AM +0000 ali.pouya(a)free.fr wrote: > Full_Name: Ali Pouya > Version: 2.3.36 > OS: Linux 2.6 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (145.242.11.4) > > > My directory is formed with 4 servers syncronized through syncrepl > (RefreshAndPersist). > THe directory contains about 10 million entries in the BDB back-end. > My slapd servers are configured with the default 16 threads. > I have a JAVA injector for write operations. The injector establishes 28 > connections to the master and writes about 1400 entries per minute. > > After several hours of activity the master hangs. It accepts TCP > connections but does not handle LDAP operations. LDAP requests remain > hanged until interruption by the client. The replicas are OK. strace is useless. Please get a backtrace of all the threads using gdb. Make sure you compiled with debugging symbols, and that slapd is not stripped. I'd also advise getting a backtrace on a current release, as there have been a number of race conditions and cleanup fixes made since 2.3.36. You may want to wait on 2.3.41 which will be released in the next few days. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

(ITS#5381) ldap_result error
by fabio.ubaldi＠coritel.it 15 Feb '08

15 Feb '08

Full_Name: Fabio Ubaldi Version: 2.3.27 OS: Linux kernel 2.6.18 URL: Submission from: (NULL) (194.237.142.11) Hi all, I have two processes running on the same PC that receive data from an LDAP server. Each process opens a connection with a different "slapd" server (i.e each server runs on a different PC) and launches "search" requests at a fixed rate (about 100 searches/s). Each process creates a thread that polls the server responses using the API "ldap_result" the used macro are LDAP_RES_ANY and LDAP_MSG_ONE. When the two processes send the requestes one of the two "ldap_result" return with error (-1) and the error is "Can't contact the LDAP server". I tried to launch one processes and it works fine (the maximum measured rate is 800 searches/s). Also I launch the two processes alternating the search requestes and it works fine. It seems that the error happens only if the two process runs simultaneously (I use a dual core PC). Thinking of a race condition error , I used the libldap_r library to build process, but the error still remains. The openldap version is 2.3.27 both for slapd servers and the libraries. Have anyone encountered a similar error ? Thanks in advance for the reply

1 0

(ITS#5380) master slapd hangs when writing
by ali.pouya＠free.fr 15 Feb '08

15 Feb '08

Full_Name: Ali Pouya Version: 2.3.36 OS: Linux 2.6 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (145.242.11.4) My directory is formed with 4 servers syncronized through syncrepl (RefreshAndPersist). THe directory contains about 10 million entries in the BDB back-end. My slapd servers are configured with the default 16 threads. I have a JAVA injector for write operations. The injector establishes 28 connections to the master and writes about 1400 entries per minute. After several hours of activity the master hangs. It accepts TCP connections but does not handle LDAP operations. LDAP requests remain hanged until interruption by the client. The replicas are OK. Is this problem already known ? I checked the CHANGES file for the 2.3.40 release and did not find any trace of a known problem. I used strace to see what slapd does at hang (freeze) situation. It shows an infinite epoll loop in one of the threads. I reproduce the result at the end of this ITS. Thanks for your help Best regards Ali ==================== The strace result : Process 16970 attached with 18 threads - interrupt to quit [pid 16601] futex(0xa341abf8, FUTEX_WAIT, 16625, NULL <unfinished ...> [pid 16625] time( <unfinished ...> [pid 16626] futex(0xb7f4d3d0, FUTEX_WAIT, 9, NULL <unfinished ...> [pid 16627] futex(0xb7f4c110, FUTEX_WAIT, 21, NULL <unfinished ...> [pid 20161] futex(0xb7f53708, FUTEX_WAIT, 3, NULL <unfinished ...> [pid 20162] futex(0xb7f4c9a8, FUTEX_WAIT, 19, NULL <unfinished ...> [pid 31353] futex(0xb7f4b5bc, FUTEX_WAIT, 11, NULL <unfinished ...> [pid 31354] futex(0xb7f4980c, FUTEX_WAIT, 1, NULL <unfinished ...> [pid 31355] futex(0xb7f4d178, FUTEX_WAIT, 11, NULL <unfinished ...> [pid 2229] futex(0xb7f4fd9c, FUTEX_WAIT, 1, NULL <unfinished ...> [pid 2241] futex(0xb7f48cb8, FUTEX_WAIT, 5, NULL <unfinished ...> [pid 2242] futex(0xb7f50440, FUTEX_WAIT, 3, NULL <unfinished ...> [pid 2243] futex(0xb7f49d20, FUTEX_WAIT, 17, NULL <unfinished ...> [pid 16228] futex(0xb7f523e4, FUTEX_WAIT, 17, NULL <unfinished ...> [pid 16899] futex(0xb7f500bc, FUTEX_WAIT, 19, NULL <unfinished ...> [pid 16916] futex(0xb7f4aa04, FUTEX_WAIT, 29, NULL <unfinished ...> [pid 16969] futex(0xb7f52060, FUTEX_WAIT, 23, NULL <unfinished ...> [pid 16970] futex(0xb7f4c87c, FUTEX_WAIT, 27, NULL <unfinished ...> [pid 16625] <... time resumed> NULL) = 1203063506 [pid 16625] epoll_wait(6, {{EPOLLERR|EPOLLHUP, {u32=153710248, u64=153710248}}, {EPOLLERR|EPOLLHUP, {u32=153710244, u64=15371 0244}}, {EPOLLERR|EPOLLHUP, {u32=153710232, u64=153710232}}, {EPOLLERR|EPOLLHUP, {u32=153710220, u64=153710220}}, {EPOLLERR|E POLLHUP, {u32=153710204, u64=153710204}}, {EPOLLERR|EPOLLHUP, {u32=153710196, u64=153710196}}, {EPOLLERR|EPOLLHUP, {u32=15371 0224, u64=153710224}}, {EPOLLERR|EPOLLHUP, {u32=153710192, u64=153710192}}, {EPOLLERR|EPOLLHUP, {u32=153710180, u64=153710180 }}, {EPOLLERR|EPOLLHUP, {u32=153710176, u64=153710176}}, {EPOLLERR|EPOLLHUP, {u32=153710164, u64=153710164}}, {EPOLLERR|EPOLL HUP, {u32=153710160, u64=153710160}}, {EPOLLERR|EPOLLHUP, {u32=153710144, u64=153710144}}, {EPOLLERR|EPOLLHUP, {u32=153710140 , u64=153710140}}, {EPOLLERR|EPOLLHUP, {u32=153710128, u64=153710128}}, {EPOLLERR|EPOLLHUP, {u32=153710116, u64=153710116}}, {EPOLLERR|EPOLLHUP, {u32=153710108, u64=153710108}}, {EPOLLERR|EPOLLHUP, {u32=153710104, u64=153710104}}, {EPOLLERR|EPOLLHUP, {u32=153710100, u64=153710100}}, {EPOLLERR|EPOLLHUP, {u32=153710096, u64=153710096}}, {EPOLLERR|EPOLLHUP, {u32=153710092, u6 4=153710092}}, {EPOLLERR|EPOLLHUP, {u32=153710088, u64=153710088}}, {EPOLLERR|EPOLLHUP, {u32=153710080, u64=153710080}}, {EPO LLERR|EPOLLHUP, {u32=153710068, u64=153710068}}, {EPOLLERR|EPOLLHUP, {u32=153710056, u64=153710056}}, {EPOLLERR|EPOLLHUP, {u3 2=153710052, u64=153710052}}, {EPOLLERR|EPOLLHUP, {u32=153710048, u64=153710048}}, {EPOLLERR|EPOLLHUP, {u32=153710044, u64=15 3710044}}, {EPOLLERR|EPOLLHUP, {u32= ..........

1 0

ITS#5375
by ecizaguirre＠gmv.com 15 Feb '08

15 Feb '08

Hi Pierangelo, the patch corrects the issue in the current CVS of REL_ENG_2_4 and now is working correctly. I will test the system with more workload. The make phase fails with the following error after applying the patch to 2.4.7 release: cd back-meta; make all rm -f version.c ../../../build/mkversion -v "2.4.7" back_meta > version.c /bin/sh ../../..//libtool --tag=disable-shared --mode=compile gcc -m64 -D_AVL_H -g -I../../../include -I../../../include -I.. -I./.. -I/opt/db-4.5.20/include -I/opt/openssl-0.9.8d/include -c init.c gcc -m64 -D_AVL_H -g -I../../../include -I../../../include -I.. -I./.. -I/opt/db-4.5.20/include -I/opt/openssl-0.9.8d/include -c init.c -o init.o /bin/sh ../../..//libtool --tag=disable-shared --mode=compile gcc -m64 -D_AVL_H -g -I../../../include -I../../../include -I.. -I./.. -I/opt/db-4.5.20/include -I/opt/openssl-0.9.8d/include -c config.c gcc -m64 -D_AVL_H -g -I../../../include -I../../../include -I.. -I./.. -I/opt/db-4.5.20/include -I/opt/openssl-0.9.8d/include -c config.c -o config.o /bin/sh ../../..//libtool --tag=disable-shared --mode=compile gcc -m64 -D_AVL_H -g -I../../../include -I../../../include -I.. -I./.. -I/opt/db-4.5.20/include -I/opt/openssl-0.9.8d/include -c search.c gcc -m64 -D_AVL_H -g -I../../../include -I../../../include -I.. -I./.. -I/opt/db-4.5.20/include -I/opt/openssl-0.9.8d/include -c search.c -o search.o search.c: In function `meta_back_search_start': search.c:627: error: structure has no member named `mi_ldap_extra' search.c:644: error: structure has no member named `mi_ldap_extra' *** Error code 1 make: Fatal error: Command failed for target `search.lo' Current working directory /opt/software/fuentes/openldap-2.4.7/servers/slapd/back-meta *** Error code 1 The following command caused the error: if test -n "back-ldif back-monitor back-bdb back-hdb back-ldap back-meta back-relay"; then \ echo "building static backends..."; \ for i in XX back-ldif back-monitor back-bdb back-hdb back-ldap back-meta back-relay; do \ if test $i != XX; then \ echo " "; echo " cd $i; make all"; \ ( cd $i; make all ); \ if test $? != 0; then exit 1; fi; \ fi; \ done; \ echo " "; \ fi make: Fatal error: Command failed for target `.backend' Current working directory /opt/software/fuentes/openldap-2.4.7/servers/slapd *** Error code 1 The following command caused the error: for i in slapd ; do \ echo " Entering subdirectory $i"; \ ( cd $i; make all ); \ if test $? != 0 ; then exit 1; fi ; \ echo " "; \ done make: Fatal error: Command failed for target `all-common' Current working directory /opt/software/fuentes/openldap-2.4.7/servers *** Error code 1 The following command caused the error: for i in include libraries clients servers tests doc ; do \ echo " Entering subdirectory $i"; \ ( cd $i; make all ); \ if test $? != 0 ; then exit 1; fi ; \ echo " "; \ done make: Fatal error: Command failed for target `all-common' Thanks for the fix. Cheers. Eduardo. ________________________________ Eduardo Izaguirre Pazos Administrador de Sistemas / Systems Administrator GRUPO TECNOLÓGICO E INDUSTRIAL GMV,S.A. Isaac Newton, 11 P.T.M. Tres Cantos E-28760 Madrid Tel. +34 91 807 21 00 Fax +34 91 807 21 99 www.gmv.com ______________________ Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede contener informacion clasificada por su emisor como confidencial en el marco de su Sistema de Gestion de Seguridad de la Informacion siendo para uso exclusivo del destinatario, quedando prohibida su divulgacion copia o distribucion a terceros sin la autorizacion expresa del remitente. Si Vd. ha recibido este mensaje erroneamente, se ruega lo notifique al remitente y proceda a su borrado. Gracias por su colaboracion. ______________________ This message including any attachments may contain confidential information, according to our Information Security Management System, and intended solely for a specific individual to whom they are addressed. Any unauthorised copy, disclosure or distribution of this message is strictly forbidden. If you have received this transmission in error, please notify the sender immediately and delete it. ______________________

1 0

Re: (ITS#5369) GSSAPI support for client library
by kurt＠OpenLDAP.org 14 Feb '08

14 Feb '08

You've only included one of the two required statements. You need also need to include either a copyright + license statement, or a public domain release statement. -- Kurt On Feb 14, 2008, at 9:12 AM, mimir(a)samba.org wrote: > > --OgqxwSJOaUobr8KG > Content-Type: text/plain; charset=iso-8859-2 > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > Kurt, > > On Mon, Feb 11, 2008 at 09:06:19AM -0800, Kurt Zeilenga wrote: >>> Full_Name: Rafal Szczesniak >>> Version: HEAD >>> OS: GNU/Linux >>> URL: http://www.samba.org/~mimir/gssapi-head.diff >> >> The submitted patch file does not contain (at the top of the file, >> not = > =20 >> as part of the diffs) the required notices. Please review=20 >> http://www.openldap.org/devel/contributing.html and insert >> appropriate=20 >> notices. Also, please don't include in the diffs derived files >> (e.g.,=20 >> configure). > > I've updated the patch file with necessary changes. Please take a look > if it's fine now. > > > cheers, > --=20 > Rafal Szczesniak > Samba Team member http://www.samba.org > Likewise Software http://www.likewisesoftware.com > > > --OgqxwSJOaUobr8KG > Content-Type: application/pgp-signature; name="signature.asc" > Content-Description: Digital signature > Content-Disposition: inline > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFHtJLCHvdfyv3qiKkRArL0AJ9ZazJE3LUduZb3A8rz21KheW/EYQCfQt8z > F7AnIDF5EkJ7ssDwHStryEo= > =tIVf > -----END PGP SIGNATURE----- > > --OgqxwSJOaUobr8KG-- > >

1 0

Re: (ITS#5378) hot slapcat for slapadd issues with delta-sync
by quanah＠zimbra.com 14 Feb '08

14 Feb '08

--On February 14, 2008 12:21:00 PM +0000 hyc(a)symas.com wrote: > Pierangelo Masarati wrote: >> hyc(a)OpenLDAP.org wrote: >> >>> Another possibility would be to filter out any entries whose entryCSNs >>> are newer than the contextCSN in the LDIF before trying to slapadd it. >> >> Should slapadd take care of it (perhaps if instructed to do so)? > > Of course it might be better to change the delta-sync consumer to check > the target's entryCSN after a modification fails, to see if it matches > the current modification attempt. If so, then the failure can be safely > ignored. -- Note: It should be if it matches or is greater. For example, if it was the very last entry in the DB, thus the last to be added to the resulting LDIF, it is entirely possible that multiple modifications could be done from the time the dump started and the dump ended, meaning the CSN would be greater than the one encountered in the accesslog DB. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

← Newer
1
2
3
4
5
6
7
8
9
...
21
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs February 2008