openldap-bugs

openldap-bugs@openldap.org

1 participants
20964 discussions

Re: (ITS#5640) slapd scans too many objects at startup
by ali.pouya＠free.fr 02 Nov '08

02 Nov '08

Howard Chu a écrit : > > The startup scan is only performed inside the syncprov overlay. If > server C is only a consumer, then it does not need the syncprov overlay. > Yes, you are right for the point 1). Thank you. But I'm also bothered with the point 2) reproduced below : .... 2) If I do only one write operation on B, then I get two contextCSN values, which is normal. But il this case slapd on B scans, at each startup, all objecs written on A after the write operation on B. The log and the effect are similar to those explained above. Best Regards Ali

1 0

Re: (ITS#5640) slapd scans too many objects at startup
by hyc＠symas.com 02 Nov '08

02 Nov '08

ali.pouya(a)free.fr wrote: > Full_Name: Ali Pouya > Version: 2.4.11 > OS: Linux 2.6 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (145.242.11.4) > > > I have a test directory with two mirrors A and B and a replica C connected to > A. > I usaually use server A for write operations. > > I encounter the following problems : > > > 1) If the data base is initiated in stand alone (so serverID defaults to zero) > and then I set serverIDs 1 and 2 for A and B then each time I start up slapd on > C it scans all of the objects writtent on A afterwards, producing the followin > log for each object : The startup scan is only performed inside the syncprov overlay. If server C is only a consumer, then it does not need the syncprov overlay. -- -- 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: (ITS#5709) slapd sync provider skips some objects
by hyc＠symas.com 02 Nov '08

02 Nov '08

hyc(a)symas.com wrote: > sylvain.thomas(a)gmail.com wrote: >> On 10/30/08, Gavin Henry<ghenry(a)openldap.org> wrote: >>> Can you upload these zip attachments to our ftp server or somewhere else >>> with online >>> access please. Then we can test. >>> >> I have uploaded the two files to your ftp server (incoming folder). > > I can confirm that the problem is easily reproducable. Fixed now in HEAD. A couple of bad assumptions from 1.234-1.236... -- -- 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: (ITS#5785) dontUseCopy in slapd requires criticality to be TRUE
by michael＠stroeder.com 01 Nov '08

01 Nov '08

ando(a)sys-net.it wrote: > > The "dontUseCopy" control requires criticality to be TRUE. While this is the > desirable value, Why is this a desirable value? The answer Kurt gave on ldap-ext mailing list just mentioned direct mapping to X.511 dontUseCopy option. > a DUA could use the control with the criticality set to FALSE. As I stated on ldap-ext mailing list in this case I'd simply accept a best effort on the DSA side. So sending "dontUseCopy" control with criticality FALSE would mean: If the DSA supports this control it should *process* it according to what's specified in draft-zeilenga-ldap-dontusecopy. Otherwise ignore it. The main problem is that a DUA cannot determine in advance whether a DSA supports a certain control for a certain backend. It turned out in practice that looking a supportedControl in rootDSE does not have any meaning at all. IMO yet another control does not solve this. > For full conformance with RFC4511, if the control is syntactically well-formed > and criticality is set to FALSE, slapd MUST accept it if recognized, or MUST > ignore it if not recognized, but CANNOT question the fact that the value of > criticality is violating the control's specification. I'm not sure whether this statement can be made generally. I'd wish so and I'd rephrase "accept it" to "process it". Ciao, Michael.

1 0

(ITS#5785) dontUseCopy in slapd requires criticality to be TRUE
by ando＠sys-net.it 01 Nov '08

01 Nov '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 "dontUseCopy" control requires criticality to be TRUE. While this is the desirable value, a DUA could use the control with the criticality set to FALSE. For full conformance with RFC4511, if the control is syntactically well-formed and criticality is set to FALSE, slapd MUST accept it if recognized, or MUST ignore it if not recognized, but CANNOT question the fact that the value of criticality is violating the control's specification. p. PS: other controls with similar requirements for the DUA accept any value for criticality (e.g. RFC4370).

1 0

(ITS#5784) [enhancement] add support for "What Failed?" LDAP control
by ando＠sys-net.it 01 Nov '08

01 Nov '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 I'm about to add support for what I termed the "What Failed?" LDAP control, which allows to request detailed information about what extension caused the failure of a request. The commit includes a preliminary version of what I intend to submit as an I.D. shortly. p.

1 0

Re: (ITS#5709) slapd sync provider skips some objects
by hyc＠symas.com 31 Oct '08

31 Oct '08

sylvain.thomas(a)gmail.com wrote: > On 10/30/08, Gavin Henry<ghenry(a)openldap.org> wrote: >> Can you upload these zip attachments to our ftp server or somewhere else >> with online >> access please. Then we can test. >> > > I have uploaded the two files to your ftp server (incoming folder). I can confirm that the problem is easily reproducable. Adding a debug message here diff -u -r1.248 syncprov.c --- syncprov.c 17 Oct 2008 15:40:49 -0000 1.248 +++ syncprov.c 31 Oct 2008 21:06:56 -0000 @@ -1638,6 +1638,7 @@ si->si_sids[i] = sid; } } else { + Debug( LDAP_DEBUG_SYNC, "Empty maxcsn for %s\n", op->o_req_dn.bv_val, 0, 0 ); /* internal ops that aren't meant to be replicated */ ldap_pvt_thread_rdwr_wunlock( &si->si_csn_rwlock ); return SLAP_CB_CONTINUE; shows that some of the missing entries are caused by this situation, but not necessarily all. Still investigating. -- -- 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: (ITS#5781) syncrepl doing delete/add on items without equality
by rubin＠physics.umn.edu 31 Oct '08

31 Oct '08

Patched in servers/slapd/syncrepl.c rev 1.418 http://www.openldap.org/devel/cvsweb.cgi/servers/slapd/syncrepl.c.diff?r1=1… I applied the patch to 2.4.11 and verified it does solve the problem. Thanks!

1 0

Re: (ITS#5709) slapd sync provider skips some objects
by sylvain.thomas＠gmail.com 31 Oct '08

31 Oct '08

On 10/30/08, Gavin Henry <ghenry(a)openldap.org> wrote: > Can you upload these zip attachments to our ftp server or somewhere else > with online > access please. Then we can test. > >> I have uploaded the two files to your ftp server (incoming folder). Best regards Sylvain Thomas

1 0

(ITS#5783) Possible DB corruption
by moya＠latertulia.org 31 Oct '08

31 Oct '08

Full_Name: Maykel Moya Version: 2.4.11 OS: Debian Lenny URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (200.55.135.211) It's second time that I have bitten by this: Oct 31 07:49:24 swage slapd[4308]: PROXIED attributeDescription "DC" inserted. After that I'm unable to bind against the DSA. The problem has arise in two independent systems. Steps to reproduce: 1. Create a minor db (like Debian does), a dc=foo,dc=org node and a cn=admin,rootdn node 2. Migrate to cn=config 3. Edit cn=config I've added olcTLSCACertificateFile / olcTLSCertificateFile / olcTLSCertificateKeyFiel attributes 4. Restart the server After restarting I see the PROXIED error. I'd wrote to the list before [1][2] but the same thing has come in another system. Regards, maykel [1] http://www.openldap.org/lists/openldap-software/200808/msg00170.html [2] http://www.openldap.org/lists/openldap-software/200808/msg00170.html

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