- openldap-bugs - openldap.org

Re: (ITS#5061) client/tools: Password Policy control handling
by kurt＠OpenLDAP.org 13 Aug '07

13 Aug '07

Given the ppolicy change backport for everything else was straight forward for every other command, and committed, seems reasonable to keep it. Ando and/or I likely can do a quick backport for ldapmodify.c. -- Kurt

1 0

Re: (ITS#5061) client/tools: Password Policy control handling
by kurt＠OpenLDAP.org 13 Aug '07

13 Aug '07

On Aug 13, 2007, at 6:06 PM, quanah(a)zimbra.com wrote: > --On July 23, 2007 6:51:35 PM +0000 kurt(a)OpenLDAP.org wrote: > >> Full_Name: Kurt Zeilenga >> Version: 2.3 >> OS: Mac OS X >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (130.129.101.249) >> Submitted by: kurt >> >> >> 2.3 (and 2.4) client tools only send the password policy control >> with the >> Bind requests. However, the control is not only valid with most >> every >> request, but useful to send with every request. HEAD has been >> updated >> to send, when -e ppolicy is selected, the control with every >> request, and >> to print the control details on return. While this could be >> viewed as a >> new feature by some it could abe viewed as a bug fix by others. >> Given >> this change scope is quite narrow (should only effect -e ppolicy >> users), >> I recommend it inclusion in the next patch release of 2.3. > > Hi Kurt, > > I've been working on this for the 2.3 release, however there is a > problem > when it comes to ldapmodify. Pierangelo made the change around > controls to > the ldapmodify code around revision 1.172. However, when 2.3 was > branched > (after revision 1.175), this new code was excluded by you. So, the > question I have now, is should this code now be pulled into 2.3? > It is > quite a bit of change. > > --Quanah If 2.3 wasn't quite frozen, I'd say just suck in the new tools... But given 2.3 is very much frozen, and the change scope isn't as narrow as I thought it would be, seems more appropriate just to leave this out. Oh well. Another reason to push 2.4beta out, I guess. -- Kurt

1 0

Re: (ITS#5061) client/tools: Password Policy control handling
by quanah＠zimbra.com 13 Aug '07

13 Aug '07

--On July 23, 2007 6:51:35 PM +0000 kurt(a)OpenLDAP.org wrote: > Full_Name: Kurt Zeilenga > Version: 2.3 > OS: Mac OS X > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (130.129.101.249) > Submitted by: kurt > > > 2.3 (and 2.4) client tools only send the password policy control with the > Bind requests. However, the control is not only valid with most every > request, but useful to send with every request. HEAD has been updated > to send, when -e ppolicy is selected, the control with every request, and > to print the control details on return. While this could be viewed as a > new feature by some it could abe viewed as a bug fix by others. Given > this change scope is quite narrow (should only effect -e ppolicy users), > I recommend it inclusion in the next patch release of 2.3. Hi Kurt, I've been working on this for the 2.3 release, however there is a problem when it comes to ldapmodify. Pierangelo made the change around controls to the ldapmodify code around revision 1.172. However, when 2.3 was branched (after revision 1.175), this new code was excluded by you. So, the question I have now, is should this code now be pulled into 2.3? It is quite a bit of change. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#5090) Error with attribute "jpegPhoto"
by ando＠sys-net.it 13 Aug '07

13 Aug '07

nicolas.sandraz(a)gmail.com wrote: Fixed in HEAD & re23; 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#5090) Error with attribute "jpegPhoto"
by ando＠sys-net.it 13 Aug '07

13 Aug '07

Howard Chu wrote: > ando(a)sys-net.it wrote: >> marg(a)rz.tu-clausthal.de wrote: >>> Oh, and that special syntax is a function of ldapadd/ldapmodify, not >>> some standard way of importing images - so using it with slapadd >>> won't work. > > Not true. Both slapadd and ldapadd use the same LDIF reading routines; > they have since 2.3 was first released. All valid LDIF is accepted > identically by both programs. > >> well, that's a SHOULD in RFC2849, so it is indeed a standard way of >> importing values (works with any value) using LDIF. The fact it doesn't >> work with slapadd should be seen as a limitation of that tool, which it >> is not intended for use with arbitrary LDIF but rather with LDIF >> produced by slapcat. Well, I need to take both my claims back; I was writing jpegPhoto: <file///... while the right syntax (still with the missing ":") is jpegPhoto:< file///... and the error is still there in 2.3. I'll fix it in a moment. 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#5090) Error with attribute "jpegPhoto"
by hyc＠symas.com 13 Aug '07

13 Aug '07

ando(a)sys-net.it wrote: > marg(a)rz.tu-clausthal.de wrote: >> Oh, and that special syntax is a function of ldapadd/ldapmodify, not >> some standard way of importing images - so using it with slapadd won't work. Not true. Both slapadd and ldapadd use the same LDIF reading routines; they have since 2.3 was first released. All valid LDIF is accepted identically by both programs. > well, that's a SHOULD in RFC2849, so it is indeed a standard way of > importing values (works with any value) using LDIF. The fact it doesn't > work with slapadd should be seen as a limitation of that tool, which it > is not intended for use with arbitrary LDIF but rather with LDIF > produced by slapcat. -- -- 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#5090) Error with attribute "jpegPhoto"
by ando＠sys-net.it 13 Aug '07

13 Aug '07

marg(a)rz.tu-clausthal.de wrote: >> i use this line (on my ldif file) to add a picture on my LDAP directory: >> >> jpegPhoto: < file///etc/ldap/pictures/test.jpg > > Are you sure that you aren't missing a colon (':')? According to the > manpage of ldapadd the line should look like this: > > jpegPhoto: < file:///etc/ldap/pictures/test.jpg Moreover, this bug appears to have already been fixed. It is recommended to check the latest version before reporting bugs. > Oh, and that special syntax is a function of ldapadd/ldapmodify, not > some standard way of importing images - so using it with slapadd won't work. well, that's a SHOULD in RFC2849, so it is indeed a standard way of importing values (works with any value) using LDIF. The fact it doesn't work with slapadd should be seen as a limitation of that tool, which it is not intended for use with arbitrary LDIF but rather with LDIF produced by slapcat. 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#5090) Error with attribute "jpegPhoto"
by marg＠rz.tu-clausthal.de 13 Aug '07

13 Aug '07

Hello, nicolas.sandraz(a)gmail.com wrote: > when i use a LDIF file with the falowing attribute jpegPhoto associate with the > object class inetOrgPerson i have this error: > > slapadd : /tmp/build/openldap2.3-2.3.30/servers/slapd/schema_check.c:87 : > entry_schema_check: Assertion `a->a_vals[0].bv_val != ((void *)0)' failed. > > i use this line (on my ldif file) to add a picture on my LDAP directory: > > jpegPhoto: < file///etc/ldap/pictures/test.jpg Are you sure that you aren't missing a colon (':')? According to the manpage of ldapadd the line should look like this: jpegPhoto: < file:///etc/ldap/pictures/test.jpg Oh, and that special syntax is a function of ldapadd/ldapmodify, not some standard way of importing images - so using it with slapadd won't work. bye Christian -- Christian Marg mail : mailto:marg@rz.tu-clausthal.de Dezernat 2 TU Clausthal web : http://www.tu-clausthal.de D-38678 Clausthal-Zellerfeld fon : 05323/72-2107 Germany jabber: ifcma(a)jabber.tu-clausthal.de

1 0

(ITS#5090) Error with attribute "jpegPhoto"
by nicolas.sandraz＠gmail.com 13 Aug '07

13 Aug '07

Full_Name: Sandraz Nicolas Version: 2.3.30 OS: Linux (debian Etch) URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (81.252.72.177) when i use a LDIF file with the falowing attribute jpegPhoto associate with the object class inetOrgPerson i have this error: slapadd : /tmp/build/openldap2.3-2.3.30/servers/slapd/schema_check.c:87 : entry_schema_check: Assertion `a->a_vals[0].bv_val != ((void *)0)' failed. i use this line (on my ldif file) to add a picture on my LDAP directory: jpegPhoto: < file///etc/ldap/pictures/test.jpg note: when i remove this line from my ldif file i can import all information!

1 0

(ITS#5089) test043-delta-syncrepl: test failed - producer and consumer databases differ
by michael＠stroeder.com 11 Aug '07

11 Aug '07

Full_Name: Michael Ströder Version: HEAD OS: openSUSE 10.2 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (83.124.34.52) Running ./scripts/test043-delta-syncrepl... running defines.sh Starting producer slapd on TCP/IP port 9011... Using ldapsearch to check that producer slapd is running... Using ldapadd to create the context prefix entries in the producer... Starting consumer slapd on TCP/IP port 9012... Using ldapsearch to check that consumer slapd is running... Waiting 5 seconds for slapd to start... Using ldapadd to populate the producer directory... Waiting 15 seconds for syncrepl to receive changes... Stopping the provider, sleeping 10 seconds and restarting it... Using ldapsearch to check that producer slapd is running... Using ldapmodify to modify producer directory... Waiting 15 seconds for syncrepl to receive changes... Stopping consumer to test recovery... Modifying more entries on the producer... Restarting consumer... Waiting 25 seconds for syncrepl to receive changes... Try updating the consumer slapd... Waiting 15 seconds for syncrepl to receive changes... Using ldapsearch to read all the entries from the producer... Using ldapsearch to read all the entries from the consumer... Filtering producer results... Filtering consumer results... Comparing retrieved entries from producer and consumer... test failed - producer and consumer databases differ

1 0

Re: (ITS#5051) Translucent overlay and back-monitor
by ghenry＠suretecsystems.com 11 Aug '07

11 Aug '07

<quote who="Pierangelo Masarati"> > Gavin Henry wrote: > >> OK, thanks. Do you have any reference for custom monitoring examples? > > Not sure what you mean. By "custom monitoring" I mean that pieces of > code may register callbacks in back-monitor to enrich the monitor > entries with dynamically generated data. Right now, the only code that > exploits this functionality is back-bdb/back-hdb, but it's something we > use intensively for custom modules we develop (the monitor database can > be proficiently used as an interface for non-persistent interaction with > the DSA). Ah, right. Sorry, I misunderstood custom as something done via configuration in the front end, not via callbacks. > > With reference to code, see servers/slapd/back-bdb/monitor.c (the API is > implemented in servers/slapd-back-monitor/init.c). Will do, sounds very useful indeed. > > What back-bdb/hdb publishes by means of this API is not documented, > AFAIK; it might be worth mentioning somewhere in the docs, as this > monitoring could be quite useful for tuning. Nothing that cannot be > accessed thru db_stat, the advantage is access via LDAP protocol. Exactly, sounds very useful and one that I can investigate and document in the Monitoring section, with implementation examples (not code) in the Tuning and Maintenance sections of our guide. > > A recent addition was the capability to monitor what unindexed > attributes were used in searches. Yeah, I commented on that previously. Nice. Gavin. > > 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#5051) Translucent overlay and back-monitor
by ando＠sys-net.it 11 Aug '07

11 Aug '07

Gavin Henry wrote: > OK, thanks. Do you have any reference for custom monitoring examples? Not sure what you mean. By "custom monitoring" I mean that pieces of code may register callbacks in back-monitor to enrich the monitor entries with dynamically generated data. Right now, the only code that exploits this functionality is back-bdb/back-hdb, but it's something we use intensively for custom modules we develop (the monitor database can be proficiently used as an interface for non-persistent interaction with the DSA). With reference to code, see servers/slapd/back-bdb/monitor.c (the API is implemented in servers/slapd-back-monitor/init.c). What back-bdb/hdb publishes by means of this API is not documented, AFAIK; it might be worth mentioning somewhere in the docs, as this monitoring could be quite useful for tuning. Nothing that cannot be accessed thru db_stat, the advantage is access via LDAP protocol. A recent addition was the capability to monitor what unindexed attributes were used in searches. 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#5051) Translucent overlay and back-monitor
by ghenry＠suretecsystems.com 11 Aug '07

11 Aug '07

<quote who="ando(a)sys-net.it"> > ghenry(a)suretecsystems.com wrote: > >> Ok. What can the rootdn do on the monitor database then? Write to >> anything? >> I can update the "Monitoring" section with this info then ;-) > > As usual, the privilege of the rootdn consists in bypassing ACLs. In > this case, you just need the rootdn, it doesn't need to be able to bind > (i.e. no rootpw and no fancy SASL rules to map someone with that > identity), since it will only be used for internal purposes, namely to > look up where bdb custom monitoring will be placed. OK, thanks. Do you have any reference for custom monitoring examples? Gavin. > > 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#4211
by ando＠sys-net.it 11 Aug '07

11 Aug '07

Quanah, for which is which, HEAD now has back-config support for both slapo-rwm and slapd-relay. You may resume your configuration replication experiments... 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#5051) Translucent overlay and back-monitor
by ando＠sys-net.it 11 Aug '07

11 Aug '07

ghenry(a)suretecsystems.com wrote: > Ok. What can the rootdn do on the monitor database then? Write to anything? > I can update the "Monitoring" section with this info then ;-) As usual, the privilege of the rootdn consists in bypassing ACLs. In this case, you just need the rootdn, it doesn't need to be able to bind (i.e. no rootpw and no fancy SASL rules to map someone with that identity), since it will only be used for internal purposes, namely to look up where bdb custom monitoring will be placed. 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#5088) ObjectClass inheritance check in back-sql
by ando＠sys-net.it 11 Aug '07

11 Aug '07

Full_Name: Pierangelo Masarati Version: HEAD/re23 OS: irrelevant URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (82.63.140.131) Submitted by: ando When extra objectClasses for an entry are listed in table ldap_entry_objclasses, if any of them is structural and derived from the objectClass used to map the RDBMS data to LDAP, the entry is now rejected because the computed objectClass does not match the objectClass used to map data, although the entry would be perfectly valid from an LDAP standpoint. This is now fixed in HEAD/re23. p.

1 0

(ITS#5087) slapacl is broken for back-hdb
by hyc＠OpenLDAP.org 10 Aug '07

10 Aug '07

Full_Name: Howard Chu Version: 2.3/HEAD OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (76.168.84.21) Submitted by: hyc The tool_id2entry_get function neglects the fix_dn step for hdb, so every retrieved entry has a zero-length DN. A patch to HEAD is coming. Really there should never have been such a function, tool_entry_get should have been used for this purpose.

1 0

Re: (ITS#5077) syncrepl.add_cmp() infinite loop on swapped values
by donn＠u.washington.edu 10 Aug '07

10 Aug '07

On Aug 10, 2007, at 2:16 PM, Howard Chu wrote: > donn(a)u.washington.edu wrote: >> Full_Name: Donn Cave >> Version: 2.4.4 >> OS: Red Hat Linux >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (128.95.135.150) >> In "while" loop at 2656, I find old->a_vals are like [..., a, >> b, ...] and >> new->a_vals are like [..., b, a, ...]. >> Matches are found at old [i] == new [k = j+1] and old [k = i+1] == >> new [j], but >> this just shows that neither an add nor a delete is called for, >> and the loop end >> is reached without having incremented i or j. >> Actual attribute values I'm looking at right now in the debugger are >> eduPersonAffiliation: old [ member, alum, employee, faculty ], >> new [ member, >> alum, faculty, employee ]. I built the replica from a slapcat >> dump on the idle >> master, started the slapd syncrepl client and applied a lot of normal >> modifications to the master, until it hit the infinite loop. It >> has been a >> recurrent problem. > > Now fixed in HEAD, please test. Aug 10 15:06:55 rufus03 slapd[31488]: null_callback : error code 0x14 Aug 10 15:06:55 rufus03 slapd[31488]: syncrepl_entry: rid=101 be_modify (20) Aug 10 15:06:55 rufus03 slapd[31488]: syncrepl_entry: rid=101 be_modify failed (20) I could put some more research into this, but tell me if this doesn't make sense. Suppose this mysteriously swapped order: a,b,... b,a,... Your fix increments the first list's index, so next iteration it's b,... b,a,... which is fine, but next iteration is ... a,... "a" looks new at this point, and I try to add it, but it isn't new - we just forgot that it was in "old" - and I get error 0x14 (LDAP_TYPE_OR_VALUES_EXISTS) Donn Cave, donn(a)u.washington.edu

1 0

Re: (ITS#5065) out of order ctxcsn from old entryCSN
by hyc＠symas.com 10 Aug '07

10 Aug '07

donn(a)u.washington.edu wrote: > On Aug 10, 2007, at 1:53 PM, Howard Chu wrote: >> You didn't mention how your syncrepl is configured but it seems >> that this can only occur for refreshAndPersist mode, with old >> entries being ldapadd'd to the running master. > > It is indeed refreshAndPersist ... > >> In fact, since entryCSN is NO-USER-MODIFICATION it shouldn't even >> be possible to add entries this way to a running server. Before we >> can "catch the problem in the master" we need more information on >> how the problem was caused. > > The master server had updatedn defined to itself. Changes, logged from > another server, were applied with ldapmodify. "Don't do this" ... You're essentially creating the same inconsistency that a naive multimaster setup introduces. Since 2.4.4 has real multimaster support, you should not be doing things this way. Note that a proper configuration works with either refreshOnly or refreshAndPersist mode, and cascaded to an arbitrary depth. Your current setup only works with refreshAndPersist, and cannot be cascaded reliably. I.e. your setup is inherently broken. -- -- 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#5077) syncrepl.add_cmp() infinite loop on swapped values
by hyc＠symas.com 10 Aug '07

10 Aug '07

donn(a)u.washington.edu wrote: > Full_Name: Donn Cave > Version: 2.4.4 > OS: Red Hat Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (128.95.135.150) > > > In "while" loop at 2656, I find old->a_vals are like [..., a, b, ...] and > new->a_vals are like [..., b, a, ...]. > > Matches are found at old [i] == new [k = j+1] and old [k = i+1] == new [j], but > this just shows that neither an add nor a delete is called for, and the loop end > is reached without having incremented i or j. > > Actual attribute values I'm looking at right now in the debugger are > eduPersonAffiliation: old [ member, alum, employee, faculty ], new [ member, > alum, faculty, employee ]. I built the replica from a slapcat dump on the idle > master, started the slapd syncrepl client and applied a lot of normal > modifications to the master, until it hit the infinite loop. It has been a > recurrent problem. Now fixed in HEAD, please test. -- -- 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#5065) out of order ctxcsn from old entryCSN
by donn＠u.washington.edu 10 Aug '07

10 Aug '07

On Aug 10, 2007, at 1:53 PM, Howard Chu wrote: > > You didn't mention how your syncrepl is configured but it seems > that this can only occur for refreshAndPersist mode, with old > entries being ldapadd'd to the running master. It is indeed refreshAndPersist ... > > In fact, since entryCSN is NO-USER-MODIFICATION it shouldn't even > be possible to add entries this way to a running server. Before we > can "catch the problem in the master" we need more information on > how the problem was caused. The master server had updatedn defined to itself. Changes, logged from another server, were applied with ldapmodify. Donn Cave, donn(a)u.washington.edu

1 0

Re: (ITS#5065) out of order ctxcsn from old entryCSN
by hyc＠symas.com 10 Aug '07

10 Aug '07

donn(a)u.washington.edu wrote: > Full_Name: Donn Cave > Version: 2.4.4 > OS: RH Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (128.95.135.150) > > > Old entryCSN values imported into the data from another server, can crash > replicas. > > In loop at top of syncrepl_updateCookie, replica encounters a syncCookie whose > value is less than its matching si_cookieState->cs_val. This breaks out of the > inner loop, and the outer loop, without copying anything into `first', so > slap_queue_csn crashes on the null csn. Both are element 0 of their respective > arrays. I assume it is no surprise that syncCookie takes its value from an > entryCSN attribute. > > To duplicate, add an entry with an explicit entryCSN, with value less than the > current contextCSN. In my case, the entryCSN is of the format without the > `decimal fraction' field, but I doubt that matters. > > I don't want to say OpenLDAP needs to support this, but maybe it would be better > to catch the problem in the master, than crash the replicas. You didn't mention how your syncrepl is configured but it seems that this can only occur for refreshAndPersist mode, with old entries being ldapadd'd to the running master. As you say, this is not a supported mode of operation. New data in the server should always have a new entryCSN as well. In fact, since entryCSN is NO-USER-MODIFICATION it shouldn't even be possible to add entries this way to a running server. Before we can "catch the problem in the master" we need more information on how the problem was caused. As for crashing the replicas - the only sure solution is to patch the code in the replicas - "catching the problem in the master" isn't really a proper solution anyway. -- -- 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#5082
by hyc＠symas.com 10 Aug '07

10 Aug '07

ando(a)sys-net.it wrote: > See also discussion in thread > <http://www.openldap.org/lists/openldap-software/200708/msg00063.html> The fix currently in CVS HEAD is to remove the olcPasswordHash attribute from the olcGlobal entry and move it to the frontendDB entry. -- -- 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#5085) slapo-translucent has wrong Debug message
by ghenry＠OpenLDAP.org 10 Aug '07

10 Aug '07

ghenry(a)OpenLDAP.org wrote: > Full_Name: Gavin Henry > Version: HEAD > OS: > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (212.159.59.85) > Submitted by: ghenry > > > Inside: > > translucent_db_destroy > > Debug: > > Debug(LDAP_DEBUG_TRACE, "==> translucent_db_close\n", 0, 0, 0); > > Should be: > > Debug(LDAP_DEBUG_TRACE, "==> translucent_db_destroy\n", 0, 0, 0); > > Probably copy and paste error. > > Correcting. > > Gavin. > > This is missing from RE_23, but obviously not going to be added. There is another error in RE_23 though: Debug(LDAP_DEBUG_TRACE, "==> translucent_init\n", 0, 0, 0); should be translucent_db_init. Will change under this ITS. Gavin. -- Kind Regards, Gavin Henry. OpenLDAP Engineering Team. E ghenry(a)OpenLDAP.org Community developed LDAP software. http://www.openldap.org/project/

1 0

(ITS#5086) back-bdb bug when add is used with snapshot isolation
by stelios.xx.grigoriadis＠ericsson.com 10 Aug '07

10 Aug '07

Full_Name: Stelios Grigoriadis Version: 2.3.32 OS: Linux, (SLES 10) URL: http://ninikos.freehostia.com/bdb_idl_cache_bug.tar.gz Submission from: (NULL) (194.237.142.7) When using slapd with the snapshot isolation level in DB (version 4.5.20) it is possible that added entries don't appear in subsequent searches. Scenario: A client is adding new information while at the same time another is initiating an LDAP search with the same searchbase as the "parent" of the added information. If the search is executed after the add operation has cleared the IDL-cache but before the changes has been committed, the added entries will not appear in any subsequent searches unless slapd is restarted. The problem is that, in the bdb_idl_insert_key-function, the key is deleted from the IDL-cache but the newly added keys in the database are not yet committed, so clients that re-read the information will not have those updated keys. The solution would be to clear the relevant IDL-cache entries after the changes has been committed. This behaviour is demonstrated by the program cache_test_fork.c which is supplied in bdb_idl_cache_bug.tar.gz along with the slapd configuration. I am currently working on the solution but would greatly appreciate any help from you as I am not nearly as familiar with the code as you are.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs