openldap-technical January 2011

openldap-technical@openldap.org

91 participants
107 discussions

Index for objectclass does not work...
by Steeg Carson 03 Jan '11

03 Jan '11

Hello again, I can't solve my problem on my own... please help. As I can see at the moment, the Index for objectclass is not used. The searchtime with and without index for objectclass is the same! The search looks like: ldapsearch -x -h localhost -wpassword -D"uid=admin,ou=root" -b"cn=ownPath,ou=root" "(ObjectClass=subEngine)" The first serach, it takes about 40seconds. So after the cache is filled, the next searches takes only about 2 seconds (during both logging is turned off!)... It doesn't matter whether the index is set up in the config or not. To check, that the index is really set up (or not), I set loglevel 64 ind the slapd.conf: ####################################################################### @(#) $OpenLDAP: slapd 2.4.23 $#012#011opensuse-buildservice(a)opensuse.org line 30 (rootpw ***) line 31 (directory#011/var/lib/ldap_hdb) line 32 (logfile#011#011/var/log/openldap.log) line 33 (cachesize 1000000) line 34 (dncachesize 1000000) line 34 (idlcachesize 3000000) line 36 (dbnosync) line 38 (index objectClass eq) index objectClass 0x0004 line 39 (index cn eq,sub) index cn 0x0714 hdb_monitor_db_open: monitoring disabled; configure monitor database to enable slapd starting ####################################################################### The searched objectClass=subEngine exists 104384 times in the entire directory: (=> ldapsearch -x -h localhost -D"uid=admin,ou=root" -b"cn=ou=root>" "(ObjectClass=subEngine)" dn | grep "^dn:" | wc -l) If I configure with index for Objectclass, I get for the search following messages: ####################################################################### => bdb_equality_candidates (objectClass) => key_read <= bdb_index_read 470601 candidates <= bdb_equality_candidates: id=-1, first=228, last=470828 <= bdb_filter_candidates: id=-1 first=228 last=470828 <= bdb_list_candidates: id=-1 first=228 last=470828 <= bdb_filter_candidates: id=-1 first=228 last=470828 <= bdb_list_candidates: id=-1 first=40595 last=470828 <= bdb_filter_candidates: id=-1 first=40595 last=470828 bdb_search_candidates: id=-1 first=40595 last=470828 ####################################################################### If I search then in the logfile, I see 430233 messages like: "hdb_search: <candidate> <message: does not match filter | scope not okay>" If I configure without index for objectclass, I get for the search following messages: ####################################################################### => bdb_equality_candidates (objectClass) <= bdb_equality_candidates: (objectClass) not indexed <= bdb_filter_candidates: id=-1 first=1 last=470828 <= bdb_list_candidates: id=-1 first=1 last=470828 <= bdb_filter_candidates: id=-1 first=1 last=470828 <= bdb_list_candidates: id=-1 first=40595 last=470828 <= bdb_filter_candidates: id=-1 first=40595 last=470828 bdb_search_candidates: id=-1 first=40595 last=470828 ####################################################################### During initial set up of the Database (slapadd, copied from production, off-line with slapcat), the index for objectclass was build. I also tried to rebuild the index with slapindex. I configured a 64bit system, with 16GByte RAM and 2 CPUs under VMware ESX with own SAS-Storage (RAID10) for only this Machine. The entire directory holds 470812 entires. (=> ldapsearch -x -h localhost -wpassword -D"uid=admin,ou=root" -b"ou=root" "(objectClass=*)" dn | grep "^dn:" | wc -l) I configured slapd.conf as following: ####################################################################### include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/rfc2307bis.schema include /etc/openldap/schema/own.schema pidfile /var/run/slapd/slapd.pid argsfile /var/run/slapd/slapd.args modulepath /usr/lib/ldap moduleload back_hdb sizelimit -1 timelimit 300 disallow bind_anon gentlehup on tool-threads 2 # hdb database definitions database hdb suffix "ou=root" rootdn "uid=admin,ou=root" checkpoint 4096 15 # loglevel only for test, not during time measuring loglevel 33 # or for config file processing # loglevel 64 rootpw password directory /var/lib/ldap_hdb logfile /var/log/openldap.log cachesize 1000000 dncachesize 1000000 idlcachesize 3000000 dbnosync index objectClass,entryUUID,entryCSN eq index cn eq,sub ####################################################################### In DB_CONF I set 2GB BDB page cache (set_cachesize 2 0 1) Thanks for help, kindly regards Steeg PS: During the first search, the disk is heavy used (iotop) by writing from slapd.conf ... why it - should only read ...? -

3 3

Re: Windows ldp.exe kills openldap 2.4.23
by masarati＠aero.polimi.it 03 Jan '11

03 Jan '11

> On Sun, Jan 2, 2011 at 3:45 AM, <masarati(a)aero.polimi.it> wrote: >> >> >>>> Is this a know bug (see ITS#6570) or something new? Is there a >>>> workaround >>>> it? >>> >>> AFAIK it is not known. I am able to reproduce it (Linux, HEAD code), >>> so I >>> suggest you file an ITS. With respect to a workaround, it is not clear >>> what's the purpose of the operation you're trying to accomplish. In >>> general, a modrdn on the empty DN should be meaningless (although it >>> should not crash the server). >> >> A fix is in HEAD (slapd/modrdn.c); please test. p. Please keep replies on the thread. > Thanks, I'll give it a try. And sorry for the confusion, by "work > around" a meant securing server from a such easy DOS attack, > i.e.preventing a crush. > > Do you know when 2.4.24 is scheduled to come out? Do you still want me > to create an ITS? Yes, please, so we can track the issue. Thanks, p.

2 2

Re: Kerberos/GSSAPI issues
by Brian Candler 02 Jan '11

02 Jan '11

On Thu, Dec 30, 2010 at 11:49:23AM -0800, Russ Allbery wrote: > > Have you got the one-line patch? > > Included below. Thank you Russ. Discussed further on kerberos(a)mit.edu list, and ticket raised as http://bugzilla.cyrusimap.org/show_bug.cgi?id=3380 Regards, Brian.

1 0

SASL proxy auth problem
by Jaap Winius 02 Jan '11

02 Jan '11

Hi folks, Thanks to Pierangelo's last reply, I now know what I suspected: that my consumer servers are configured to authenticate to their providers using SASL/GSSAPI, but that sometimes they don't do this, especially with proxy authorization. I've documented the entire install process: * OpenLDAP provider with MIT Kerberos V on Debian squeeze http://www.rjsystems.nl/en/2100-d6-openldap-provider-kerberos.php * OpenLDAP consumer with MIT Kerberos V on Debian squeeze http://www.rjsystems.nl/en/2100-d6-openldap-consumer-kerberos.php The last time I followed these instructions to the letter, proxy authorization worked. Now I've booted up the same machines again a few days later and it no longer works: the consumer still uses SASL to bind with the provider for replication, but it uses a SIMPLE bind for proxy authorization. Of course that results in an error. Yet, the configuration seems unchanged. Has anyone else experienced this problem? Thanks, Jaap PS -- If anyone is interested, I can supply plenty of details. See also my post of 12/24/2010 03:25:51 AM CET with subject "No ProxyAuthz with SASL-GSSAPI?"

2 6

Re: Windows ldp.exe kills openldap 2.4.23
by masarati＠aero.polimi.it 02 Jan '11

02 Jan '11

>> Is this a know bug (see ITS#6570) or something new? Is there a >> workaround >> it? > > AFAIK it is not known. I am able to reproduce it (Linux, HEAD code), so I > suggest you file an ITS. With respect to a workaround, it is not clear > what's the purpose of the operation you're trying to accomplish. In > general, a modrdn on the empty DN should be meaningless (although it > should not crash the server). A fix is in HEAD (slapd/modrdn.c); please test. p.

1 0

Windows ldp.exe kills openldap 2.4.23
by Serge Dubrouski 01 Jan '11

01 Jan '11

Hello - I just found that ldp.exe tool that comes with Windows is able to successfully kill OpenLDAP 2.4.23 when one tries tp modify DN and submits an empty old DN. Log files on openldap show this: Dec 29 15:19:32 ottawa slapd[11818]: conn=1000 op=2 do_modrdn Dec 29 15:19:32 ottawa slapd[11818]: do_modrdn: dn () newrdn (C=US) newsuperior () Dec 29 15:19:32 ottawa slapd[11818]: >>> dnPrettyNormal: <> Dec 29 15:19:32 ottawa slapd[11818]: <<< dnPrettyNormal: <>, <> Dec 29 15:19:32 ottawa slapd[11818]: >>> dnPrettyNormal: <C=US> Dec 29 15:19:32 ottawa slapd[11818]: <<< dnPrettyNormal: <c=US>, <c=us> Dec 29 15:19:32 ottawa slapd[11818]: conn=1000 op=2 MODRDN dn="" Is this a know bug (see ITS#6570) or something new? Is there a workaround it? -- Serge Dubrouski.

2 1

slapd bind method codes
by Jaap Winius 01 Jan '11

01 Jan '11

Hi folks, When clients bind with a provider and the provider's loglevel is set to stats, bind events show up frequently in the log. Often, some logged bind events have only a blank dn along with a "method" code. Here are two separate examples: slapd[903]: conn=1021 op=0 BIND dn="" method=128 slapd[903]: conn=1020 op=0 BIND dn="" method=163 Two questions: 1.) What do these method codes mean? Perhaps there list somewhere that explains all possible method codes. 2.) When a method code is shown, as in the examples above, why is the value for the dn empty? Thanks, Jaap

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical January 2011