openldap-devel

openldap-devel@openldap.org

1431 discussions

test039: ldap_search_ext_s(cn=Database 1,cn=Databases,cn=Monitor): No such object (32)
by Michael Ströder 13 Mar '09

13 Mar '09

Why are there so many messages like this when running test039-glue-ldap-concurrency in RE24? slapd-read PID=25003: ldap_search_ext_s(cn=Database 1,cn=Databases,cn=Monitor): No such object (32) matched: cn=Databases,cn=Monitor Ciao, Michael.

2 1

Re: commit: ldap/servers/slapd/overlays syncprov.c
by Pierangelo Masarati 13 Mar '09

13 Mar '09

hyc(a)OpenLDAP.org wrote: > Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/overlays > > Modified Files: > syncprov.c 1.272 -> 1.273 > > Log Message: > More for #6020 Howard, I'm running a set of private tests loosely derived from test050. There is one which basically consisted in simultaneously running 3 concurrency tests (slapd-tester) with 3 MMR (intensive potentially conflicting write load). It didn't use to pass until this last fix. Now all modifications seem to apply and replicate consistently. However, in the end the entryCSN of some entries differ (occasionally, the test just passes). Does this give you some useful indication? I can share the tests (they were meant for inclusion in OpenLDAP, all in all, although they are under development). It may require a while, because they need harmonization. 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 -----------------------------------

2 1

Re: commit: ldap/servers/slapd/overlays syncprov.c
by Howard Chu 12 Mar '09

12 Mar '09

hyc(a)OpenLDAP.org wrote: > Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/overlays > > Modified Files: > syncprov.c 1.266 -> 1.267 > > Log Message: > ITS#6020 better tracking of where changes came from Note that this is an incompatible change on the wire. Previously the rid and sid that a consumer sends to a provider were returned unchanged in any responses from the provider. (Which was, in retrospect, a mistake... It allowed the syncprov to know the sid of the consumer, but the consumer didn't know the sid of the provider.) Now the current server's serverID is always sent. This allows both sides of the connection to know each other's serverID, which is essential for routing decisions. -- -- 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

Re: Please test RE24
by Quanah Gibson-Mount 10 Mar '09

10 Mar '09

--On Tuesday, March 10, 2009 7:58 PM +0100 Jens Vagelpohl <jens(a)dataflake.org> wrote: >> This should be fixed now, please test further. :) > > Not yet :-( > > testrun tarball attached. Thanks. Please keep replies on the list though. :) --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Enforce serverID 0 is for single-master only
by Rein Tollevik 09 Mar '09

09 Mar '09

ServerID 0 should be reserved for single-master configurations, ref http://www.openldap.org/lists/openldap-bugs/200809/msg00131.html. But this is neither enforced in the code, nor mentioned in the doc. as far as I can see. Reserving serverID 0 for the single-master case would make it easier to distinguish between old single-master and new multi-master configuration based on the SID of the CSNs. But the main benefit would be to catch the apparently far too common configuration error of failing to set a correct serverID in multi master configurations. Is it OK if I implement it? This would mean that slapd would refuse to start if syncrepl or syncprov finds a contextCSN value with SID=0 in the database upon startup and there is more than one contextCSN, or if MirrorMode is enabled. Syncrepl should refuse to receive updates to contextCSN values under the same conditions, and tear down the connection (and retry later) if one is seen. Syncprov should also refuse slapd to start if serverID is 0 and MirrorMode is enabled or any contextCSN with non-zero SIDs are found. This would require a non-zero serverID also on pure forwarding servers that never changes anything by them self. But I think this minor drawback is worth it if it allows us to catch the serverID configuration errors. Syncrepl should probably allow serverID 0, so that pure consumers can exist without requiring separate serverID values. Comments? Rein

3 3

Extend slapd -c option to accept only sid=XXX?
by Rein Tollevik 09 Mar '09

09 Mar '09

There are (at least as far as I know) no other way than slapcat/slapadd to get rid of any incorrect contextCSN values, at least on servers where syncprov is enabled. I have been down that road some times already, each time being equally annoyed by the fact that there are no easier way to fix it.. Removing a contextCSN value is required in order to remove a server from a multi-master configuration, or to get rid of the values with SID=0 that is far to easy to slip in if slapd or slapadd is started without the proper serverID setting. The slapd -c option requires a rid=XXX to be specified, but also allows sid=XXX (which I haven't quite understood the usefulness of..). I suggest that the -c option is extended to also allow only sid=XXX without any rid. With only sid=XXX,csn=XXX specified both syncrepl and syncprov should replace the contextCSN value with that sid (as read from the database upon startup) with the specified csn. Obviously, only a single csn value can be accepted, and an absent or zero csn value should mean to delete the contextCSN value with that sid. Well, deleting a contextCSN value is really all I need, so I would be I more than happy to leave the replace possibility out... Adding an easy way to get rid of invalid contextCSN values should make a transition to enforcing serverID 0 for single-master only configs much more acceptable for those that have used serverID 0 in multi-master setups. Comments? Rein

2 4

Re: commit: ldap/libraries/librewrite rewrite-int.h
by Hallvard B Furuseth 08 Mar '09

08 Mar '09

hyc(a)OpenLDAP.org wrote: > rewrite-int.h 1.24 -> 1.25 > ITS#6005 librewrite must use the same mem allocators as slapd If you are killing C free/mallocs, here are some others from 'nm *.o' to look at. I don't have time at the moment. Hopefully most are malloced/freed by the same code, not passed to/from ber memory. clients/tools/common.o: free malloc clients/tools/ldapcompare.o: free malloc clients/tools/ldappasswd.o: free clients/tools/ldapsearch.o: free malloc realloc clients/tools/ldapurl.o: free realloc libraries/liblber/memory.o: free malloc calloc realloc libraries/libldap/test.o: free malloc calloc realloc libraries/libldap_r/test.o: free malloc calloc realloc libraries/liblunicode/ure.o: free malloc calloc realloc libraries/liblutil/meter.o: free calloc libraries/liblutil/passwd.o: free libraries/liblutil/sha1.o: malloc libraries/librewrite/rewrite.o: free servers/slapd/alock.o: free calloc servers/slapd/sl_malloc.o: realloc tests/progs/slapd-addel.o: malloc calloc realloc tests/progs/slapd-bind.o: free realloc tests/progs/slapd-read.o: free malloc tests/progs/slapd-search.o: realloc tests/progs/slapd-tester.o: malloc calloc -- Hallvard

2 2

multiple free in ldapsearch
by manu＠netbsd.org 07 Mar '09

07 Mar '09

Hello NetBSD's libc reports a multiple free each time I run 2.4.15's ldapsearch using x509 certificate authentication (That is, SASL EXTERNAL): Running with export MALLOC_OPTIONS=A, it is kind enough to abort, so I have a backtrace: (gdb) bt #0 0xbb94223f in kill () from /usr/lib/libc.so.12 #1 0xbb9dea64 in abort () from /usr/lib/libc.so.12 #2 0xbb9dd300 in tcgetattr () from /usr/lib/libc.so.12 #3 0xbb9dd331 in tcgetattr () from /usr/lib/libc.so.12 #4 0xbb9de661 in free () from /usr/lib/libc.so.12 #5 0xbbaff5c7 in CRYPTO_free () from /usr/lib/libcrypto.so.3 #6 0xbbad0871 in X509_asn1_meth () from /usr/lib/libcrypto.so.3 #7 0xbbaec6d7 in ASN1_primitive_free () from /usr/lib/libcrypto.so.3 #8 0xbbaec8f3 in ASN1_item_free () from /usr/lib/libcrypto.so.3 #9 0xbbad09dd in X509_free () from /usr/lib/libcrypto.so.3 #10 0xbbb6fe31 in ssl_cert_free () from /usr/lib/libssl.so.4 #11 0xbbb6d981 in SSL_CTX_free () from /usr/lib/libssl.so.4 #12 0xbbbe008f in tlso_ctx_free () from /usr/pkg/lib/libldap-2.4.so.2 #13 0xbbbdce5b in ldap_pvt_tls_ctx_free () from /usr/pkg/lib/libldap-2.4.so.2 #14 0xbbbdcf78 in ldap_int_tls_destroy () from /usr/pkg/lib/libldap-2.4.so.2 #15 0xbbbdd06e in ldap_pvt_tls_destroy () from /usr/pkg/lib/libldap-2.4.so.2 #16 0x08050e88 in ?? () #17 0x00000000 in ?? () I will investigate further if I find time, but I post this just in case it rings a bell for someone. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu(a)netbsd.org

2 1

Re: commit: ldap/servers/slapd/back-bdb operational.c
by Howard Chu 05 Mar '09

05 Mar '09

hyc(a)OpenLDAP.org wrote: > Update of /repo/OpenLDAP/pkg/ldap/servers/slapd/back-bdb > > Modified Files: > operational.c 1.32 -> 1.33 > > Log Message: > Must use txns everywhere, otherwise it will deadlock This one should have happened back on 2008-08-26 along with all the other updates for read-only txn's and BDB 4.7 support (ITS#5523). The change to test050 also turned up this deadlock. -- -- 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

Re: commit: ldap/servers/slapd syncrepl.c
by Howard Chu 05 Mar '09

05 Mar '09

hyc(a)OpenLDAP.org wrote: > Update of /repo/OpenLDAP/pkg/ldap/servers/slapd > > Modified Files: > syncrepl.c 1.449 -> 1.450 > > Log Message: > Once more, mutex_lock -> trylock... See ITS#5454 and the commit logs for this history behind this one, it's gone back and forth several times. The recent change to add a 4th server to test050 caused a config/pause deadlock to occur again. -- -- 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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-devel