- openldap-bugs - openldap.org

Re: (ITS#6239) ldap_pvt_tls_check_hostname() may be vulnerable
by hyc＠symas.com 30 Jul '09

30 Jul '09

hyc(a)OpenLDAP.org wrote: > Full_Name: Howard Chu > Version: any > OS: > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (76.91.220.157) > Submitted by: hyc > > > Our chkhost implementation for OpenSSL does a simple strcasecmp on the name > obtained from the certificate CN; if the CN has an embedded NUL it is possible > for this check to be spoofed. This is now fixed in HEAD. > > Our chkhost implementation for GnuTLS is not vulnerable. > > We didn't write a chkhost implementation for MozNSS, we just use the default one > they provide. Inspecting their code shows that their default checker is also > vulnerable. I will be writing a replacement for libldap shortly. All fixed in HEAD/RE24. Surprisingly, the GnuTLS API got this one right. So did OpenSSL (we just botched our use of their APIs). But the MozNSS APIs all discard the length info of the data instead of returning it, so we had to reimplement some of their basic name-handling code in libldap. Probably should have just done all of this using DER and liblber too, like the other cert parsing code. -- -- 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

(ITS#6239) ldap_pvt_tls_check_hostname() may be vulnerable
by hyc＠OpenLDAP.org 30 Jul '09

30 Jul '09

Full_Name: Howard Chu Version: any OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (76.91.220.157) Submitted by: hyc Our chkhost implementation for OpenSSL does a simple strcasecmp on the name obtained from the certificate CN; if the CN has an embedded NUL it is possible for this check to be spoofed. This is now fixed in HEAD. Our chkhost implementation for GnuTLS is not vulnerable. We didn't write a chkhost implementation for MozNSS, we just use the default one they provide. Inspecting their code shows that their default checker is also vulnerable. I will be writing a replacement for libldap shortly.

1 0

Re: (ITS#6238) contrib: lastbind overlay to record timestamp of last successful bind
by michael＠stroeder.com 30 Jul '09

30 Jul '09

jonathan(a)phillipoux.net wrote: > Full_Name: Jonathan Clarke > Version: RE24 > OS: > URL: ftp://ftp.openldap.org/incoming/jonathan-clarke-lastbind-20090730.tgz > Submission from: (NULL) (82.67.204.30) > > Please find, at the above URL, an overlay, built for OpenLDAP 2.4, that > intercepts successful binds and records the current timestamp in an attribute > named "bindTimestamp" in the bound-to entry. It's original use-case is to detect > unused accounts. Detecting unused accounts can also somewhat achieved by using slapo-accesslog with configuration directive "logops session". Still I see some value for such an simple overlay. > A configuration parameter (olcLastBindPrecision) allows to set a minimum > precision for the timestamp (ie, don't update the timestamp unless it's older > than <n> seconds). This avoids a performance hit from many unnecessary writes in > case there are many binds per minute/hour/day/week/etc. Things to consider: Is this attribute supposed to be replicated? How about adding configuration paramters so you can specify 1. the attribute type used and 2. the datetime format. This could be handy in situations where you want to mimique the behaviour of other LDAP servers. Ciao, Michael.

1 0

(ITS#6238) contrib: lastbind overlay to record timestamp of last successful bind
by jonathan＠phillipoux.net 30 Jul '09

30 Jul '09

Full_Name: Jonathan Clarke Version: RE24 OS: URL: ftp://ftp.openldap.org/incoming/jonathan-clarke-lastbind-20090730.tgz Submission from: (NULL) (82.67.204.30) Hi, Please find, at the above URL, an overlay, built for OpenLDAP 2.4, that intercepts successful binds and records the current timestamp in an attribute named "bindTimestamp" in the bound-to entry. It's original use-case is to detect unused accounts. A configuration parameter (olcLastBindPrecision) allows to set a minimum precision for the timestamp (ie, don't update the timestamp unless it's older than <n> seconds). This avoids a performance hit from many unnecessary writes in case there are many binds per minute/hour/day/week/etc. Of course, the behaviour this overlay implements is not described in any RFC, or other. However, it closely resembles some of the functionality from the password policy overlay, and similar functionality already exists in other LDAP servers. I post it here in the hope that it may serve others, and in case the OpenLDAP wishes to include it in one form or another. I would most appreciate any comments or feedback. Regards, Jonathan PS: please note that the OIDs used are not registered, but used temporarily. I do not currently have access to a registered OID to use.

1 0

Re: (ITS#6234) CONFIGURABLE TCP BUFFERS IN SLAPD FEATURE REQUEST
by masarati＠aero.polimi.it 30 Jul '09

30 Jul '09

evaristojosec(a)yahoo.es wrote: > Full_Name: Evaristo Camarero > Version: 2.4.x > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (194.237.142.20) > > > > Hi, > > Working with slapd under heavy load it could be interesting to have TCP buffers > size configurable at slapd application level instead of getting default OS > values. > > Some fast modifications in daemon.c file to achieve a hardcoded value for the > sender buffer are: > > int buf_size = 1572864; /* 1.5 Mb */ > rc =setsockopt ( s, SOL_SOCKET, SO_SNDBUF, (int*)&buf_size, > sizeof(buf_size)); > if(rc==-1) { > Debug( LDAP_DEBUG_ANY, "slapd(%ld): " > "setsockopt(SO_SNDBUF) failed errno=%d (%s)\n", > (long) l.sl_sd, err, sock_errstr(err) ); > } else { > Debug( LDAP_DEBUG_ANY, "slapd(%ld): setsockopt(SO_SNDBUF) to %d\n", > (long) l.sl_sd, buf_size, 0); > } Since you use Linux, you could try the kernel's tcp autotuning capabilities described in tcp(7) (other informative links are <http://fasterdata.es.net/TCP-tuning/linux.html>, <http://www.kernelfaq.com/2007/11/tcp-auto-tuning.html>). Of course, the possibility to manually enforce the size of the buffer may be useful in some cases, so a specific configuration option may deserve consideration. p.

1 0

Re: (ITS#6235) Installing openLDAP on Solaris 10 (Berkeley DB issue)
by mkassawara＠gmail.com 29 Jul '09

29 Jul '09

The configure script can't find the BDB headers/libraries in the typical places. Either install them to a typical place seen by the preprocessor/linker (e.g., /usr/include, /usr/lib, /usr/local/ include, /usr/local/lib ...) or set the CPPFLAGS and LDFLAGS environment variables appropriately before running the configure script. If you plan to install OpenLDAP to a custom location, consider using "crle" to add the necessary library path(s) to the runtime linking environment. Also, to prevent another issue down the road, make sure you apply the Oracle patches to BDB 4.7.25 before building it. This is not an ITS... you should use openldap-technical for future correspondence on this issue. On Jul 29, 2009, at 3:09 PM, mark.liu(a)nyu.edu wrote: > Full_Name: Mark Liu > Version: 2.4.16 > OS: Sun Solaris 10 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (128.122.149.115) > > > I am trying to install openLDAP on Solaris 10. Whenever I tried to > configure > openLDAP, it would give the following message: > > checking db.h usability... no > checking db.h presence... no > checking for db.h... no > configure: error: BDB/HDB: BerkeleyDB not available > > The install would stop there. I thought it might be require a > different version > of BerkeleyDB, I downloaded both BerkeleyDB 4.7.25 and 4.6.21. > OpenLDAP > produced the same result for both instances of BerkeleyDB. > > What do i need to do to get pass this? Thanks! >

1 0

(ITS#6235) Installing openLDAP on Solaris 10 (Berkeley DB issue)
by mark.liu＠nyu.edu 29 Jul '09

29 Jul '09

Full_Name: Mark Liu Version: 2.4.16 OS: Sun Solaris 10 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (128.122.149.115) I am trying to install openLDAP on Solaris 10. Whenever I tried to configure openLDAP, it would give the following message: checking db.h usability... no checking db.h presence... no checking for db.h... no configure: error: BDB/HDB: BerkeleyDB not available The install would stop there. I thought it might be require a different version of BerkeleyDB, I downloaded both BerkeleyDB 4.7.25 and 4.6.21. OpenLDAP produced the same result for both instances of BerkeleyDB. What do i need to do to get pass this? Thanks!

1 0

Re: (ITS#6225) GSSAPI support for client library (fixes)
by mikbec＠web.de 29 Jul '09

29 Jul '09

hyc(a)symas.com wrote: > mimir(a)samba.org wrote: >> Full_Name: Rafal Szczesniak >> Version: Stable (2.4.16) >> OS: GNU/Linux >> URL: http://www.samba.org/~mimir/gssapi-bugfix.diff >> Submission from: (NULL) (67.51.54.234) >> >> >> This is a bugfix patch for OpenLDAP's gssapi support. >> > One of these patches appears to duplicate ITS#6092. As the original author of > this code, could you also take a look at #6091 and #6093? > Yes, I think this patch tries to resolve the same problem like #6093 but with a different approach. And after some discussion with Hallvard B Furuseth about the guess_service_principal() string problem (#6223) I have sent a all-in-one-patch which results in #6110. best regards mike

1 0

Re: (ITS#6215) liblber problems
by h.b.furuseth＠usit.uio.no 29 Jul '09

29 Jul '09

Fixing this, and some other problems: - decode.c incorrectly treats length octet 0x80 (indefinite-length) as long length = 0. Fixing to returning an error. - Overly complex and inefficient code, in particular encode.c. Rewriting. Removing struct seqorset and related allocations. - Missing overflow/max-size checks. - ber_scanf() *must* clean up properly on error, as the code notes. Currently it can crash when reading malformed elements. Both encode.c and decode.c mostly access the Ber data "properly" via ber_write()/ber_read() but sometimes accesses the buffer directly. Can clean up and speed up at the same time by collecting that in fewer places. Side effects: - Dropping ber_write(,,,nonzero) support. Any callers likey need to use BerElement.ber_sos_ptr/ber_sos_inner, the struct seqorset replacement. - Dropping ber_log_sos_dump() and ber_sos_dump(), leaving behind stubs. They'd need a new ber parameter to work. Other matters - questions: - decode.c is quite lax about what it accepts. Should we tighten that when feasible, or remain "liberal in what we accept"? E.g. it accepts BER INTEGER length 0 and BOOLEAN length != 1, and wrong CONSTRUCTED/PRIMITIVE encoding bit. - encode.c willingly stores broken identifier octets if passed an invalid tag, e.g. a single octet with low bits 0x1F implying long tag format. I'm inclined to leave that alone, caller's responsibility. -- Hallvard

1 0

Re: (ITS#6232) OpenLDAP 2.4.17 fails to compile with --with-tls=gnutls
by steffen＠hauihau.de 29 Jul '09

29 Jul '09

Dear Howard, please have a look at http://bugs.gentoo.org/show_bug.cgi?id=233633 . The provided patch in the Debian bug tracker does not fix the compiling issue of passwd.c as the defines and typedefs are inserted *after* the first occurrence of "des_key". I've modified this patch, and it's already included in gentoo's ebuild for OpenLDAP 2.4.17. I don't know if I'm authorized to contribute it to the ITS, as I've only modified the original patch. I would do it of course, if 'm allowed to, since there is no employer, who would prevent me to do it, as I'm doing it in my freetime.

1 0

(ITS#6234) CONFIGURABLE TCP BUFFERS IN SLAPD FEATURE REQUEST
by evaristojosec＠yahoo.es 29 Jul '09

29 Jul '09

Full_Name: Evaristo Camarero Version: 2.4.x OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (194.237.142.20) Hi, Working with slapd under heavy load it could be interesting to have TCP buffers size configurable at slapd application level instead of getting default OS values. Some fast modifications in daemon.c file to achieve a hardcoded value for the sender buffer are: int buf_size = 1572864; /* 1.5 Mb */ rc =setsockopt ( s, SOL_SOCKET, SO_SNDBUF, (int*)&buf_size, sizeof(buf_size)); if(rc==-1) { Debug( LDAP_DEBUG_ANY, "slapd(%ld): " "setsockopt(SO_SNDBUF) failed errno=%d (%s)\n", (long) l.sl_sd, err, sock_errstr(err) ); } else { Debug( LDAP_DEBUG_ANY, "slapd(%ld): setsockopt(SO_SNDBUF) to %d\n", (long) l.sl_sd, buf_size, 0); } Regards, Evaristo

1 0

Re: (ITS#5942) URI matching of "self" in add_syncrepl is incomplete
by hyc＠symas.com 29 Jul '09

29 Jul '09

jclarke(a)linagora.com wrote: > On 14.02.2009 01:51, Howard Chu wrote: >> Jonathan Clarke wrote: >>> On 13.02.2009 01:23, Howard Chu wrote: >>>> There are valid reasons to point a syncrepl consumer at the same slapd >>>> (e.g., proxy syncrepl, automatic local backup/mirroring, rewriting a >>>> subtree of a main database, etc.). Using the exhaustive matching that >>>> serverID uses would preclude those cases from working. >>> I see. I understand you don't want to break existing functionality. >>> However, I still feel this is a bug, or at least that you need to "hack" >>> the setup to get things working as expected. >> >> The docs state that "syncrepl provider" is the LDAP URI of the master >> server. If you're not putting in the same URI as the master is using, >> that's a config error, not a bug. > > Understood. Nothing is broken, and we have worked around this issue > using explicit listeners to slapd -h. > > This behaviour did surprise me, considering the behaviour of serverID > matching. May I suggest that a note of warning is included in the admin > guide? For example: > http://milopita.phillipoux.net/jonathan-clarke-20090216.patch > >>> Would I be right in assuming that in all the "valid reasons to point a >>> syncrepl consumer at the same slapd" you mention, the syncrepl consumer >>> uses a different base DN than the base DN of the database that the >>> syncrepl consumer is configured on? If so, maybe the exhaustive matching >>> that serverID uses could be used, if and only if those two base DNs are >>> different? Actually, the exhaustive matching is only needed if the two base DNs are the same. This is now patched in HEAD, please test. >> That sounds reasonable. Will think about it a bit more. Certainly if the >> two base DNs are the same, it will cause a loop... > > Indeed. For what it's worth, while testing on cn=config, I noticed this > having various consequences including: > 1) cn=config becoming read-only (shadow) and updates returning a referral. > 2) in a MMR setup, some updates not being replicated to all N servers. -- -- 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#6233) print_deref assertion if no deref attributes returned
by hyc＠symas.com 28 Jul '09

28 Jul '09

rmeggins(a)redhat.com wrote: > Full_Name: Rich Megginson > Version: 2.4.17+ (current HEAD) > OS: Fedora > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (76.113.59.19) > > > I am testing the LDAP Dereference feature specified here - > http://www.openldap.org/devel/cvsweb.cgi/~checkout~/doc/drafts/draft-masara… > > I am getting an assertion in common.c at line 2077: > 2074: ptr = lutil_strncopy( ptr, dr->derefVal.bv_val, dr->derefVal.bv_len ); > 2075: *ptr++ = '\n'; > 2076: *ptr++ = '\0'; > 2077: assert( ptr<= buf + len ); > > tool_write_ldif( LDIF_PUT_COMMENT, NULL, buf, ptr - buf); > > In my test, ptr is one greater than buf + len. It appears that len does not > take into consideration the addition of the trailing \0 at line 2076. My test > is looking for a dereference attribute which does not have any values, so that > the attrVals in the control response is empty. If there are values to return in > attrVals, the assertion is not triggered. > Ah the ever-popular off-by-one. Should be OK now in HEAD, thanks for the report. -- -- 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#6232) OpenLDAP 2.4.17 fails to compile with --with-tls=gnutls
by hyc＠symas.com 28 Jul '09

28 Jul '09

steffen.hau(a)rz.uni-mannheim.de wrote: > Full_Name: Steffen Hau > Version: 2.4.17 > OS: gentoo > URL: > Submission from: (NULL) (134.155.35.13) > > > Gentoo prefers gnutls usage over openssl when compiling openldap. But if > with-tls=gnutls and enable-lmpasswd set, neither HAVE_OPENSSL nor NAVE_MOZNSS is > defined and passwd.c failes to compile with: See ITS #4997. There is a patch for this in the debian bug tracker, but until someone with appropriate authorization (i.e., the patch author) contributes it to the ITS with the requisite Rights statements attached, we cannot incorporate it. > passwd.c:813: error: expected declaration specifiers or ... before des_key > passwd.c: In function lmPasswd_to_key: > passwd.c:828: error: key undeclared (first use in this function) > passwd.c:828: error: (Each undeclared identifier is reported only once > passwd.c:828: error: for each function it appears in.) > passwd.c: In function chk_lanman: > passwd.c:839: error: des_key undeclared (first use in this function) > passwd.c:839: error: expected ; before key > passwd.c:840: error: des_context undeclared (first use in this function) > passwd.c:840: error: expected ; before schedule > passwd.c:841: error: des_data_block undeclared (first use in this function) > passwd.c:841: error: expected ; before StdText > passwd.c:842: error: expected ; before PasswordHash1 > passwd.c:859: error: key undeclared (first use in this function) > passwd.c:859: error: too many arguments to function lmPasswd_to_key > passwd.c:860: error: schedule undeclared (first use in this function) > passwd.c:861: error: StdText undeclared (first use in this function) > passwd.c:861: error: PasswordHash1 undeclared (first use in this function) > passwd.c:861: error: DES_ENCRYPT undeclared (first use in this function) > passwd.c:867: error: too many arguments to function lmPasswd_to_key > passwd.c:869: error: PasswordHash2 undeclared (first use in this function) > passwd.c: In function hash_lanman: > passwd.c:1135: error: des_key undeclared (first use in this function) > passwd.c:1135: error: expected ; before key > passwd.c:1136: error: des_context undeclared (first use in this function) > passwd.c:1136: error: expected ; before schedule > passwd.c:1137: error: des_data_block undeclared (first use in this function) > passwd.c:1137: error: expected ; before StdText > passwd.c:1138: error: expected ; before PasswordHash1 > passwd.c:1155: error: key undeclared (first use in this function) > passwd.c:1155: error: too many arguments to function lmPasswd_to_key > passwd.c:1156: error: schedule undeclared (first use in this function) > passwd.c:1157: error: StdText undeclared (first use in this function) > passwd.c:1157: error: PasswordHash1 undeclared (first use in this function) > passwd.c:1157: error: DES_ENCRYPT undeclared (first use in this function) > passwd.c:1159: error: too many arguments to function lmPasswd_to_key > passwd.c:1161: error: PasswordHash2 undeclared (first use in this function) > make[2]: *** [passwd.o] Error 1 > > I took a look in the passwd.c file, and because of neither HAVE_OPENSSL nor > HAVE_MOZNSS is defined, des_key isn't defined also. There is already a check in > the configure script, if tls is set when lmpasswd is set. The failure message > for it explains, that there has to be openssl installed in order to use lm > passwords. Perhaps this test has to be changed in a manner that it's checked, > what implementation is used for tls, and only activates lm passwords only, if > tls is either openssl or moznss. > > Please let me know if you need further information. > > Best regards, > Steffen Hau > -- -- 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

(ITS#6233) print_deref assertion if no deref attributes returned
by rmeggins＠redhat.com 28 Jul '09

28 Jul '09

Full_Name: Rich Megginson Version: 2.4.17+ (current HEAD) OS: Fedora URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (76.113.59.19) I am testing the LDAP Dereference feature specified here - http://www.openldap.org/devel/cvsweb.cgi/~checkout~/doc/drafts/draft-masara… I am getting an assertion in common.c at line 2077: 2074: ptr = lutil_strncopy( ptr, dr->derefVal.bv_val, dr->derefVal.bv_len ); 2075: *ptr++ = '\n'; 2076: *ptr++ = '\0'; 2077: assert( ptr <= buf + len ); tool_write_ldif( LDIF_PUT_COMMENT, NULL, buf, ptr - buf); In my test, ptr is one greater than buf + len. It appears that len does not take into consideration the addition of the trailing \0 at line 2076. My test is looking for a dereference attribute which does not have any values, so that the attrVals in the control response is empty. If there are values to return in attrVals, the assertion is not triggered.

1 0

(ITS#6232) OpenLDAP 2.4.17 fails to compile with --with-tls=gnutls
by steffen.hau＠rz.uni-mannheim.de 28 Jul '09

28 Jul '09

Full_Name: Steffen Hau Version: 2.4.17 OS: gentoo URL: Submission from: (NULL) (134.155.35.13) Gentoo prefers gnutls usage over openssl when compiling openldap. But if with-tls=gnutls and enable-lmpasswd set, neither HAVE_OPENSSL nor NAVE_MOZNSS is defined and passwd.c failes to compile with: passwd.c:813: error: expected declaration specifiers or ... before des_key passwd.c: In function lmPasswd_to_key: passwd.c:828: error: key undeclared (first use in this function) passwd.c:828: error: (Each undeclared identifier is reported only once passwd.c:828: error: for each function it appears in.) passwd.c: In function chk_lanman: passwd.c:839: error: des_key undeclared (first use in this function) passwd.c:839: error: expected ; before key passwd.c:840: error: des_context undeclared (first use in this function) passwd.c:840: error: expected ; before schedule passwd.c:841: error: des_data_block undeclared (first use in this function) passwd.c:841: error: expected ; before StdText passwd.c:842: error: expected ; before PasswordHash1 passwd.c:859: error: key undeclared (first use in this function) passwd.c:859: error: too many arguments to function lmPasswd_to_key passwd.c:860: error: schedule undeclared (first use in this function) passwd.c:861: error: StdText undeclared (first use in this function) passwd.c:861: error: PasswordHash1 undeclared (first use in this function) passwd.c:861: error: DES_ENCRYPT undeclared (first use in this function) passwd.c:867: error: too many arguments to function lmPasswd_to_key passwd.c:869: error: PasswordHash2 undeclared (first use in this function) passwd.c: In function hash_lanman: passwd.c:1135: error: des_key undeclared (first use in this function) passwd.c:1135: error: expected ; before key passwd.c:1136: error: des_context undeclared (first use in this function) passwd.c:1136: error: expected ; before schedule passwd.c:1137: error: des_data_block undeclared (first use in this function) passwd.c:1137: error: expected ; before StdText passwd.c:1138: error: expected ; before PasswordHash1 passwd.c:1155: error: key undeclared (first use in this function) passwd.c:1155: error: too many arguments to function lmPasswd_to_key passwd.c:1156: error: schedule undeclared (first use in this function) passwd.c:1157: error: StdText undeclared (first use in this function) passwd.c:1157: error: PasswordHash1 undeclared (first use in this function) passwd.c:1157: error: DES_ENCRYPT undeclared (first use in this function) passwd.c:1159: error: too many arguments to function lmPasswd_to_key passwd.c:1161: error: PasswordHash2 undeclared (first use in this function) make[2]: *** [passwd.o] Error 1 I took a look in the passwd.c file, and because of neither HAVE_OPENSSL nor HAVE_MOZNSS is defined, des_key isn't defined also. There is already a check in the configure script, if tls is set when lmpasswd is set. The failure message for it explains, that there has to be openssl installed in order to use lm passwords. Perhaps this test has to be changed in a manner that it's checked, what implementation is used for tls, and only activates lm passwords only, if tls is either openssl or moznss. Please let me know if you need further information. Best regards, Steffen Hau

1 0

(ITS#6231) The same problem: sasl realms don't work with digest-md5
by jackli7312＠yahoo.com.cn 27 Jul '09

27 Jul '09

Full_Name: jackli Version: 2.4.16 OS: fedora9 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (121.41.165.157) I searched this problem from mail list, and there is no response for it. I'm really suffering this for a week. Any help will be greatly appreciated! Please help. Jack hi all, i've got a problem with the sasl authentication using digest-md5 and multiple realms with my openldapServer 2.3.19 (fc5, yum). i want to be able to authenticate against different subtrees of the dit by using different realms and i was reading as many documentation, howtos and so on as i was able to find at the net for at least the last 7 days. i don't get it running...! currently, for testing, i use two different realms: mydomain.net (o=home,dc=mydit,dc=lan) test.mydomain.net (o=test,dc=mydit,dc=lan) in the slapd.conf i added: # sasl-realm mydomain.net authz-regexp uid=(.*),cn=test.mydomain.net,cn=digest-md5,cn=auth uid=$1,ou=users,o=test,dc=ditroot authz-regexp uid=(.*),cn=mydomain.net,cn=digest-md5,cn=auth uid=$1,ou=users,o=home,dc=ditroot authz-regexp uid=(.*),cn=digest-md5,cn=auth uid=$1,ou=users,o=home,dc=ditroot as you can see, the sasl-realm parameter is commented. whether or not i comment or uncomment it, it does not work. (actualy it works, but only either for the default realm or through the last sasl-regexp if i set it, all authentication attemps are of the format: uid=XY,cn=mydomain.net,cn=digest-md5,cn=auth if i do not set it, all authentication is done using: uid=XY,cn=digest-md5,cn=auth i realy tried a lot, e.g.: (things like -h, ... are covered by the ldap.conf) - ldapwhoami -U XY -R test.mydomain.net - ldapwhoami -U XY(a)test.mydomain.net - ldapsearch -U XY -R test.mydomain.net - ldap... of course all of those test where performed with different -R, ... values. i realy do not know what to do anymore, i've got no more ideas... also what i do not understand is whether or not this is a problem with my cyrus-sasl installation, but i cannot imagine that. i guess i'm missing something but i don't know what. can someone help me with this, please? have a nice day... d.a.s.

1 0

Re: (ITS#6230) test056-monitor: comparison failed - database monitor output is not correct
by hyc＠symas.com 27 Jul '09

27 Jul '09

michael(a)stroeder.com wrote: > Full_Name: Michael Ströder > Version: HEAD > OS: openSUSE Linux 11.1 > URL: > Submission from: (NULL) (84.163.81.222) > > > Please let me know whether testrun/ is needed for examining this issue: Never mind, fixed in HEAD. > >>>>>> Starting test056-monitor for bdb... > running defines.sh > Starting slapd on TCP/IP port ... > Using ldapsearch to check that slapd is running... > Using ldapsearch to read connection monitor entries... > Filtering ldapsearch results... > Filtering expected data... > Comparing filter output... > Using ldapsearch to read database monitor entries... > Filtering ldapsearch results... > Comparing filter output... > comparison failed - database monitor output is not correct >>>>>> ./scripts/test056-monitor failed for bdb (exit 1) > make[2]: *** [bdb-mod] Error 1 > make[2]: Leaving directory `/usr/src/michael/openldap/HEAD/openldap/tests' > make[1]: *** [test] Error 2 > make[1]: Leaving directory `/usr/src/michael/openldap/HEAD/openldap/tests' > make: *** [test] Error 2 > > -- -- 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#6230) test056-monitor: comparison failed - database monitor output is not correct
by hyc＠symas.com 27 Jul '09

27 Jul '09

michael(a)stroeder.com wrote: > Full_Name: Michael Ströder > Version: HEAD > OS: openSUSE Linux 11.1 > URL: > Submission from: (NULL) (84.163.81.222) > > > Please let me know whether testrun/ is needed for examining this issue: You could simply post the diff of the two files it was comparing. > >>>>>> Starting test056-monitor for bdb... > running defines.sh > Starting slapd on TCP/IP port ... > Using ldapsearch to check that slapd is running... > Using ldapsearch to read connection monitor entries... > Filtering ldapsearch results... > Filtering expected data... > Comparing filter output... > Using ldapsearch to read database monitor entries... > Filtering ldapsearch results... > Comparing filter output... > comparison failed - database monitor output is not correct >>>>>> ./scripts/test056-monitor failed for bdb (exit 1) > make[2]: *** [bdb-mod] Error 1 > make[2]: Leaving directory `/usr/src/michael/openldap/HEAD/openldap/tests' > make[1]: *** [test] Error 2 > make[1]: Leaving directory `/usr/src/michael/openldap/HEAD/openldap/tests' > make: *** [test] Error 2 > > -- -- 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

(ITS#6230) test056-monitor: comparison failed - database monitor output is not correct
by michael＠stroeder.com 27 Jul '09

27 Jul '09

Full_Name: Michael Ströder Version: HEAD OS: openSUSE Linux 11.1 URL: Submission from: (NULL) (84.163.81.222) Please let me know whether testrun/ is needed for examining this issue: >>>>> Starting test056-monitor for bdb... running defines.sh Starting slapd on TCP/IP port ... Using ldapsearch to check that slapd is running... Using ldapsearch to read connection monitor entries... Filtering ldapsearch results... Filtering expected data... Comparing filter output... Using ldapsearch to read database monitor entries... Filtering ldapsearch results... Comparing filter output... comparison failed - database monitor output is not correct >>>>> ./scripts/test056-monitor failed for bdb (exit 1) make[2]: *** [bdb-mod] Error 1 make[2]: Leaving directory `/usr/src/michael/openldap/HEAD/openldap/tests' make[1]: *** [test] Error 2 make[1]: Leaving directory `/usr/src/michael/openldap/HEAD/openldap/tests' make: *** [test] Error 2

1 0

Re: (ITS#6229) make test blocked on test001-slapadd
by battery＠writeme.com 27 Jul '09

27 Jul '09

--0015175707f6684066046fb12f9b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Yeah... those. On Mon, Jul 27, 2009 at 8:48 AM, czybear <czybear(a)qq.com> wrote: > Did you mean patches from the following URL? I didn't apply them yet, I'll > try them tomorry, thank you! > > http://www.oracle.com/technology/products/berkeley-db/db/update/4.7.25/patc… > > > ------------------ Original ------------------ > *From: * "Matt Kassawara"<battery(a)writeme.com>; > *Date: * Mon, Jul 27, 2009 10:40 PM > *To: * "czybear"<czybear(a)qq.com>; > *Cc: * "openldap-its"<openldap-its(a)openldap.org>; > *Subject: * Re: (ITS#6229) make test blocked on test001-slapadd > > Did you build against BDB 4.7.25? ?If so, did you apply all the patches? > > On Mon, Jul 27, 2009 at 3:04 AM, <czybear(a)qq.com> wrote: > >> Full_Name: John Chen >> Version: 2.4.16/2.4.17 >> OS: RHEL AS 5.2 (Tikanga) x86)64 >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (117.88.156.12) >> >> >> [root@as5u2-64]# make test >> cd tests; make test >> make[1]: Entering directory `/home/install/ldap-2.4/openldap-2.4.16/tests' >> make[2]: Entering directory `/home/install/ldap-2.4/openldap-2.4.16/tests' >> Initiating LDAP tests for BDB... >> Cleaning up test run directory leftover from previous run. >> Running ./scripts/all... >> >>>>> Executing all LDAP tests for bdb >> >>>>> Starting test000-rootdse ... >> running defines.sh >> Starting slapd on TCP/IP port 9011... >> Using ldapsearch to retrieve the root DSE... >> Waiting 5 seconds for slapd to start... >> Using ldapsearch to retrieve the cn=Subschema... >> Using ldapsearch to retrieve the cn=Monitor... >> dn: >> objectClass: top >> objectClass: OpenLDAProotDSE >> structuralObjectClass: OpenLDAProotDSE >> configContext: cn=config >> namingContexts: o=OpenLDAP Project,l=Internet >> monitorContext: cn=Monitor >> supportedControl: 1.3.6.1.4.1.4203.1.9.1.1 >> supportedControl: 2.16.840.1.113730.3.4.18 >> supportedControl: 2.16.840.1.113730.3.4.2 >> supportedControl: 1.3.6.1.4.1.4203.1.10.1 >> supportedControl: 1.2.840.113556.1.4.319 >> supportedControl: 1.2.826.0.1.3344810.2.3 >> supportedControl: 1.3.6.1.1.13.2 >> supportedControl: 1.3.6.1.1.13.1 >> supportedControl: 1.3.6.1.1.12 >> supportedExtension: 1.3.6.1.4.1.4203.1.11.1 >> supportedExtension: 1.3.6.1.4.1.4203.1.11.3 >> supportedExtension: 1.3.6.1.1.8 >> supportedFeatures: 1.3.6.1.1.14 >> supportedFeatures: 1.3.6.1.4.1.4203.1.5.1 >> supportedFeatures: 1.3.6.1.4.1.4203.1.5.2 >> supportedFeatures: 1.3.6.1.4.1.4203.1.5.3 >> supportedFeatures: 1.3.6.1.4.1.4203.1.5.4 >> supportedFeatures: 1.3.6.1.4.1.4203.1.5.5 >> supportedLDAPVersion: 3 >> vendorName: The OpenLDAP Project <http://www.openldap.org/> >> entryDN: >> subschemaSubentry: cn=Subschema >> >> dn: cn=Subschema >> objectClass: top >> objectClass: subentry >> objectClass: subschema >> objectClass: extensibleObject >> cn: Subschema >> >> dn: cn=Monitor >> objectClass: monitorServer >> cn: Monitor >> description: This subtree contains monitoring/managing objects. >> description: This object contains information about this server. >> description: Most of the information is held in operational attributes, >> which >> ?must be explicitly requested. >> monitoredInfo: OpenLDAP: slapd 2.4.16 (Jul 23 2009 13:44:24) >> >> >>>>> Test succeeded >> >>>>> ./scripts/test000-rootdse completed OK. >> >> >>>>> Starting test001-slapadd ... >> running defines.sh >> Running slapadd to build slapd database... >> >> ========================================== >> Then blocked, and no moving any more ... >> >> > --0015175707f6684066046fb12f9b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Yeah... those.<br><br><div class=3D"gmail_quote">On Mon, Jul 27, 2009 at 8:= 48 AM, czybear <span dir=3D"ltr"><<a href=3D"mailto:czybear@qq.com">czyb= ear(a)qq.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style= =3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div>Did you mean patches from the following URL? I didn't apply them y= et, I'll try them tomorry, thank you!</div><div class=3D"im"> <div><a href=3D"http://www.oracle.com/technology/products/berkeley-db/db/up= date/4.7.25/patch.4.7.25.html" target=3D"_blank">http://www.oracle.com/tech= nology/products/berkeley-db/db/update/4.7.25/patch.4.7.25.html</a></div> </div><div> <div>=A0</div> <div>=A0</div> <div style=3D"color:#000"><div class=3D"im"> <div style=3D"padding-right:0px;padding-left:0px;font-size:12px;padding-bot= tom:2px;padding-top:2px;font-family:Arial Narrow">------------------=A0Orig= inal=A0------------------</div> <div style=3D"font-size:12px"> <div><b>From: </b>=A0"Matt Kassawara"<<a href=3D"mailto:batter= y(a)writeme.com" target=3D"_blank">battery(a)writeme.com</a>>;</div> <div><b>Date: </b>=A0Mon, Jul 27, 2009 10:40 PM</div> <div><b>To: </b>=A0"czybear"<<a href=3D"mailto:czybear@qq.com"= target=3D"_blank">czybear(a)qq.com</a>>; </div> <div><b>Cc: </b>=A0"openldap-its"<<a href=3D"mailto:openldap-i= ts(a)openldap.org" target=3D"_blank">openldap-its(a)openldap.org</a>>; </div= > <div><b>Subject: </b>=A0Re: (ITS#6229) make test blocked on test001-slapadd= </div></div> <div>=A0</div></div><div><div class=3D"h5">Did you build against BDB 4.7.25= ? ?If so, did you apply all the patches?<br><br> <div class=3D"gmail_quote">On Mon, Jul 27, 2009 at 3:04 AM, <span dir=3D"lt= r"><<a href=3D"mailto:czybear@qq.com" target=3D"_blank">czybear(a)qq.com</= a>></span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"padding-left:1ex;margin:0px 0px = 0px 0.8ex;border-left:#ccc 1px solid">Full_Name: John Chen<br>Version: 2.4.= 16/2.4.17<br>OS: RHEL AS 5.2 (Tikanga) x86)64<br>URL: <a href=3D"ftp://ftp.= openldap.org/incoming/" target=3D"_blank">ftp://ftp.openldap.org/incoming/<= /a><br> Submission from: (NULL) (117.88.156.12)<br><br><br>[root@as5u2-64]# make te= st<br>cd tests; make test<br>make[1]: Entering directory `/home/install/lda= p-2.4/openldap-2.4.16/tests'<br>make[2]: Entering directory `/home/inst= all/ldap-2.4/openldap-2.4.16/tests'<br> Initiating LDAP tests for BDB...<br>Cleaning up test run directory leftover= from previous run.<br>Running ./scripts/all...<br>>>>>> Exe= cuting all LDAP tests for bdb<br>>>>>> Starting test000-root= dse ...<br> running defines.sh<br>Starting slapd on TCP/IP port 9011...<br>Using ldapse= arch to retrieve the root DSE...<br>Waiting 5 seconds for slapd to start...= <br>Using ldapsearch to retrieve the cn=3DSubschema...<br>Using ldapsearch = to retrieve the cn=3DMonitor...<br> dn:<br>objectClass: top<br>objectClass: OpenLDAProotDSE<br>structuralObject= Class: OpenLDAProotDSE<br>configContext: cn=3Dconfig<br>namingContexts: o= =3DOpenLDAP Project,l=3DInternet<br>monitorContext: cn=3DMonitor<br>support= edControl: 1.3.6.1.4.1.4203.1.9.1.1<br> supportedControl: 2.16.840.1.113730.3.4.18<br>supportedControl: 2.16.840.1.= 113730.3.4.2<br>supportedControl: 1.3.6.1.4.1.4203.1.10.1<br>supportedContr= ol: 1.2.840.113556.1.4.319<br>supportedControl: 1.2.826.0.1.3344810.2.3<br> supportedControl: 1.3.6.1.1.13.2<br>supportedControl: 1.3.6.1.1.13.1<br>sup= portedControl: 1.3.6.1.1.12<br>supportedExtension: 1.3.6.1.4.1.4203.1.11.1<= br>supportedExtension: 1.3.6.1.4.1.4203.1.11.3<br>supportedExtension: 1.3.6= .1.1.8<br> supportedFeatures: 1.3.6.1.1.14<br>supportedFeatures: 1.3.6.1.4.1.4203.1.5.= 1<br>supportedFeatures: 1.3.6.1.4.1.4203.1.5.2<br>supportedFeatures: 1.3.6.= 1.4.1.4203.1.5.3<br>supportedFeatures: 1.3.6.1.4.1.4203.1.5.4<br>supportedF= eatures: 1.3.6.1.4.1.4203.1.5.5<br> supportedLDAPVersion: 3<br>vendorName: The OpenLDAP Project <<a href=3D"= http://www.openldap.org/" target=3D"_blank">http://www.openldap.org/</a>&gt= ;<br>entryDN:<br>subschemaSubentry: cn=3DSubschema<br><br>dn: cn=3DSubschem= a<br> objectClass: top<br>objectClass: subentry<br>objectClass: subschema<br>obje= ctClass: extensibleObject<br>cn: Subschema<br><br>dn: cn=3DMonitor<br>objec= tClass: monitorServer<br>cn: Monitor<br>description: This subtree contains = monitoring/managing objects.<br> description: This object contains information about this server.<br>descrip= tion: Most of the information is held in operational attributes, which<br>?= must be explicitly requested.<br>monitoredInfo: OpenLDAP: slapd 2.4.16 (Jul= 23 2009 13:44:24)<br> <br>>>>>> Test succeeded<br>>>>>> ./scripts/t= est000-rootdse completed OK.<br><br>>>>>> Starting test001-s= lapadd ...<br>running defines.sh<br>Running slapadd to build slapd database= ...<br> <br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Then blocked, = and no moving any more ...<br><br></blockquote></div><br></div></div></div>= </div></blockquote></div><br> --0015175707f6684066046fb12f9b--

1 0

Re: (ITS#6229) make test blocked on test001-slapadd
by battery＠writeme.com 27 Jul '09

27 Jul '09

--000e0cd51bbc607056046fb112fc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit http://www.oracle.com/technology/products/berkeley-db/db/update/4.7.25/patc… Include the list in your reply next time... On Mon, Jul 27, 2009 at 8:44 AM, czybear <czybear(a)qq.com> wrote: > yes, I build aginst BDB 4.7.25 and downloaded from > http://www.oracle.com/technology/software/products/berkeley-db/htdocs/popup… > I didn't see any patches about BDB 4.7.25 from Oracle yet. > > > ------------------ Original ------------------ > *From: * "Matt Kassawara"<battery(a)writeme.com>; > *Date: * Mon, Jul 27, 2009 10:40 PM > *To: * "czybear"<czybear(a)qq.com>; > *Cc: * "openldap-its"<openldap-its(a)openldap.org>; > *Subject: * Re: (ITS#6229) make test blocked on test001-slapadd > > Did you build against BDB 4.7.25? ?If so, did you apply all the patches? On > Mon, Jul 27, 2009 at 3:04 AM, wrote: Full_Name: John Chen Version: > 2.4.16/2.4.17 OS: RHEL AS 5.2 (Tikanga) x86)64 URL: > ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (117.88.156.12) > [root@as5u2-64]# make test cd tests; make test make[1]: Entering directory > `/home/install/ldap-2.4/openldap-2.4.16/tests' make[2]: Entering directory > `/home/install/ldap-2.4/openldap-2.4.16/tests' Initiating LDAP tests for > BDB... Cleaning up test run directory leftover from previous run. Running > ./scripts/all... >>>>> Executing all LDAP tests for bdb >>>>> Starting > test000-rootdse ... running defines.sh Starting slapd on TCP/IP port 9011... > Using ldapsearch to retrieve the root DSE... Waiting 5 seconds for slapd to > start... Using ldapsearch to retrieve the cn=Subschema... Using ldapsearch > to retrieve the cn=Monitor... dn: objectClass: top objectClass: > OpenLDAProotDSE structuralObjectClass: OpenLDAProotDSE configContext: > cn=config namingContexts: o=OpenLDAP Project,l=Internet monitorContext: > cn=Monitor supportedControl: 1.3.6.1.4.1.4203.1.9.1.1 supportedControl: > 2.16.840.1.113730.3.4.18 supportedControl: 2.16.840.1.113730.3.4.2 > supportedControl: 1.3.6.1.4.1.4203.1.10.1 supportedControl: > 1.2.840.113556.1.4.319 supportedControl: 1.2.826.0.1.3344810.2.3 > supportedControl: 1.3.6.1.1.13.2 supportedControl: 1.3.6.1.1.13.1 > supportedControl: 1.3.6.1.1.12 supportedExtension: 1.3.6.1.4.1.4203.1.11.1 > supportedExtension: 1.3.6.1.4.1.4203.1.11.3 supportedExtension: 1.3.6.1.1.8 > supportedFeatures: 1.3.6.1.1.14 supportedFeatures: 1.3.6.1.4.1.4203.1.5.1 > supportedFeatures: 1.3.6.1.4.1.4203.1.5.2 supportedFeatures: > 1.3.6.1.4.1.4203.1.5.3 supportedFeatures: 1.3.6.1.4.1.4203.1.5.4 > supportedFeatures: 1.3.6.1.4.1.4203.1.5.5 supportedLDAPVersion: 3 > vendorName: The OpenLDAP Project entryDN: subschemaSubentry: cn=Subschema > dn: cn=Subschema objectClass: top objectClass: subentry objectClass: > subschema objectClass: extensibleObject cn: Subschema dn: cn=Monitor > objectClass: monitorServer cn: Monitor description: This subtree contains > monitoring/managing objects. description: This object contains information > about this server. description: Most of the information is held in > operational attributes, which ?must be explicitly requested. monitoredInfo: > OpenLDAP: slapd 2.4.16 (Jul 23 2009 13:44:24) >>>>> Test succeeded >>>>> > ./scripts/test000-rootdse completed OK. >>>>> Starting test001-slapadd ... > running defines.sh Running slapadd to build slapd database... > ========================================== Then blocked, and no moving any > more ... > --000e0cd51bbc607056046fb112fc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <div><a href=3D"http://www.oracle.com/technology/products/berkeley-db/db/up= date/4.7.25/patch.4.7.25.html">http://www.oracle.com/technology/products/be= rkeley-db/db/update/4.7.25/patch.4.7.25.html</a><br></div><div></div><div> Include the list in your reply next time...</div><br><div class=3D"gmail_qu= ote">On Mon, Jul 27, 2009 at 8:44 AM, czybear <span dir=3D"ltr"><<a href= =3D"mailto:czybear@qq.com">czybear(a)qq.com</a>></span> wrote:<br><blockqu= ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s= olid;padding-left:1ex;"> <div>yes, I build aginst BDB 4.7.25 and downloaded from <a href=3D"http://w= ww.oracle.com/technology/software/products/berkeley-db/htdocs/popup/db/4.7.= 25/db-targz.html" target=3D"_blank">http://www.oracle.com/technology/softwa= re/products/berkeley-db/htdocs/popup/db/4.7.25/db-targz.html</a></div> <div>I didn't see any patches about BDB 4.7.25 from Oracle yet.</div> <div> <div>=A0</div> <div>=A0</div> <div style=3D"color:#000"> <div style=3D"padding-right:0px;padding-left:0px;font-size:12px;padding-bot= tom:2px;padding-top:2px;font-family:Arial Narrow">------------------=A0Orig= inal=A0------------------</div> <div style=3D"font-size:12px"> <div><b>From: </b>=A0"Matt Kassawara"<<a href=3D"mailto:batter= y(a)writeme.com" target=3D"_blank">battery(a)writeme.com</a>>;</div> <div><b>Date: </b>=A0Mon, Jul 27, 2009 10:40 PM</div> <div><b>To: </b>=A0"czybear"<<a href=3D"mailto:czybear@qq.com"= target=3D"_blank">czybear(a)qq.com</a>>; </div> <div><b>Cc: </b>=A0"openldap-its"<<a href=3D"mailto:openldap-i= ts(a)openldap.org" target=3D"_blank">openldap-its(a)openldap.org</a>>; </div= > <div><b>Subject: </b>=A0Re: (ITS#6229) make test blocked on test001-slapadd= </div></div> <div>=A0</div>Did you build against BDB 4.7.25? ?If so, did you apply all t= he patches? On Mon, Jul 27, 2009 at 3:04 AM, wrote: Full_Name: John Chen Ve= rsion: 2.4.16/2.4.17 OS: RHEL AS 5.2 (Tikanga) x86)64 URL: <a href=3D"ftp:/= /ftp.openldap.org/incoming/" target=3D"_blank">ftp://ftp.openldap.org/incom= ing/</a> Submission from: (NULL) (117.88.156.12) [root@as5u2-64]# make test= cd tests; make test make[1]: Entering directory `/home/install/ldap-2.4/op= enldap-2.4.16/tests' make[2]: Entering directory `/home/install/ldap-2.= 4/openldap-2.4.16/tests' Initiating LDAP tests for BDB... Cleaning up t= est run directory leftover from previous run. Running ./scripts/all... >= >>>> Executing all LDAP tests for bdb >>>>> Star= ting test000-rootdse ... running defines.sh Starting slapd on TCP/IP port 9= 011... Using ldapsearch to retrieve the root DSE... Waiting 5 seconds for s= lapd to start... Using ldapsearch to retrieve the cn=3DSubschema... Using l= dapsearch to retrieve the cn=3DMonitor... dn: objectClass: top objectClass:= OpenLDAProotDSE structuralObjectClass: OpenLDAProotDSE configContext: cn= =3Dconfig namingContexts: o=3DOpenLDAP Project,l=3DInternet monitorContext:= cn=3DMonitor supportedControl: 1.3.6.1.4.1.4203.1.9.1.1 supportedControl: = 2.16.840.1.113730.3.4.18 supportedControl: 2.16.840.1.113730.3.4.2 supporte= dControl: 1.3.6.1.4.1.4203.1.10.1 supportedControl: 1.2.840.113556.1.4.319 = supportedControl: 1.2.826.0.1.3344810.2.3 supportedControl: 1.3.6.1.1.13.2 = supportedControl: 1.3.6.1.1.13.1 supportedControl: 1.3.6.1.1.12 supportedEx= tension: 1.3.6.1.4.1.4203.1.11.1 supportedExtension: 1.3.6.1.4.1.4203.1.11.= 3 supportedExtension: 1.3.6.1.1.8 supportedFeatures: 1.3.6.1.1.14 supported= Features: 1.3.6.1.4.1.4203.1.5.1 supportedFeatures: 1.3.6.1.4.1.4203.1.5.2 = supportedFeatures: 1.3.6.1.4.1.4203.1.5.3 supportedFeatures: 1.3.6.1.4.1.42= 03.1.5.4 supportedFeatures: 1.3.6.1.4.1.4203.1.5.5 supportedLDAPVersion: 3 = vendorName: The OpenLDAP Project entryDN: subschemaSubentry: cn=3DSubschema= dn: cn=3DSubschema objectClass: top objectClass: subentry objectClass: sub= schema objectClass: extensibleObject cn: Subschema dn: cn=3DMonitor objectC= lass: monitorServer cn: Monitor description: This subtree contains monitori= ng/managing objects. description: This object contains information about th= is server. description: Most of the information is held in operational attr= ibutes, which ?must be explicitly requested. monitoredInfo: OpenLDAP: slapd= 2.4.16 (Jul 23 2009 13:44:24) >>>>> Test succeeded >>= >>> ./scripts/test000-rootdse completed OK. >>>>> S= tarting test001-slapadd ... running defines.sh Running slapadd to build sla= pd database... =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Then blo= cked, and no moving any more ... </div> </div></blockquote></div><br> --000e0cd51bbc607056046fb112fc--

1 0

Re: (ITS#6229) make test blocked on test001-slapadd
by battery＠writeme.com 27 Jul '09

27 Jul '09

--000e0cd2e7328a11aa046fb0ee75 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Did you build against BDB 4.7.25? If so, did you apply all the patches? On Mon, Jul 27, 2009 at 3:04 AM, <czybear(a)qq.com> wrote: > Full_Name: John Chen > Version: 2.4.16/2.4.17 > OS: RHEL AS 5.2 (Tikanga) x86)64 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (117.88.156.12) > > > [root@as5u2-64]# make test > cd tests; make test > make[1]: Entering directory `/home/install/ldap-2.4/openldap-2.4.16/tests' > make[2]: Entering directory `/home/install/ldap-2.4/openldap-2.4.16/tests' > Initiating LDAP tests for BDB... > Cleaning up test run directory leftover from previous run. > Running ./scripts/all... > >>>>> Executing all LDAP tests for bdb > >>>>> Starting test000-rootdse ... > running defines.sh > Starting slapd on TCP/IP port 9011... > Using ldapsearch to retrieve the root DSE... > Waiting 5 seconds for slapd to start... > Using ldapsearch to retrieve the cn=Subschema... > Using ldapsearch to retrieve the cn=Monitor... > dn: > objectClass: top > objectClass: OpenLDAProotDSE > structuralObjectClass: OpenLDAProotDSE > configContext: cn=config > namingContexts: o=OpenLDAP Project,l=Internet > monitorContext: cn=Monitor > supportedControl: 1.3.6.1.4.1.4203.1.9.1.1 > supportedControl: 2.16.840.1.113730.3.4.18 > supportedControl: 2.16.840.1.113730.3.4.2 > supportedControl: 1.3.6.1.4.1.4203.1.10.1 > supportedControl: 1.2.840.113556.1.4.319 > supportedControl: 1.2.826.0.1.3344810.2.3 > supportedControl: 1.3.6.1.1.13.2 > supportedControl: 1.3.6.1.1.13.1 > supportedControl: 1.3.6.1.1.12 > supportedExtension: 1.3.6.1.4.1.4203.1.11.1 > supportedExtension: 1.3.6.1.4.1.4203.1.11.3 > supportedExtension: 1.3.6.1.1.8 > supportedFeatures: 1.3.6.1.1.14 > supportedFeatures: 1.3.6.1.4.1.4203.1.5.1 > supportedFeatures: 1.3.6.1.4.1.4203.1.5.2 > supportedFeatures: 1.3.6.1.4.1.4203.1.5.3 > supportedFeatures: 1.3.6.1.4.1.4203.1.5.4 > supportedFeatures: 1.3.6.1.4.1.4203.1.5.5 > supportedLDAPVersion: 3 > vendorName: The OpenLDAP Project <http://www.openldap.org/> > entryDN: > subschemaSubentry: cn=Subschema > > dn: cn=Subschema > objectClass: top > objectClass: subentry > objectClass: subschema > objectClass: extensibleObject > cn: Subschema > > dn: cn=Monitor > objectClass: monitorServer > cn: Monitor > description: This subtree contains monitoring/managing objects. > description: This object contains information about this server. > description: Most of the information is held in operational attributes, > which > must be explicitly requested. > monitoredInfo: OpenLDAP: slapd 2.4.16 (Jul 23 2009 13:44:24) > > >>>>> Test succeeded > >>>>> ./scripts/test000-rootdse completed OK. > > >>>>> Starting test001-slapadd ... > running defines.sh > Running slapadd to build slapd database... > > ========================================== > Then blocked, and no moving any more ... > > --000e0cd2e7328a11aa046fb0ee75 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Did you build against BDB 4.7.25? =A0If so, did you apply all the patches?<= br><br><div class=3D"gmail_quote">On Mon, Jul 27, 2009 at 3:04 AM, <span d= ir=3D"ltr"><<a href=3D"mailto:czybear@qq.com">czybear(a)qq.com</a>></sp= an> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex;">Full_Name: John Chen<br> Version: 2.4.16/2.4.17<br> OS: RHEL AS 5.2 (Tikanga) x86)64<br> URL: <a href=3D"ftp://ftp.openldap.org/incoming/" target=3D"_blank">ftp://f= tp.openldap.org/incoming/</a><br> Submission from: (NULL) (117.88.156.12)<br> <br> <br> [root@as5u2-64]# make test<br> cd tests; make test<br> make[1]: Entering directory `/home/install/ldap-2.4/openldap-2.4.16/tests&#= 39;<br> make[2]: Entering directory `/home/install/ldap-2.4/openldap-2.4.16/tests&#= 39;<br> Initiating LDAP tests for BDB...<br> Cleaning up test run directory leftover from previous run.<br> Running ./scripts/all...<br> >>>>> Executing all LDAP tests for bdb<br> >>>>> Starting test000-rootdse ...<br> running defines.sh<br> Starting slapd on TCP/IP port 9011...<br> Using ldapsearch to retrieve the root DSE...<br> Waiting 5 seconds for slapd to start...<br> Using ldapsearch to retrieve the cn=3DSubschema...<br> Using ldapsearch to retrieve the cn=3DMonitor...<br> dn:<br> objectClass: top<br> objectClass: OpenLDAProotDSE<br> structuralObjectClass: OpenLDAProotDSE<br> configContext: cn=3Dconfig<br> namingContexts: o=3DOpenLDAP Project,l=3DInternet<br> monitorContext: cn=3DMonitor<br> supportedControl: 1.3.6.1.4.1.4203.1.9.1.1<br> supportedControl: 2.16.840.1.113730.3.4.18<br> supportedControl: 2.16.840.1.113730.3.4.2<br> supportedControl: 1.3.6.1.4.1.4203.1.10.1<br> supportedControl: 1.2.840.113556.1.4.319<br> supportedControl: 1.2.826.0.1.3344810.2.3<br> supportedControl: 1.3.6.1.1.13.2<br> supportedControl: 1.3.6.1.1.13.1<br> supportedControl: 1.3.6.1.1.12<br> supportedExtension: 1.3.6.1.4.1.4203.1.11.1<br> supportedExtension: 1.3.6.1.4.1.4203.1.11.3<br> supportedExtension: 1.3.6.1.1.8<br> supportedFeatures: 1.3.6.1.1.14<br> supportedFeatures: 1.3.6.1.4.1.4203.1.5.1<br> supportedFeatures: 1.3.6.1.4.1.4203.1.5.2<br> supportedFeatures: 1.3.6.1.4.1.4203.1.5.3<br> supportedFeatures: 1.3.6.1.4.1.4203.1.5.4<br> supportedFeatures: 1.3.6.1.4.1.4203.1.5.5<br> supportedLDAPVersion: 3<br> vendorName: The OpenLDAP Project <<a href=3D"http://www.openldap.org/" t= arget=3D"_blank">http://www.openldap.org/</a>><br> entryDN:<br> subschemaSubentry: cn=3DSubschema<br> <br> dn: cn=3DSubschema<br> objectClass: top<br> objectClass: subentry<br> objectClass: subschema<br> objectClass: extensibleObject<br> cn: Subschema<br> <br> dn: cn=3DMonitor<br> objectClass: monitorServer<br> cn: Monitor<br> description: This subtree contains monitoring/managing objects.<br> description: This object contains information about this server.<br> description: Most of the information is held in operational attributes, whi= ch<br> =A0must be explicitly requested.<br> monitoredInfo: OpenLDAP: slapd 2.4.16 (Jul 23 2009 13:44:24)<br> <br> >>>>> Test succeeded<br> >>>>> ./scripts/test000-rootdse completed OK.<br> <br> >>>>> Starting test001-slapadd ...<br> running defines.sh<br> Running slapadd to build slapd database...<br> <br> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br> Then blocked, and no moving any more ...<br> <br> </blockquote></div><br> --000e0cd2e7328a11aa046fb0ee75--

1 0

(ITS#6229) make test blocked on test001-slapadd
by czybear＠qq.com 27 Jul '09

27 Jul '09

Full_Name: John Chen Version: 2.4.16/2.4.17 OS: RHEL AS 5.2 (Tikanga) x86)64 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (117.88.156.12) [root@as5u2-64]# make test cd tests; make test make[1]: Entering directory `/home/install/ldap-2.4/openldap-2.4.16/tests' make[2]: Entering directory `/home/install/ldap-2.4/openldap-2.4.16/tests' Initiating LDAP tests for BDB... Cleaning up test run directory leftover from previous run. Running ./scripts/all... >>>>> Executing all LDAP tests for bdb >>>>> Starting test000-rootdse ... running defines.sh Starting slapd on TCP/IP port 9011... Using ldapsearch to retrieve the root DSE... Waiting 5 seconds for slapd to start... Using ldapsearch to retrieve the cn=Subschema... Using ldapsearch to retrieve the cn=Monitor... dn: objectClass: top objectClass: OpenLDAProotDSE structuralObjectClass: OpenLDAProotDSE configContext: cn=config namingContexts: o=OpenLDAP Project,l=Internet monitorContext: cn=Monitor supportedControl: 1.3.6.1.4.1.4203.1.9.1.1 supportedControl: 2.16.840.1.113730.3.4.18 supportedControl: 2.16.840.1.113730.3.4.2 supportedControl: 1.3.6.1.4.1.4203.1.10.1 supportedControl: 1.2.840.113556.1.4.319 supportedControl: 1.2.826.0.1.3344810.2.3 supportedControl: 1.3.6.1.1.13.2 supportedControl: 1.3.6.1.1.13.1 supportedControl: 1.3.6.1.1.12 supportedExtension: 1.3.6.1.4.1.4203.1.11.1 supportedExtension: 1.3.6.1.4.1.4203.1.11.3 supportedExtension: 1.3.6.1.1.8 supportedFeatures: 1.3.6.1.1.14 supportedFeatures: 1.3.6.1.4.1.4203.1.5.1 supportedFeatures: 1.3.6.1.4.1.4203.1.5.2 supportedFeatures: 1.3.6.1.4.1.4203.1.5.3 supportedFeatures: 1.3.6.1.4.1.4203.1.5.4 supportedFeatures: 1.3.6.1.4.1.4203.1.5.5 supportedLDAPVersion: 3 vendorName: The OpenLDAP Project <http://www.openldap.org/> entryDN: subschemaSubentry: cn=Subschema dn: cn=Subschema objectClass: top objectClass: subentry objectClass: subschema objectClass: extensibleObject cn: Subschema dn: cn=Monitor objectClass: monitorServer cn: Monitor description: This subtree contains monitoring/managing objects. description: This object contains information about this server. description: Most of the information is held in operational attributes, which must be explicitly requested. monitoredInfo: OpenLDAP: slapd 2.4.16 (Jul 23 2009 13:44:24) >>>>> Test succeeded >>>>> ./scripts/test000-rootdse completed OK. >>>>> Starting test001-slapadd ... running defines.sh Running slapadd to build slapd database... ========================================== Then blocked, and no moving any more ...

1 0

Re: (ITS#6228) test000-rootdse: slapd fails to start
by hyc＠symas.com 25 Jul '09

25 Jul '09

michael(a)stroeder.com wrote: > Full_Name: Michael Ströder > Version: HEAD > OS: openSUSE Linux 11.1 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (84.163.115.191) > > > HEAD synced right now fails right in test000. Thanks, fixed. > > ----------- console output ----------- > > michael@nb2:/usr/src/michael/openldap/HEAD/openldap> make test > cd tests; make test > make[1]: Entering directory `/usr/src/michael/openldap/HEAD/openldap/tests' > make[2]: Entering directory `/usr/src/michael/openldap/HEAD/openldap/tests' > Initiating LDAP tests for BDB... > Cleaning up test run directory leftover from previous run. > Running ./scripts/all for bdb... >>>>>> Executing all LDAP tests for bdb >>>>>> Starting test000-rootdse for bdb... > running defines.sh > Starting slapd on TCP/IP port 9011... > Using ldapsearch to retrieve the root DSE... > Waiting 5 seconds for slapd to start... > Waiting 5 seconds for slapd to start... > Waiting 5 seconds for slapd to start... > Waiting 5 seconds for slapd to start... > Waiting 5 seconds for slapd to start... > Waiting 5 seconds for slapd to start... > ./scripts/test000-rootdse: line 66: kill: (2749) - No such process > ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1) >>>>>> Test failed >>>>>> ./scripts/test000-rootdse failed for bdb (exit 255) > make[2]: *** [bdb-mod] Error 255 > make[2]: Leaving directory `/usr/src/michael/openldap/HEAD/openldap/tests' > make[1]: *** [test] Error 2 > make[1]: Leaving directory `/usr/src/michael/openldap/HEAD/openldap/tests' > make: *** [test] Error 2 > > ----------- last lines of tests/testrun/slapd.1.log ----------- > > backend_startup_one: starting "cn=config" > config_back_db_open > config_build_entry: "cn=config" > config_build_entry: "cn=module{0}" > config_build_entry: "cn=module{1}" > config_build_entry: "cn=schema" > config_build_entry: "cn={0}core" > config_build_entry: "cn={1}cosine" > config_build_entry: "cn={2}corba" > config_build_entry: "cn={3}java" > config_build_entry: "cn={4}inetorgperson" > config_build_entry: "cn={5}misc" > config_build_entry: "cn={6}nis" > config_build_entry: "cn={7}openldap" > config_build_entry: "cn={8}duaconf" > config_build_entry: "cn={9}dyngroup" > config_build_entry: "cn={10}ppolicy" > config_build_entry: "olcDatabase={-1}frontend" > config_build_entry: "olcDatabase={0}config" > config_build_entry: "olcDatabase={1}bdb" > config_build_attrs: error 21 on olcDbCacheSize value #0 > config_build_entry: build "1000d" failed: "" > backend_startup_one: bi_db_open failed! (-1) > lt-slapd shutdown: initiated > ====> bdb_cache_release_all > lt-slapd destroy: freeing system resources. > slapd stopped. > > -- -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs