openldap-bugs

openldap-bugs@openldap.org

1 participants
20963 discussions

(ITS#8270) win32: fix conversion error
by nacho.resa＠gmail.com 15 Oct '15

15 Oct '15

Full_Name: Ignacio Casal Quinteiro Version: OS: Windows 7 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (2a01:111f:9fa:7f00:864b:f5ff:fe34:ddaa) https://github.com/nice-software/lmdb/commit/076281a2c03356667fca7cce1a898a…

1 0

(ITS#8269) win32: avoid warning about using strdup instead of _strdup
by nacho.resa＠gmail.com 15 Oct '15

15 Oct '15

Full_Name: Ignacio Casal Quinteiro Version: OS: Windows 7 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (2a01:111f:9fa:7f00:864b:f5ff:fe34:ddaa) You can find the patch here: https://github.com/nice-software/lmdb/commit/67a61ed18ddb978f4e58198ca55b97…

1 0

Re: (ITS#7771) liblmdb cursor issues
by h.b.furuseth＠usit.uio.no 12 Oct '15

12 Oct '15

I wrote: > mdb_subcursor(MDB_cursor *mc) > (...) > if (((mc->mc_flags | subc->mc_flags) & C_INITIALIZED) && Oops. For reference, the '|' should be '&'. mdb.master has now been fixed to work without this function, though. -- Hallvard

1 0

Re: (ITS#7771) liblmdb cursor issues
by h.b.furuseth＠usit.uio.no 11 Oct '15

11 Oct '15

On 22/12/13 23:09, h.b.furuseth(a)usit.uio.no wrote: > I.e. lots more code needs something like > if ((leaf->mn_flags & (F_DUPDATA|F_SUBDATA)) == F_DUPDATA) > m2->mc_xcursor->mx_cursor.mc_pg[0] = NODEDATA(leaf); > before using an xcursor. I tried that everywhere before > using xcursors: That helped, but it was not enough. E.g. > after mdb_cursor_del() calls mdb_node_shrink(), it tracks > cursors in the same sub-page but not nearby sub-pages. Such fixups do heal this ITS's test program with current mdb.master, though. That is, perl -i -pe ' s/\b(\w+)->mc_xcursor->mx_cursor\./mdb_subcursor($1)->/gx; s/\&(\w+)->mc_xcursor->mx_cursor/mdb_subcursor($1)/gx;' mdb.c plus this function: static MDB_cursor * mdb_subcursor(MDB_cursor *mc) { MDB_xcursor *mx = mc->mc_xcursor; MDB_cursor *subc = NULL; MDB_page *mp = mc->mc_pg[mc->mc_top]; if (mx) { subc = &mx->mx_cursor; if (((mc->mc_flags | subc->mc_flags) & C_INITIALIZED) && mp && !(mp->mp_flags & (P_BRANCH|P_LEAF2|P_SUBP))) { MDB_node *leaf = NODEPTR(mp, mc->mc_ki[mc->mc_top]); if ((leaf->mn_flags & (F_SUBDATA|F_DUPDATA)) == F_DUPDATA) subc->mc_pg[0] = NODEDATA(leaf); } } return subc; }

1 0

ITS#8267
by ingo.voss＠gmail.com 11 Oct '15

11 Oct '15

Hello, after rereading, I=E2=80=99ve made a few changes in the manual page, so tha= t the old tar package can be discarded. Please use instead the old package now: ftp://ftp.openldap.org/incoming/contrib-slapd-modules-unicodepw-151011.tar Thanks, kindly regards Ingo Voss

1 0

(ITS#8268) slapd-ldap quarantine, per configuration retries fail
by nvoutsin＠gmai.com 11 Oct '15

11 Oct '15

Full_Name: Nikos Voutsinas Version: 2.4.42 OS: Solaris/Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (62.38.193.214) Hi, In a 4-nodes MMR deployment with a 2-nodes LDAP Proxy Front-ends, we have repeatedly noticed that whenever the connection recovery method falls into the quarantine code, it fails. i.e. when all the back-end ldap servers become unavailable, for some reason, slapd-ldap fails to follow the retry scheme that is dictated by olcDbQuarantine. In our case we set olcDbQuarantine to: 10,30;60,+ and when we got a temporary network timeout from all back-end ldap server this is what we saw in the slapd logs. Oct 7 21:30:58 proxy slapd[330]: conn=632725 op=0 ldap_back_retry: retrying URI="ldap://back01 ldap://back02" DN="" Oct 7 21:30:58 proxy slapd[330]: conn=632725 op=0: ldap_back_quarantine enter. Oct 7 21:31:08 proxy slapd[330]: conn=632759 op=0: ldap_back_getconn quarantine retry block #0 try #0. After that the only method to recover was either to restart the whole process or reset the value of olcDbQuarantine. Thanks, Nikos

1 0

(ITS#8267) contributing a new overlay unicodepw
by ingo.voss＠gmail.com 10 Oct '15

10 Oct '15

Full_Name: Ingo Voss Version: OS: URL: ftp://ftp.openldap.org/incoming/contrib-slapd-modules-unicodepw.tar Submission from: (NULL) (78.53.86.212) Hello, I wrote a small overlay, that restricts all LDAP modification requests, so that only password changes for MS unicodePwd are possible. All other LDAP requests will not be observed. If someone needs a read-only proxy (in a e.g. dmz) for an MS Active Directory, but password changes must be possible, then unicodepw is the right overlay. For more informations, a manual page is included. Kindly regards Ingo Voss

1 0

(ITS#8266) empty ldapmodify refused with slapo-unique
by geert＠hendrickx.be 08 Oct '15

08 Oct '15

Full_Name: Geert Hendrickx Version: 2.4.42 OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (212.123.14.2) When slapo-unique constraints are in effect, it seems empty updates are no longer allowed: $ ldapmodify -x -h localhost -D cn=Manager,dc=my-domain,dc=com -w secret dn: cn=test1,dc=my-domain,dc=com changetype: modifyA%A modifying entry "cn=test1,dc=my-domain,dc=com" ldap_modify: Invalid syntax (21) additional info: unique_modify() got null op.orm_modlist Why is this considered invalid syntax? Without slapo-unique constraint, empty updates like these are accepted.

1 0

Re: (ITS#8263) Broken cursor tracking in mdb_cursor_put()
by h.b.furuseth＠usit.uio.no 06 Oct '15

06 Oct '15

On 07/10/15 07:37, Howard Chu wrote: > Note: It's tempting to just merge the new xcursor_init2 function into > xcursor_init1 since they're very similar, but that's a bad idea. The > xcursor_init1 function really is meant for init'ing an unused cursor; > it's expected that immediately after, a full cursor-positioning action > will occur. > > xcursor_init2 is meant for xcursors that have already been positioned, > in which case their physical position is updated in order to keep their > logical position unchanged. Maybe you should document that in the code instead of in a mail message.

1 0

Re: (ITS#8263) Broken cursor tracking in mdb_cursor_put()
by hyc＠symas.com 06 Oct '15

06 Oct '15

h.b.furuseth(a)usit.uio.no wrote: > Full_Name: Hallvard B Furuseth > Version: mdb.master, 8b46dcc26d1e9897ab1da3a4a164cad4a4479a52 > OS: Linux x86_64 > URL: ftp://ftp.openldap.org/incoming/Hallvard-Furuseth-151005.c > Submission from: (NULL) (81.191.45.5) > Submitted by: hallvard > > > The test program catches several cursor tracking bugs. > It works when the DUPSORT sub-DB is created immediately: Yes, when using a fake page we init the subcursor with the fake page. When using a full sub-DB we left the subcursor pointing to the sub-DB but otherwise uninit'd. > > $ ./a.out 1500 > mn_flags = 6 <repeated 22 times> Fixed now in mdb.master. Note: It's tempting to just merge the new xcursor_init2 function into xcursor_init1 since they're very similar, but that's a bad idea. The xcursor_init1 function really is meant for init'ing an unused cursor; it's expected that immediately after, a full cursor-positioning action will occur. xcursor_init2 is meant for xcursors that have already been positioned, in which case their physical position is updated in order to keep their logical position unchanged. -- -- 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:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs