openldap-devel

openldap-devel@openldap.org

1418 discussions

Use of oidValidate() in schema-related attrs?
by Pierangelo Masarati 27 Sep '08

27 Sep '08

We currently use oidValidate() in the hardcoded definition of attributes like dITContentRules, matchingRules, attributeTypes, objectClasses, nameForms, matchingRuleUse. However, this only looks correct as a validator for an assertion value of the related syntaxes, while it fails for valid attribute values. I understand this is a moot point, since we do not allow direct writing of cn=subschema and subschema subentries in general. However this causes, for example, an incorrect error to be returned when one attempts to write, for example, cn=subschema. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it ----------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Fax: +39 0382 476497 Email: ando(a)sys-net.it -----------------------------------

1 0

New test054-syncrepl-asymmetric
by Rein Tollevik 25 Sep '08

25 Sep '08

I have created a test script that shows the contextCSN propagation problems we have, as well as a patch that fixes most of them. But before I commit anything or files more ITSs I'd like to receive comments. The test script and patch can be found at: ftp://ftp.openldap.org/incoming/test054-syncrepl-asymmetric ftp://ftp.openldap.org/incoming/test054-syncrepl-asymmetric.patch The comments in the scripts should hopefully explain the configuration. The patch adds support for the newCookie sync info protocol messages, and sends them when the contextCSN is being updated without any changes being sent from the syncprov provider (i.e when the entries that changed didn't match the syncrepl filter and/or was forbidden by ACL rules). The queuing of the CSNs done in syncrepl_updateCookie should not be necessary with this patch, it should be removed after the patch has been committed. The bug reported in ITS#5710 is also worked around by this patch, but defining SLAP_SYNC_UPDATE_MSGID with an unique value would be better. This test requires the proposed patch to fix ITS#5572 to be applied. Dynamically creating the configuration doesn't work as expected without it, and the number of errors reported by the script increases from 10 to 25. Mostly due to the replication starting in an unexpected state, and several restarts and writes are needed before an expected state is reached. This patch can be found at: ftp://ftp.openldap.org/incoming/ITS5572.patch The test script finds 10 errors (assuming the race condition discussed below is actually hit) after the ITS#5572 patch has been applied With both patches I'm left with 3 errors, all related to the race condition. Howard, you'll probably object to the rootdn usage in this test. But as of now there is no way I know of that allows me to create the layout I need without it. Extending syncrepl with the ability to exclude a list of dn subtrees from its control could be the solution. But in that case I assume it would be better to have a list of URIs (evaluated locally) that defines the entries to exclude. Which again opens a can of new questions as to when the URIs should be evaluated. For add and delete it should be pretty obvious, but what about modify? Test against the entry as it is before the change, would be after or both? Hmm, the ability to exclude a list of URIs from syncrepl control could be (ab)used to merge some type of entries from one server, other types from other servers, if anyone should wish to do such weired things.. The errors remaining after these two patches have been applied are due to the race condition that arise if more then one subordinate database replicates from the same provider. I have a clear idea as to how this race can be eliminated, it must be addressed in both syncrepl and syncprov: In syncrepl it should be fairly easy, as storing the contextCSN values in the suffix of the database where syncrepl is configured rather than the suffix of the glue entry should be sufficient. Syncprov needs a bit more work. Whenever it detects that syncrepl updates the contextCSN value it must use the *lowest* contextCSN value for any given sid stored in all the databases within its context. And no updates must be accepted from syncrepl until a contextCSN value has been stored in the suffix dn of all databases (within its context) where syncrepl has been enabled. Assuming syncrepl cannot be used on both a superior and a subordinate database (which could no be true if the ability to exclude something from its control is introduced) it should not be required to make these extra tests when syncrepl updates the contextCSN in the suffix of the glue database itself (i.e when syncrepl and syncprov are configured in the same database). The sending of newCookie messages should cause the contextCSN values to be updated to the newest values fairly quickly. Actually, there could be another problem buried here as well, as the consumers really need a full resynchronization after new subordinate syncrepl consumers are added on their provider (at least if the new consumer replicates from the same server as an existing). The easiest fix would be to require the clients to do a full resync whenever the config of the provider is changed, which I find a bit drastic. Noting it in the doc. should hopefully be sufficient. Rein Tollevik Basefarm AS

1 0

Re: commit: ldap/servers/slapd/back-bdb add.c back-bdb.h bind.c cache.c compare.c config.c delete.c dn2entry.c dn2id.c filterindex.c id2entry.c idl.c init.c key.c modify.c modrdn.c proto-bdb.h referral.c search.c tools.c
by Howard Chu 25 Sep '08

25 Sep '08

hyc(a)OpenLDAP.org wrote: > Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/back-bdb > > Modified Files: > add.c 1.173 -> 1.174 > back-bdb.h 1.173 -> 1.174 > bind.c 1.54 -> 1.55 > cache.c 1.180 -> 1.181 > compare.c 1.57 -> 1.58 > config.c 1.107 -> 1.108 > delete.c 1.172 -> 1.173 > dn2entry.c 1.35 -> 1.36 > dn2id.c 1.156 -> 1.157 > filterindex.c 1.75 -> 1.76 > id2entry.c 1.86 -> 1.87 > idl.c 1.134 -> 1.135 > init.c 1.291 -> 1.292 > key.c 1.24 -> 1.25 > modify.c 1.176 -> 1.177 > modrdn.c 1.200 -> 1.201 > proto-bdb.h 1.159 -> 1.160 > referral.c 1.50 -> 1.51 > search.c 1.265 -> 1.266 > tools.c 1.127 -> 1.128 > > Log Message: > Use read-only txn's instead of read lockers. Support BDB 4.4-4.7 Please test... At the moment I've only run it with BDB 4.7.25. I'll be testing with older releases over the next couple of days. In particular, take note of any LDAP_OTHER/Internal Error results in the test suite. Right now it passes all tests for me on bdb and hdb. If push comes to shove we can probably create a new BerkeleyDB4.2.patch file to get 4.2 working again, but at this point most people should already be on something newer, and people stuck on 4.2 probably won't compile their own anyway. -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

2 4

RE24 and BDB 4.7.25p1 hanging
by Michael Ströder 23 Sep '08

23 Sep '08

HI! I'm trying to run current RE24 with BDB 4.7.25p1. It hangs in test-001 and it hangs (probably when doing a bind). Is that combination really stable? Ciao, Michael.

6 18

RE24 testing
by Quanah Gibson-Mount 22 Sep '08

22 Sep '08

Please test RE24. Thanks! --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

8 23

test050-syncrepl-multimaster failures
by Rein Tollevik 18 Sep '08

18 Sep '08

Like others have reported, I have seen failures with this test after upgrading to the recent RE_24. I have only seen it when running the test on a multi-cpu linux system tough, it works find on a single-cpu solaris. When it fails it is always syncrepl in the two first servers that fails to bind to the third. In the logs they complains repeatedly like: slap_client_connect: URI=ldap://localhost:9013/ DN="cn=config" ldap_sasl_bind_s failed (-5) I.e, the bind timed out. Server3 logs the bind request, but first after the unbind that follows.. Modifying the source with some more debug output that prints the time it shows that the bind request is sent and times out (after 3 seconds) before server3 logs accept of the connection. Some race condition that kicks in if two servers tries to connect and bind at the same time? Btw, I've only tested with back-bdb. Well, that's how far I've had time to look at it. I have plenty of logs available if anyone care to look at them. Rein

1 1

Re: RE24 testing
by ghenry＠OpenLDAP.org 16 Sep '08

16 Sep '08

----- "Quanah Gibson-Mount" <quanah(a)zimbra.com> wrote: > --On Monday, September 15, 2008 10:53 PM +0100 ghenry(a)OpenLDAP.org > wrote: > > > I've added --disable-ndb and I'm using our normal build_openldap.sh > with > > bdb 4.7.25.NC: > > > > config.status: creating servers/slapd/back-meta/Makefile > > config.status: creating servers/slapd/back-monitor/Makefile > > config.status: creating servers/slapd/back-ndb/Makefile > > config.status: error: cannot find input file: > > servers/slapd/back-ndb/Makefile.in Making depend in cvs up -d would help, as configure wasn't completing. > Works for me... :P Me too now ;-) -- Kind Regards, Gavin Henry. OpenLDAP Engineering Team. E ghenry(a)OpenLDAP.org Community developed LDAP software. http://www.openldap.org/project/

7 6

Re: commit: ldap/build openldap.m4
by Howard Chu 15 Sep '08

15 Sep '08

hyc(a)OpenLDAP.org wrote: > Update of /repo/OpenLDAP/pkg/ldap/build > > Modified Files: > openldap.m4 1.167 -> 1.168 > > Log Message: > Updated BerkeleyDB version tests The only question here is whether we need an explicit "-o -" on the CPP invocation to force output to stdout. For most systems, that's the default behavior. Let me know if you find something that behaves differently... -- -- 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 1

Re: RE24 testing
by ghenry＠OpenLDAP.org 15 Sep '08

15 Sep '08

I've added --disable-ndb and I'm using our normal build_openldap.sh with bdb 4.7.25.NC: config.status: creating servers/slapd/back-meta/Makefile config.status: creating servers/slapd/back-monitor/Makefile config.status: creating servers/slapd/back-ndb/Makefile config.status: error: cannot find input file: servers/slapd/back-ndb/Makefile.in Making depend in /anything/src/openldap/RE_2_4 Entering subdirectory include make[1]: Entering directory `/anything/src/openldap/RE_2_4/include' Making ldap_config.h make[1]: Leaving directory `/anything/src/openldap/RE_2_4/include' Entering subdirectory libraries make[1]: Entering directory `/anything/src/openldap/RE_2_4/libraries' Making depend in /anything/src/openldap/RE_2_4/libraries Entering subdirectory liblutil make[2]: Entering directory `/anything/src/openldap/RE_2_4/libraries/liblutil' ../../build/mkdep -d "." -c "gcc" -m "-M" -I../../include -I../../include -I/usr/local/BerkeleyDB.4.7/include base64.c csn.c entropy.c sasl.c signal.c hash.c passfile.c md5.c passwd.c sha1.c getpass.c lockf.c utils.c uuid.c sockpair.c avl.c tavl.c ldif.c fetch.c testavl.c setproctitle.c getpeereid.c detach.c base64.c:38:22: error: portable.h: No such file or directory csn.c:44:22: error: portable.h: No such file or directory entropy.c:22:22: error: portable.h: No such file or directory sasl.c:16:22: error: portable.h: No such file or directory signal.c:16:22: error: portable.h: No such file or directory -- Kind Regards, Gavin Henry. OpenLDAP Engineering Team. E ghenry(a)OpenLDAP.org Community developed LDAP software. http://www.openldap.org/project/

2 1

slapd fails an assertion
by Emmanuel Dreyfus 15 Sep '08

15 Sep '08

Hello I have a setup where slapd regularly fails and assertion and exits: assertion "SLAP_SOCK_IS_ACTIVE( s )" failed: file "daemon.c", line 931, function "slapd_clr_write" I don't have epoll(4), nor /dev/poll, neitheram I running on win32, so the right definition for me is # define SLAP_SOCK_IS_ACTIVE(fd) FD_ISSET((fd), &slap_daemon.sd_actives) Any hint? This is OpenLDAP-2.4.9 on NetBSD-4.0. Is it possible that this problem be fixed in a later OpenLDAP version? -- Emmanuel Dreyfus manu(a)netbsd.org

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-devel