From: Quanah Gibson-Mount Subject: RE24 testing call (2.4.45) LMDB RE0.9 testing call (0.9.20)
For this testing call, we particularly need folks to test OpenLDAP with startTLS/LDAPS when compiled against OpenSSL (both pre 1.1 series and with the 1.1 series).
Compiled successfully with Gentoo linux and openSSL 1.02j/cyrus-sasl 2.1.26, configured as:
--prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-silent-rules --libdir=/usr/lib64 --libexecdir=/usr/lib64/openldap --disable-static --enable-ldap --enable-slapd --enable-bdb --enable-hdb --enable-dnssrv=mod --enable-ldap=mod --enable-mdb=mod --enable-meta=mod --enable-monitor=mod --enable-null=mod --enable-passwd=mod --enable-relay=mod --enable-shell=mod --enable-sock=mod --disable-perl --disable-sql --disable-crypt --disable-slp --disable-lmpasswd --enable-syslog --enable-aci --enable-cleartext --enable-modules --enable-rewrite --enable-rlookups --enable-slapi --enable-syncprov=yes --enable-overlays=mod --enable-ipv6 --with-cyrus-sasl --enable-spasswd --disable-wrappers --with-tls=openssl --enable-dynamic --enable-local --enable-proctitle --enable-shared
make test completed successfully, is there any particular way to verify all the tests were okay? Does the make itself fail if any of the tests do, I did not see a summary at the end. make its was not as happy:
Starting its4326 ...
running defines.sh Running slapadd to build slapd database... Starting slapd on TCP/IP port 9011... Using ldapsearch to check that slapd is running... Starting proxy slapd on TCP/IP port 9012... Using ldapsearch to check that proxy slapd is running... 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... ldapsearch failed (255)! ./data/regressions/its4326/its4326: line 93: kill: (28780) - No such process
./data/regressions/its4326/its4326 failed (exit 255)
I see the fix for ITS8432 is included in this release (yay); I was wondering if you've had any luck tracking down the underlying issue behind ITS8444? So far I still haven't seen any corruption or operational issues from it, but the rampant noise in the logs and errors being generated are quite disconcerting :). Plus they will potentially mask any errors that are actually indicative of a real problem.
Thanks.