- openldap-bugs - openldap.org

Re: (ITS#5409) paged results invalid sizelimit error
by hyc＠symas.com 17 Mar '08

17 Mar '08

pshao(a)zimbra.com wrote: > ------=_Part_3887_1760018525.1205731478084 Content-Type: text/plain; > charset=utf-8 Content-Transfer-Encoding: 7bit > > > I did more testing and found there is more to the bug, page size is not the > only factor. The number of results in the next search also matters. > However, in all cases, if JNDI connection pooling is disabled, then it > always works. > > Test description: > > create 10000 account: user-1 to user-10000 search size limit = 5000 > > test 1: step 1. search with filter (uid=*user*): expect > SizeLimitExceededException step 2. search with filter (uid=*user-9999*): > expect 1 entry > > test 2: step 1. search with filter (uid=*user*): expect > SizeLimitExceededException step 2. search with filter (uid=*user-10*): > expect 112 entries Please be more descriptive, re: intermittent failure - how many iterations of a test a required (on average) before the problem shows up? -- -- 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#5409) paged results invalid sizelimit error
by pshao＠zimbra.com 16 Mar '08

16 Mar '08

oops, looks my attachment in Followup 3 did not go thru. Let me know if you need the attachment.

1 0

Re: (ITS#5409) paged results invalid sizelimit error
by pshao＠zimbra.com 16 Mar '08

16 Mar '08

------=_Part_3887_1760018525.1205731478084 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit I did more testing and found there is more to the bug, page size is not the only factor. The number of results in the next search also matters. However, in all cases, if JNDI connection pooling is disabled, then it always works. Test description: create 10000 account: user-1 to user-10000 search size limit = 5000 test 1: step 1. search with filter (uid=*user*): expect SizeLimitExceededException step 2. search with filter (uid=*user-9999*): expect 1 entry test 2: step 1. search with filter (uid=*user*): expect SizeLimitExceededException step 2. search with filter (uid=*user-10*): expect 112 entries With Connection Pooling ======================= (A) page size = factor of 5000, e.g. 1000, 2500 test 1: fails intermittently, step 2 got SizeLimitExceededException while 1 entry is expected test 2: fails intermittently, step 2 got SizeLimitExceededException while 112 entry is expected (B) page size = not factor of 5000, e.g. 999, 2000 test 1: always works test 2: fails intermittently, step 2 got SizeLimitExceededException while 112 entry is expected Without Connection Pooling ========================== test 1, test 2 always work, regardless of page size. Apparently the page size and result size of test 1 in (B) somehow mask the real bug, which has to do with connection reuse. Updated test java program attached. Thanks, phoebe ------=_Part_3887_1760018525.1205731478084 Content-Type: application/octet_stream; name=TestPagedControl.java Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=TestPagedControl.java package com.zimbra.sandbox; import java.io.IOException; import java.util.ArrayList; import java.util.Hashtable; import java.util.List; import javax.naming.Context; import javax.naming.NameNotFoundException; import javax.naming.NamingEnumeration; import javax.naming.NamingException; import javax.naming.SizeLimitExceededException; import javax.naming.directory.Attribute; import javax.naming.directory.Attributes; import javax.naming.directory.DirContext; import javax.naming.directory.InvalidSearchFilterException; import javax.naming.directory.SearchControls; import javax.naming.directory.SearchResult; import javax.naming.ldap.Control; import javax.naming.ldap.InitialLdapContext; import javax.naming.ldap.LdapContext; import javax.naming.ldap.PagedResultsControl; import javax.naming.ldap.PagedResultsResponseControl; /* README: Intermittently if the max entries requested is exact multiple of page size, after a paged search hits SizeLimitExceededException, the next search also always throws a SizeLimitExceededException, even when it should not. e.g. if max requested is 5000, then page size of: 1000 => bad 2500 => bad 999 => good 2000 => good - create 10100 user entries in OpenLDAP: with uid user-0 to user-10100 - Perform the following steps in a loop 1. search (uid=*user*) with limit 5000 and paged control, expecting SizeLimitExceededException 2. search (uid=*user-10001*) with limit 5000 and paged control, expecting 1 entry returned - observed that if the limit is multiple of page size (e.g. 1000, 2500), the test failed at the second iteration when it performs 2 - it throws SizeLimitExceededException when it should find one entry. OpenLDAP returns err=4: conn=262 op=8 SRCH base="" scope=2 deref=3 filter="(uid=*user-10001*)" conn=262 op=8 SRCH attr=uid conn=262 op=8 SEARCH RESULT tag=101 err=4 nentries=0 text= otherwise (e.g. when page size is 999, or 123, or 2000) the test passes. Example test runs: --------------------------------------------------- >java TestPagedControl 1000 Testing page size 1000 iter 0 iter 1 javax.naming.SizeLimitExceededException: [LDAP: error code 4 - Sizelimit Exceeded]; remaining name '' at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3037) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2931) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2737) at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1808) at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1731) at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:368) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:338) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:321) at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:248) at TestPagedControl.testPagedControl(TestPagedControl.java:81) at TestPagedControl.doTest(TestPagedControl.java:127) at TestPagedControl.main(TestPagedControl.java:140) --------------------------------------------------- >java TestPagedControl 999 Testing page size 999 iter 0 iter 1 iter 2 iter 3 iter 4 iter 5 iter 6 iter 7 iter 8 iter 9 pass */ public class TestPagedControl { static byte[] getCookie(LdapContext lctxt) throws NamingException { Control[] controls = lctxt.getResponseControls(); if (controls != null) { for (int i = 0; i < controls.length; i++) { if (controls[i] instanceof PagedResultsResponseControl) { PagedResultsResponseControl prrc = (PagedResultsResponseControl)controls[i]; return prrc.getCookie(); } } } return null; } static List<String> testPagedControl(String query, int maxResults, int pageSize, boolean useConnPool) throws Exception { List<String> results = new ArrayList<String>(); // int total = 0; DirContext ctxt = null; try { Hashtable<String, String> env = new Hashtable<String, String>(); env.put(Context.INITIAL_CONTEXT_FACTORY, "com.sun.jndi.ldap.LdapCtxFactory"); env.put(Context.PROVIDER_URL, "ldap://localhost:389"); env.put(Context.SECURITY_AUTHENTICATION, "simple"); env.put(Context.SECURITY_PRINCIPAL, "uid=zimbra,cn=admins,cn=zimbra"); env.put(Context.SECURITY_CREDENTIALS, "zimbra"); env.put(Context.REFERRAL, "follow"); env.put("com.sun.jndi.ldap.connect.timeout", "30000"); env.put("com.sun.jndi.ldap.read.timeout", "30000"); if (useConnPool) env.put("com.sun.jndi.ldap.connect.pool", "true"); else env.put("com.sun.jndi.ldap.connect.pool", "false"); ctxt = new InitialLdapContext(env, null); String base = ""; String[] returnAttrs = {"uid"}; SearchControls searchControls = new SearchControls(SearchControls.SUBTREE_SCOPE, maxResults, 0, returnAttrs, false, false); byte[] cookie = null; LdapContext lctxt = (LdapContext)ctxt; NamingEnumeration ne = null; try { do { lctxt.setRequestControls(new Control[]{new PagedResultsControl(pageSize, cookie, Control.CRITICAL)}); ne = ctxt.search(base, query, searchControls); while (ne != null && ne.hasMore()) { // total++; SearchResult sr = (SearchResult) ne.nextElement(); String dn = sr.getNameInNamespace(); results.add(dn); } cookie = getCookie(lctxt); } while (cookie != null); } finally { if (ne != null) ne.close(); } } catch (InvalidSearchFilterException e) { throw e; } catch (NameNotFoundException e) { throw e; } catch (SizeLimitExceededException e) { throw e; } catch (NamingException e) { throw e; } catch (IOException e) { throw e; } finally { ctxt.close(); } return results; } static void test1(int pageSize, boolean useConnPool) throws Exception { /* * first search: expecting SizeLimitExceededException */ boolean good = false; try { testPagedControl("(uid=*user*)", 5000, pageSize, useConnPool); } catch (SizeLimitExceededException e) { good = true; } if (!good) throw new Exception("expecting SizeLimitExceededException"); List<String> results; /* * second search: expecting one result */ results = testPagedControl("(uid=*user-9999*)", 5000, pageSize, useConnPool); // for (String s : results) System.out.println(s); if (results.size() != 1) throw new Exception("expecting 1 result, got " + results.size()); } static void test2(int pageSize, boolean useConnPool) throws Exception { /* * first search: expecting SizeLimitExceededException */ boolean good = false; try { testPagedControl("(uid=*user*)", 5000, pageSize, useConnPool); } catch (SizeLimitExceededException e) { good = true; } if (!good) throw new Exception("expecting SizeLimitExceededException"); List<String> results; /* * second search: expecting 112 results */ results = testPagedControl("(uid=*user-10*)", 5000, pageSize, useConnPool); // for (String s : results) System.out.println(s); if (results.size() != 112) throw new Exception("expecting 112 result, got " + results.size()); } private static void usage() { System.out.println("usage: TestPagedControl <page size> <whcih test 1|2> <use conn pool: true|false>"); } public static void main(String[] args) { if (args.length != 3) { usage(); System.exit(1); } int pageSize = Integer.parseInt(args[0]); int test = Integer.parseInt(args[1]); boolean useConnPool = Boolean.parseBoolean(args[2]); System.out.println("Testing page size " + pageSize); try { for (int i=0; i<10; i++) { System.out.println(" iter " + i); if (test == 1) test1(pageSize, useConnPool); else if (test == 2) test2(pageSize, useConnPool); else { usage(); System.exit(1); } } System.out.println("pass"); } catch (Exception e) { e.printStackTrace(); } } } ------=_Part_3887_1760018525.1205731478084--

1 0

Re: (ITS#5412) Add operation should not require naming attrs
by h.b.furuseth＠usit.uio.no 16 Mar '08

16 Mar '08

ando(a)sys-net.it writes: >> slapadd: tools.c:494: bdb_tool_entry_put: Assertion `text->bv_val[0] == >> '\0'' failed. > > I only tested with ldapadd, but at a glance I don't see what could be the > difference. The protocol Add operation doesn't run into that assert. Have only looked briefly at the code, but I guess entry_schema_check()'s params textbuf[0] (and textlen?) must be zeroed if they were filled with a message but entry_schema_check() returns success anyway. Don't know where (in which function) that should be done though. -- Hallvard

1 0

Re: (ITS#5412) Add operation should not require naming attrs
by ando＠sys-net.it 16 Mar '08

16 Mar '08

> slapadd: tools.c:494: bdb_tool_entry_put: Assertion `text->bv_val[0] == > '\0'' failed. I only tested with ldapadd, but at a glance I don't see what could be the difference. Unfortunately I won't be able to work at it/connect for a while (a week or so); I ran the whole test suite and this fix shouldn't break any existing test, in the meanwhile. 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 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: (ITS#5412) Add operation should not require naming attrs
by h.b.furuseth＠usit.uio.no 16 Mar '08

16 Mar '08

Pierangelo Masarati writes: > Patched in HEAD; please test. p. test.conf: include servers/slapd/schema/core.schema database bdb suffix o=foo directory /tmp/db test.ldif: dn: o=foo objectClass: organization $ servers/slapd/slapadd -f test.conf < test.ldif ... slapadd: tools.c:494: bdb_tool_entry_put: Assertion `text->bv_val[0] == '\0'' failed. -- Hallvard

1 0

Re: (ITS#5412) Add operation should not require naming attrs
by ando＠sys-net.it 15 Mar '08

15 Mar '08

h.b.furuseth(a)usit.uio.no wrote: > slapd and slapadd should generate them if they are missing. Patched in HEAD; please test. 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 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: (ITS#5412) Add operation should not require naming attrs
by ando＠sys-net.it 15 Mar '08

15 Mar '08

h.b.furuseth(a)usit.uio.no wrote: > A somewhat belated ITS: ldapadd of > dn: o=foo > objectClass: organization > complains that "naming attribute 'o' is not present in entry". > RFC 2251 required this, but RFC 4511 changed it to the opposite: > The RDN attrs need not be present in AddRequest.attributes. > > slapd and slapadd should generate them if they are missing. I'm patching HEAD code in this sense. For this purpose, I decided to hijack the add_soc parameter of entry_schema_check() that controlled adding the structural objectClass. In fact, in the current code so far I couldn't find any call to that function where the structural objectClass had to be added and the naming attributes hadn't. If this distinction becomes necessary the parameter can be used as a mask instead of a boolean. > I don't know if the change belongs in RE23. re23 claims to comply with rfc 2251-2256, and knows nothing of rfc 4510-4519, so IMHO it shouldn't be affected. 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 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

(ITS#5428) Enhancement: allow slapo-refint(5) to implement global referential integrity
by ando＠sys-net.it 15 Mar '08

15 Mar '08

Full_Name: Pierangelo Masarati Version: HEAD OS: irrelevant URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (82.63.140.131) Submitted by: ando See <http://www.openldap.org/lists/openldap-technical/200803/msg00068.html> for discussion. p.

1 0

(ITS#5427) slapo-refint(5) erroneously uses smr_str field for dnSubtreeMatch
by ando＠sys-net.it 15 Mar '08

15 Mar '08

Full_Name: Pierangelo Masarati Version: HEAD/re24 OS: irrelevant URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (82.63.140.131) Submitted by: ando The right field is smr_bvoid (or smr_names[0]). p.

1 0

(ITS#5426) syncrepl and syncprov clash on contextCSN updates
by hyc＠OpenLDAP.org 14 Mar '08

14 Mar '08

Full_Name: Howard Chu Version: 2.4/HEAD OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (76.91.220.157) Submitted by: hyc If syncprov-checkpoint is configured on a database with a syncrepl consumer (either for cascaded syncrepl or for mirrormode), the syncrepl consumer may fail to update the contextCSN because syncprov updates it first. In 2.4 the syncrepl consumer tries to delete its old value and add the new value, instead of just doing a modify/Replace as it used to in 2.3. The 2.4 consumer was changed in this respect because multiple consumers are now allowed on a database, thus using multiple values in the contextCSN attribute. Replacing the entire attribute when only a single value needed to change seemed like the wrong thing to do. The syncprov overlay still just uses a modify/Replace, so it doesn't have this problem. Since both syncrepl and syncprov now currently track all of the contextCSNs in use, probably syncrepl should just be switched back to using modify/Replace, with the full list of known contextCSNs.

1 0

Re: Adding new Attribute in OpenLdap (ITS#5423)
by ando＠sys-net.it 14 Mar '08

14 Mar '08

vijayaragavanp(a)zenithsoft.com wrote: > i was't able to find the manual ,can you please send me the link Please send software usage requests to the OpenLDAP-software mailing list. The ITS is to track software bug. 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 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

(ITS#5425) slapdconfig.sdf and slapdconf2.sdf out of date
by ghenry＠OpenLDAP.org 14 Mar '08

14 Mar '08

Full_Name: Gavin Henry Version: HEAD OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (80.229.93.1) Submitted by: ghenry Note to self: These are missing the latest Syncrepl directives and others things. Need to sync them with slapd.conf(5)

1 0

RE: Adding new Attribute in OpenLdap (ITS#5423)
by vijayaragavanp＠zenithsoft.com 14 Mar '08

14 Mar '08

i was't able to find the manual ,can you please send me the link -----Original Message----- From: Pierangelo Masarati [mailto:openldap-its@OpenLDAP.org] Sent: Friday, March 14, 2008 2:46 PM To: vijayaragavanp(a)zenithsoft.com Subject: Re: Adding new Attribute in OpenLdap (ITS#5423) > how to add custom attributes in OpenLdap As clearly explained in the manual. p.

1 0

(ITS#5424) pwdGraceLoginLimit only mentioned, not documented in slapo-ppolicy
by ghenry＠OpenLDAP.org 14 Mar '08

14 Mar '08

Full_Name: Gavin Henry Version: HEAD OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (212.159.59.85) Submitted by: ghenry "(please refer to the pwdGraceLoginLimit password policy attribute)" Nothing else mentioned. Gavin.

1 0

(ITS#5423) Adding new Attribute in OpenLdap
by vijayaragavanp＠zenithsoft.com 13 Mar '08

13 Mar '08

Full_Name: vijayaragavanp Version: 2.0 OS: yes URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (124.30.128.168) how to add custom attributes in OpenLdap

1 0

(ITS#5422) strerror(errno) problems
by h.b.furuseth＠usit.uio.no 13 Mar '08

13 Mar '08

Full_Name: Hallvard B Furuseth Version: HEAD, RE23, RE24 OS: URL: Submission from: (NULL) (129.240.6.233) Submitted by: hallvard "grep -i strerror" shows some places <strerror/STRERROR>(errno) are passed to Debug(). However Debug() can evaluate its arguments twice: for -d output and syslog. Thus it can syslog the wrong message, since the -d stdio call can change errno. Also strerror() can return NULL, which can break with Debug(%s). STRERROR() fixes that, but not the duplicate call. And strerror too can change errno:-( So the STRERROR() variant #elif defined( HAVE_STRERROR ) #define STRERROR(e) ( strerror(e) ? strerror(e) : _AC_ERRNO_UNKNOWN ) in include/ac/errno.h isn't quite safe either. I suggest we put something like below in ac/string.h or ac/errno.h, then we can usually say if (whatever) { DEF_STRERROR(msg, errno); Debug(..., msg, ...); } ac/something.h: #define DEF_STRERROR(msg, err) \ DECL_STRERROR(msg); \ SET_STRERROR(msg, err) #ifdef HAVE_SYS_ERRLIST #define DECL_STRERROR(msg) \ unsigned int msg##_err_; \ const char *msg #define SET_STRERROR(msg, err) \ ((void)(msg = (msg##_err_ = (e)) < (unsigned) sys_nerr \ ? sys_errlist[msg##_err_] : _AC_ERRNO_UNKNOWN)) #elif <threaded> && defined( HAVE_NONPOSIX_STRERROR_R ) #define DECL_STRERROR(msg) \ char msg##_buf_[80]; \ const char *msg #define SET_STRERROR(msg, err) \ ((void) ((msg = strerror_r(err, msg##_buf_, 80)) || \ (msg = _AC_ERRNO_UNKNOWN))) #elif <threaded> && defined( HAVE_STRERROR_R ) #define DECL_STRERROR(msg) \ char msg##_buf_[80]; \ const char *msg #define SET_STRERROR(msg, err) \ ((void) (msg = strerror_r(err, msg##_buf_, 80) != -1 \ ? msg##_buf_ : _AC_ERRNO_UNKNOWN)) #elif defined( HAVE_STRERROR ) #define DECL_STRERROR(msg) \ const char *msg #define SET_STRERROR(msg, err) \ ((void) ((msg = strerror(err)) || (msg = _AC_ERRNO_UNKNOWN))) #else #define DECL_STRERROR(msg) const char *msg #define SET_STRERROR(msg, err) ((void) (msg = "Unknown error")) #endif Don't know what the #if <threaded> test should look like, see ITS#5421.

1 0

(ITS#5421) slapd vs LDAP_R_COMPILE
by h.b.furuseth＠usit.uio.no 13 Mar '08

13 Mar '08

Full_Name: Hallvard B Furuseth Version: HEAD, RE23, RE24 OS: URL: Submission from: (NULL) (129.240.6.233) Submitted by: hallvard Some slapd source files include libldap/ldap-int.h, which contains #ifdef LDAP_R_COMPILE in structs. slapd links libldap_r but does not define LDAP_R_COMPILE, so these files have access to bad struct definitions. A quick grep doesn't show any use cases though. Anyway: Either #ifdef LDAP_R_COMPILE in libldap(_r)should be something else, or we should define LDAP_R_COMPILE in slapd - maybe like this: --- slap.h 13 Mar 2008 13:37:07 +++ slap.h 13 Mar 2008 16:40:25 @@ -28,4 +28,10 @@ #define _SLAP_H_ +#if defined _LDAP_INT_H +# error include slap.h before ldap-int.h +#elif !defined NO_THREADS +# define LDAP_R_COMPILE 1 +#endif + #include "ldap_defaults.h"

1 0

Re: (ITS#5416) slapd core dump
by ando＠sys-net.it 13 Mar '08

13 Mar '08

rui.yan(a)gmail.com wrote: > Full_Name: yanr > Version: 2.4.8 > OS: Linux 2.6.22 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (128.221.197.21) > > > Verion: 2.4.8 > Desc: client runs some codes like ldap_modify_ext, sometimes slapd core dump. > The same codes works on 2.3.38. > > [root@test1 /]# uname -r > 2.6.22.9-2.smp.gcc3.4.x86_64 > > (gdb) bt > > #0 0x00002b018fa6da3d in *__GI_raise (sig=19040) > at ../nptl/sysdeps/unix/sysv/linux/raise.c:67 > 67 int res = INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); > (gdb) bt > #0 0x00002b018fa6da3d in *__GI_raise (sig=19040) > at ../nptl/sysdeps/unix/sysv/linux/raise.c:67 > #1 0x00002b018fa6ef1e in *__GI_abort () at ../sysdeps/generic/abort.c:88 > #2 0x00002b018fa67720 in *__GI___assert_fail (assertion=0x56ad43 "i > 0", > file=0x56acf8 "schema_init.c", line=366, > function=0x56ad30 "octetStringIndexer") at assert.c:83 > #3 0x00000000004664b3 in octetStringIndexer (use=163, flags=4, > syntax=0x77ea70, mr=0x77ed70, prefix=0x77ec48, values=0x2aaaaacad6b0, > keysp=0x42001598, ctx=0x83d970) at schema_init.c:366 > #4 0x000000000046ffde in objectSubClassIndexer (use=163, mask=4, > syntax=0x77ea70, mr=0x77ed70, prefix=0x77ec48, values=0x87b7e0, > keysp=0x42001598, ctx=0x83d970) at schema_prep.c:305 You should provide: - your slapd.conf - the LDIF of the modification that caused the issue - the contents of some variables from gdb: (gdb) frame 4 (gdb) print nocs (gdb) print values (gdb) print values[0] 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 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: (ITS#5420) test048-syncrepl-multiproxy: ldapsearch failed at P1 slave (32)!
by hyc＠symas.com 13 Mar '08

13 Mar '08

Dup of ITS#5419. michael(a)stroeder.com wrote: > Full_Name: Michael Ströder > Version: HEAD > OS: OpenSUSE Linux 10.3 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (84.163.68.253) > > > make test fails with current HEAD synced right now. > > michael@nb2:~/src/openldap/HEAD/openldap/tests> ./run -b bdb test048 > Cleaning up test run directory leftover from previous run. > Running ./scripts/test048-syncrepl-multiproxy... > running defines.sh > Starting master slapd on TCP/IP port 9011... > Using ldapsearch to check that master slapd is running... > Using ldapadd to create the context prefix entry in the master... > Starting P1 slave slapd on TCP/IP port 9012... > Using ldapsearch to check that P1 slave slapd is running... > Starting R1 slave slapd on TCP/IP port 9013... > Using ldapsearch to check that R1 slave slapd is running... > 1> Using ldapadd to populate the master directory... > Waiting 15 seconds for syncrepl to receive changes... > ldapsearch failed at P1 slave (32)! > > > -- -- 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

(ITS#5420) test048-syncrepl-multiproxy: ldapsearch failed at P1 slave (32)!
by michael＠stroeder.com 13 Mar '08

13 Mar '08

Full_Name: Michael Ströder Version: HEAD OS: OpenSUSE Linux 10.3 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (84.163.68.253) make test fails with current HEAD synced right now. michael@nb2:~/src/openldap/HEAD/openldap/tests> ./run -b bdb test048 Cleaning up test run directory leftover from previous run. Running ./scripts/test048-syncrepl-multiproxy... running defines.sh Starting master slapd on TCP/IP port 9011... Using ldapsearch to check that master slapd is running... Using ldapadd to create the context prefix entry in the master... Starting P1 slave slapd on TCP/IP port 9012... Using ldapsearch to check that P1 slave slapd is running... Starting R1 slave slapd on TCP/IP port 9013... Using ldapsearch to check that R1 slave slapd is running... 1 > Using ldapadd to populate the master directory... Waiting 15 seconds for syncrepl to receive changes... ldapsearch failed at P1 slave (32)!

1 0

Re: (ITS#5419) test048 fails...
by h.b.furuseth＠usit.uio.no 13 Mar '08

13 Mar '08

hyc(a)symas.com writes: > op->o_bd is essentially supposed to be a constant once it is set on an > operation. Operations within a backend are generally not allowed to > access other backends so it should not be overriding the backend that > was given to it. "grep -n -e '.->o_bd *=[^=]' *.c */*.c" finds 10 from 'orig'something. Some of the other 202 matches also restore an old o_bd. -- Hallvard

1 0

Re: (ITS#5419) test048 fails...
by hyc＠symas.com 13 Mar '08

13 Mar '08

luca(a)OpenLDAP.org wrote: > Full_Name: Luca Scamoni > Version: HEAD > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (82.63.140.131) > > > consistently > > Running ./scripts/test048-syncrepl-multiproxy... > running defines.sh > Starting master slapd on TCP/IP port 9011... > Using ldapsearch to check that master slapd is running... > Using ldapadd to create the context prefix entry in the master... > Starting P1 slave slapd on TCP/IP port 9012... > Using ldapsearch to check that P1 slave slapd is running... > Starting R1 slave slapd on TCP/IP port 9013... > Using ldapsearch to check that R1 slave slapd is running... > 1> Using ldapadd to populate the master directory... > Waiting 15 seconds for syncrepl to receive changes... > ldapsearch failed at P1 slave (32)! > > modifications to the master are not propagated to the slaves Yes, I see this as well. syncrepl is trying to use backend_attribute() to retrieve the underlying DB's contextCSN, but backend_attribute is discarding the current op->o_bd and using select_backend() to pick which backend to query. This is definitely the wrong behavior; op->o_bd is essentially supposed to be a constant once it is set on an operation. Operations within a backend are generally not allowed to access other backends so it should not be overriding the backend that was given to it. -- -- 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#5391) hdb deadlock
by h.b.furuseth＠usit.uio.no 13 Mar '08

13 Mar '08

hyc(a)symas.com writes: >Hallvard B Furuseth wrote: >> How about making #bytes-based checkpoints signal or (pthread_kill?) the >> timed checkpoints thread, so that thread can handle all checkpoints? > > It's an interesting idea. But that means we have to count bytes ourselves, > rather than letting BerkeleyDB do it. Whoops, good point. > Personally I don't think byte counts are very useful here. They're made > somewhat superfluous because the data volume will tend to cause the > transaction log buffers to fill up and be flushed regardless. I don't think Berkeley DB writes a checkpoint record then, at least I don't see that in the docs. If not, #bytes do help keep recovery and checkpoint times down. Anyway, unless you are proposing to ignore the #bytes parameter: If this is a Berkeley DB bug we could hear what they say, and in the meantime put a mutex_trylock around checpoints. Unless db has some feature which defeats that, like if txn_checkpoint() merely schedules a checkpoint. #define CHECKPOINT_WORKAROUND /* hopefully an ITS#5391 workaround */ struct bdb_info { ... #ifdef CHECKPOINT_WORKAROUND # ldap_pvt_thread_mutex_t bi_checkpoint_mutex; #define CHECKPOINT_LOCK(op, bdb) op(&(bdb)->bi_checkpoint_mutex) #else #define CHECKPOINT_LOCK(op, bdb) 0 #endif ... }; #define TXN_CHECKPOINT(bdb, k, m, f) do { \ if ( CHECKPOINT_LOCK( ldap_pvt_thread_mutex_trylock, bdb ) == 0 ) { \ (bdb)->bi_dbenv->txn_checkpoint( (bdb)->bi_dbenv, k, m, f ); \ (void) CHECKPOINT_LOCK( ldap_pvt_thread_mutex_unlock, bdb ); \ } \ } while (0) -- Hallvard

1 0

Re: (ITS#4730) Overlay that generates operational attributes to support GUI interaction
by jclarke＠linagora.com 13 Mar '08

13 Mar '08

Hi, michael(a)stroeder.com a écrit : > I'd be interested to add support for something like this to my LDAP client. > > BTW: I'd vote against ";x-allowed" or ";x-required" since a schema-aware > client can already determine this in a non-proprietary way from the subschema. > > The overlay's source is quite old. Does it still build with recent HEAD? I'm also interested in an overlay of this type. I started hacking into it recently, and don't remember any problems getting it to build on HEAD (a couple of months ago). This was related to an implementation of Get Effective Rights [1], which returns rights the current user has on each attribute in an object. I had a premilinary working version, but it did not work as a control, just returned extra attributes. Similarly, this would be useful to LDAP GUI clients. If you're interested, I could dig out the code. [1] http://directory.fedoraproject.org/wiki/Get_Effective_Rights_Design and http://www.ietf.org/proceedings/01dec/I-D/draft-ietf-ldapext-acl-model-08.t… Regards, Jonathan -- Jonathan Clarke Cellule OSSA - Groupe LINAGORA 27 rue de Berri, 75008 Paris Tél: 01 58 18 68 28, fax: 01 58 18 68 29 http://www.linagora.com - http://www.08000linux.com

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs