openldap-devel

openldap-devel@openldap.org

1416 discussions

Debugging left over in test008?
by Quanah Gibson-Mount 29 Apr '16

29 Apr '16

After hitting test008 failure on a new system because "time" was not installed, I looked at test008, and I think the problem is someone was debugging something years ago, and checked the script in still in that state: echo "Using tester for concurrent server access..." time $SLAPDTESTER -P "$PROGDIR" -d "$TESTDIR" -h $LOCALHOST -p $PORT1 -D "$MANAGERDN" -w $PASSWD -l $TESTLOOPS #$SLAPDTESTER -P "$PROGDIR" -d "$TESTDIR" -h $LOCALHOST -p $PORT1 -D "$MANAGERDN" -w $PASSWD -l $TESTLOOPS RC=$? Note the commented out line. The checkin for this change seems to confirm it was accidental as well, and that all that was intended was the "sleep 1": quanah@b4c92f65-2064-44a6-9707-a97562610945:~/git/openldap/openldap-head$ git show 572ca2db -- tests/scripts/test008-concurrency commit 572ca2db94b0e7af95e7ac16a91cb1ea3b3d136a Author: Howard Chu <hyc(a)openldap.org> Date: Fri Sep 30 07:32:49 2005 +0000 Tweak slapd startup delays diff --git a/tests/scripts/test008-concurrency b/tests/scripts/test008-concurrency index 3841c33..6ea541f 100755 --- a/tests/scripts/test008-concurrency +++ b/tests/scripts/test008-concurrency @@ -36,6 +36,8 @@ if test $WAIT != 0 ; then fi KILLPIDS="$PID" +sleep 1 + echo "Using ldapsearch to check that slapd is running..." for i in 0 1 2 3 4 5; do $LDAPSEARCH -s base -b "$MONITOR" -h $LOCALHOST -p $PORT1 \ @@ -49,7 +51,8 @@ for i in 0 1 2 3 4 5; do done echo "Using tester for concurrent server access..." -$SLAPDTESTER -P "$PROGDIR" -d "$DATADIR" -h $LOCALHOST -p $PORT1 -D "$MANAGERDN" -w $PASSWD -l 50 +time $SLAPDTESTER -P "$PROGDIR" -d "$DATADIR" -h $LOCALHOST -p $PORT1 -D "$MANAGERDN" -w $PASSWD -l 50 +#$SLAPDTESTER -P "$PROGDIR" -d "$DATADIR" -h $LOCALHOST -p $PORT1 -D "$MANAGERDN" -w $PASSWD -l 50 RC=$? if test $RC != 0 ; then Are there any objections to me switching these around so that the time line is commented out instead? ;) --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration A division of Synacor, Inc

2 3

LMDB: mdb_cursor_put() and the rest of page in case MDB_RESERVE
by Леонид Юрьев 31 Mar '16

31 Mar '16

Hi, Howard. Why mdb_cursor_put() doesn't copy the rest of page in case MDB_RESERVE? It is here (current mdb.master, mdb.c line 7479) = http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=blob;f=libraries/… Regards, Leonid.

3 3

Performance degredation between 2.4.39 and 2.4.44
by Quanah Gibson-Mount 15 Mar '16

15 Mar '16

I've noticed a bit of a performance degradation between the 2.4.39 release and 2.4.44, when doing searches that require ACL processing (anonymous or authenticated user). To test, I set up my server with 2.4.39, freshly load the DB, reboot, and then do a query of each type to ensure its data set is fully loaded in memory, and then get timing on the subsequent searches. The server is idle other than my searches. Overall, there's about a 30 second consistent degradation in search results, regardless of whether or not ACLs are involved. It works out to about a 15% degredation for authenticated queries, and a 32% degredation for rootdn searches. Results are as follows: 2.4.39 anonymous search (only returns some data, subject to ACL processing): zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com >/dev/null real 3m25.871s user 1m43.872s sys 0m45.254s zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com >/dev/null real 3m22.730s user 1m39.575s sys 0m26.400s zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com >/dev/null real 3m23.506s user 1m41.919s sys 0m25.968s 2.4.44 anonymous search (only returns some data, subject to ACL processing): zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com >/dev/null real 3m54.841s user 1m36.754s sys 0m44.509s zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com >/dev/null real 3m56.609s user 1m37.875s sys 0m48.151s zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com >/dev/null real 3m53.275s user 1m36.293s sys 0m45.131s 2.4.39 authenticated search (returns all data, subject to ACL processing): zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com -D uid=zimbra,cn=admins,cn=zimbra -w zimbra >/dev/null real 3m23.057s user 1m59.358s sys 0m35.809s zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com -D uid=zimbra,cn=admins,cn=zimbra -w zimbra >/dev/null real 3m23.478s user 2m0.236s sys 0m26.972s zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com -D uid=zimbra,cn=admins,cn=zimbra -w zimbra >/dev/null real 3m22.965s user 1m58.245s sys 0m28.030s 2.4.44 authenticated search (returns all data, subject to ACL processing): zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com -D uid=zimbra,cn=admins,cn=zimbra -w zimbra >/dev/null real 3m57.967s user 1m56.335s sys 0m49.483s zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com -D uid=zimbra,cn=admins,cn=zimbra -w zimbra >/dev/null real 3m57.405s user 1m55.415s sys 0m50.772s zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com -D uid=zimbra,cn=admins,cn=zimbra -w zimbra >/dev/null real 3m57.717s user 1m57.427s sys 0m41.401s 2.4.39 rootdn search (no ACL processing): zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com -D cn=config -w zimbra >/dev/null real 1m20.718s user 1m14.501s sys 0m6.164s zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com -D cn=config -w zimbra >/dev/null real 1m19.569s user 1m13.557s sys 0m5.935s zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com -D cn=config -w zimbra >/dev/null real 1m20.488s user 1m14.514s sys 0m5.917s 2.4.44 rootdn search (no ACL processing): zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com -D cn=config -w zimbra >/dev/null real 1m57.199s user 1m10.855s sys 0m14.161s zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com -D cn=config -w zimbra >/dev/null real 1m58.030s user 1m10.797s sys 0m14.970s zimbra@zre-ldap001:~$ time ldapsearch -x -h zre-ldap001.eng.zimbra.com -D cn=config -w zimbra >/dev/null real 1m57.754s user 1m10.069s sys 0m15.336s --Quanah -- Quanah Gibson-Mount Platform Architect, Manager Release Engineering Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration A division of Synacor, Inc

2 6

Supported backends/overlays in 2.5
by Quanah Gibson-Mount 03 Mar '16

03 Mar '16

For 2.5, it would be good to take a look at existing backends and overlays we ship as supported, and see if there are any we want to retire. I think it would be nice as well to make it so people could configure in various contrib modules via configure flags, rather than the current manual make process. I'll start with my thoughts: backends: I would like to see us retire slapd-bdb and slapd-hdb. We first documented they were deprecated in March of 2013 and updated the man pages to officially note that in May of 2014. Nearly 2 years have passed since then, and it'll likely be at least another year before 2.5 is production ready. That's some 3 years. In addtion, both slapd-bdb and slapd-hdb depend on BDB versions that are not supported by Oracle, and the source to which Oracle is doing its best to remove and make inaccessible. Another possibility is back-perl. back-sock is a better solution. OTOH, We have gotten contributions fixing issues in it as recently as April 2015, so there may be folks using it who would like to see it continue. overlays: I'd like to see the passwd/sha2 overlay be considered for promotion. Having the ability to set strong hashes for passwords is crucial in todays world. --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration A division of Synacor, Inc

6 9

LTB Project off the air?
by Brian Reichert 02 Mar '16

02 Mar '16

I know this isn't the forum for this, but I can't reach the LTB Project's website or mail server; traceroutes fall off somewhere in Europe. I've tried from a few different networks. Does anyone here any have insight as to what's going on? -- Brian Reichert <reichert(a)numachi.com> BSD admin/developer at large

2 2

Re: RE24 testing call #1 (2.4.44) LMDB RE0.9 testing call #2 (0.9.18)
by Abdelkader Chelouah 05 Feb '16

05 Feb '16

git bd5e44c9ee9108b26053a0d03a587dda94c4ebe9 All tests run through without error on CentOS 7.2 x86_64 for hdb (bdb 5.1.29) and mdb. On Wed, Feb 3, 2016 at 10:47 PM, Quanah Gibson-Mount <quanah(a)zimbra.com> wrote: > Changes since testing call #1: > > Fixed slapo-syncprov ctxcsn snapshot on refresh (ITS#8281, ITS#8365) > > --Quanah > > -- > > Quanah Gibson-Mount > Platform Architect > Zimbra, Inc. > -------------------- > Zimbra :: the leader in open source messaging and collaboration > A division of Synacor, Inc > >

1 0

RE24 testing call #1 (2.4.44) LMDB RE0.9 testing call #2 (0.9.18)
by Quanah Gibson-Mount 04 Feb '16

04 Feb '16

Changes since testing call #1: Fixed slapo-syncprov ctxcsn snapshot on refresh (ITS#8281, ITS#8365) --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration A division of Synacor, Inc

2 1

RE24 testing call #1 (2.4.44) LMDB RE0.9 testing call #1 (0.9.18)
by Quanah Gibson-Mount 30 Jan '16

30 Jan '16

OpenLDAP 2.4.44 Engineering Fixed slapd-bdb/hdb missing olcDbChecksum config attr (ITS#8337) Fixed slapd-mdb cleanup after failed transaction (ITS#8360) Fixed slapd-sql missing id_query/olcSqlIdQuery (ITS#8329) Fixed slapo-accesslog callback initialization (ITS#8351) Fixed slapo-ppolicy pwdMaxRecordedFailure must never be zero (ITS#8327) Fixed slapo-syncprov abandon processing (ITS#8354) Documentation admin24 Stop linking to Berkeley DB downloads (ITS#8362) admin24 Update documentation for LMDB preference LMDB 0.9.18 Release Engineering Fix robust mutex detection on glibc 2.10-11 (ITS#8330) Fix page_search_root assert on FreeDB (ITS#8336) Fix MDB_APPENDDUP vs. rewrite(single item) (ITS#8334) Fix mdb_copy of large files on Windows Fix subcursor move after delete (ITS#8355) Fix mdb_midl_shirnk off-by-one (ITS#8363) Check for utf8_to_utf16 failures (ITS#7992) Catch strdup failure in mdb_dbi_open Build Additional makefile var tweaks (ITS#8169) Documentation Add Getting Started page Update WRITEMAP description Thanks! --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

5 8

Re: Dropping the MozNSS crypto bits from OpenLDAP
by Quanah Gibson-Mount 18 Jan '16

18 Jan '16

Hi Ludwig, We have yet to even alpha 2.5, and then there will be betas and potential RCs. I'd say we're overall at least a year out from an official 2.5 release. --Quanah --On Friday, January 15, 2016 3:02 PM +0100 Ludwig Krispenz <lkrispen(a)redhat.com> wrote: > Hi Quannah, > > not an objection to dropping it, but a question about timing. > We are using the openldap client library in 389-ds and rely on the fact > that they are linked to moznss. We are in the process to make our > implementation/deployment independent of which crypto lib is used, but > we are not yet there. > > What is the time frame of 2.5 ? > > Regards, > Ludwig > > On 01/12/2016 12:58 AM, Quanah Gibson-Mount wrote: >> Hi Jan, >> >> Now that the Crypto Consolidation project has been dropped by Fedora >> (<https://fedoraproject.org/wiki/FedoraCryptoConsolidation>), is there >> any objection to OpenLDAP dropping the MozNSS work going forward >> (OpenLDAP 2.5+)? We already have noted we don't support people using >> it, due to the security problems it creates, etc. >> >> Thanks, >> Quanah >> >> -- >> >> Quanah Gibson-Mount >> Platform Architect >> Zimbra, Inc. >> -------------------- >> Zimbra :: the leader in open source messaging and collaboration >> > -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Slapd startup behavior when unable to bind to an interface
by Quanah Gibson-Mount 11 Jan '16

11 Jan '16

Currently, slapd will start up even if it can't bind to an interface, if more than one potential interface is given where the bind is successful. This was, as best as Howard can recall, done because of ipv4/ipv6 issues on some systems. However, it seems to me that it should at least be possible to specify to slapd that you do not want it to start up unless binding to all interfaces is successful. This is fairly trivial to reproduce. As a non-privileged user, simply do: -h "ldap:// ldapi://slapd.sock" It will fail to bind to 389, but bind to the LDAPI socket anyway, and continue the startup process. This gives a false result that slapd started successfully, although clearly external clients will be unable to talk to it. --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

4 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-devel