- openldap-bugs - openldap.org

(ITS#4916) syncrpl consumer not listing contextcsn as operation attr
by brian＠zimbra.com 06 Apr '07

06 Apr '07

Full_Name: Brian Peterson Version: 2.3.34 OS: Linux URL: pro Submission from: (NULL) (66.92.25.194) When setup sync replication the contextCSN is available via ldapsearch on the provider but not the consumer as an operation attribute. If we do a slapcat on the consumer the resulting ldif contains the contextCSN. relavent slapd.conf entries from provider(please let me know if you want the entire file). database bdb suffix "" rootdn "uid=zimbra,cn=admins,cn=zimbra" # recommended for replication index entryUUID eq index entryCSN eq overlay syncprov syncprov-checkpoint 100 10 syncprov-sessionlog 500 slapd.conf entries from consumer. database bdb suffix "" rootdn "uid=zimbra,cn=admins,cn=zimbra" syncrepl rid=022 provider=ldap://ldapmaster:389 retry="60 +" type=refreshAndPersist schemachecking=off updatedn="uid=zimbrareplication,cn=admins,cn=zimbra" searchbase="" bindmethod=simple binddn="uid=zimbra,cn=admins,cn=zimbra" creditionals=secret updateref ldap://ldapmaster:389 Ldap search output from the consumer ldapsearch -LLL -x -D uid=zimbra,cn=admins,cn=zimbra -w secret -H ldap://ldapreplica:389 -s base -b "" + dn: structuralObjectClass: OpenLDAProotDSE configContext: cn=config namingContexts: 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.334810.2.3 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.1466.20037 supportedExtension: 1.3.6.1.4.1.4203.1.11.1 supportedExtension: 1.3.6.1.4.1.4203.1.11.3 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 entryDN: subschemaSubentry: cn=Subschema Top entry from slapcat ldif on the consumer. dn: objectClass: glue structuralObjectClass: glue contextCSN: 20070405182202Z#000000#00#000000 entryCSN: 20070405182202Z#000000#00#000000 modifiersName: uid=zimbra,cn=admins,cn=zimbra modifyTimestamp: 20070405182202Z

1 0

Re: (ITS#4915) Syncrepl task exits are not logged
by hyc＠symas.com 05 Apr '07

05 Apr '07

unix.gurus(a)gmail.com wrote: > Full_Name: Sean Burford > Version: 2.3.32 > OS: Linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (65.57.245.11) > > > It is hard to tell when the syncrepl task has exited. The attached patch adds > logging of syncrepl hard and soft failures. > > Using this patch, it is easier to spot unfortunate conditions where recoverable > failures are treated as hard failures, for example the third line below shows > that a (temporarily) unavailable kerberos credential cache causes a hard > failure: > GSSAPI Error: Miscellaneous failure (No credentials cache found) > do_syncrep1: rid 123 ldap_sasl_interactive_bind_s failed (-2) > do_syncrepl: rid 123 hard failure Looks like a good idea, thanks. I think I'd just change the messages to "giving up" or "quitting", and "retrying". That final else clause in your patch should never occur, there is no 3rd outcome. > > Hmm, no attachment because the FTP server returns: > 200 PORT command successful. > 150 Opening ASCII mode data connection for > 'openldap-2.3.32-syncrepl-log-failure.patch'. > ## > 452 Error writing file: No space left on device. > 1104 bytes sent in 0.00011 seconds (1e+04 Kbytes/s) > > The patch was: > *** openldap-2.3.32.orig/servers/slapd/syncrepl.c Wed Apr 4 17:21:31 > 2007 > --- openldap-2.3.32/servers/slapd/syncrepl.c Wed Apr 4 17:55:58 2007 > *************** > *** 1147,1159 **** > --- 1147,1169 ---- > } > > if ( !si->si_retrynum || si->si_retrynum[i] == RETRYNUM_TAIL ) > { > + Debug( LDAP_DEBUG_ANY, > + "do_syncrepl: rid %03d hard failure\n", > + si->si_rid, 0, 0 ); > ldap_pvt_runqueue_remove( &slapd_rq, rtask ); > } else if ( RETRYNUM_VALID( si->si_retrynum[i] ) ) { > if ( si->si_retrynum[i] > 0 ) > si->si_retrynum[i]--; > + Debug( LDAP_DEBUG_ANY, > + "do_syncrepl: rid %03d soft failure, > rescheduling (retries left: %d)\n", > + si->si_rid, si->si_retrynum[i], 0 ); > rtask->interval.tv_sec = si->si_retryinterval[i]; > ldap_pvt_runqueue_resched( &slapd_rq, rtask, 0 ); > slap_wake_listener(); > + } else { > + Debug( LDAP_DEBUG_ANY, > + "do_syncrepl: rid %03d soft failure, > rescheduling\n", > + si->si_rid, 0, 0 ); > } > } > > > -- -- 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

(ITS#4915) Syncrepl task exits are not logged
by unix.gurus＠gmail.com 05 Apr '07

05 Apr '07

Full_Name: Sean Burford Version: 2.3.32 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (65.57.245.11) It is hard to tell when the syncrepl task has exited. The attached patch adds logging of syncrepl hard and soft failures. Using this patch, it is easier to spot unfortunate conditions where recoverable failures are treated as hard failures, for example the third line below shows that a (temporarily) unavailable kerberos credential cache causes a hard failure: GSSAPI Error: Miscellaneous failure (No credentials cache found) do_syncrep1: rid 123 ldap_sasl_interactive_bind_s failed (-2) do_syncrepl: rid 123 hard failure Hmm, no attachment because the FTP server returns: 200 PORT command successful. 150 Opening ASCII mode data connection for 'openldap-2.3.32-syncrepl-log-failure.patch'. ## 452 Error writing file: No space left on device. 1104 bytes sent in 0.00011 seconds (1e+04 Kbytes/s) The patch was: *** openldap-2.3.32.orig/servers/slapd/syncrepl.c Wed Apr 4 17:21:31 2007 --- openldap-2.3.32/servers/slapd/syncrepl.c Wed Apr 4 17:55:58 2007 *************** *** 1147,1159 **** --- 1147,1169 ---- } if ( !si->si_retrynum || si->si_retrynum[i] == RETRYNUM_TAIL ) { + Debug( LDAP_DEBUG_ANY, + "do_syncrepl: rid %03d hard failure\n", + si->si_rid, 0, 0 ); ldap_pvt_runqueue_remove( &slapd_rq, rtask ); } else if ( RETRYNUM_VALID( si->si_retrynum[i] ) ) { if ( si->si_retrynum[i] > 0 ) si->si_retrynum[i]--; + Debug( LDAP_DEBUG_ANY, + "do_syncrepl: rid %03d soft failure, rescheduling (retries left: %d)\n", + si->si_rid, si->si_retrynum[i], 0 ); rtask->interval.tv_sec = si->si_retryinterval[i]; ldap_pvt_runqueue_resched( &slapd_rq, rtask, 0 ); slap_wake_listener(); + } else { + Debug( LDAP_DEBUG_ANY, + "do_syncrepl: rid %03d soft failure, rescheduling\n", + si->si_rid, 0, 0 ); } }

1 0

Re: (ITS#4907) Syncrepl consumer failing to perform deletes
by unix.gurus＠gmail.com 05 Apr '07

05 Apr '07

------=_Part_45311_2874873.1175811229646 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 4/3/07, Howard Chu <hyc(a)symas.com> wrote: > The log says that ITS#4638 was already fixed in 2.3.32. Why are you > still using that particular patch, given that an alternate solution is > already present in the release? I can't replicate ITS#4638 under 2.3.32, so you can mark ITS#4907 resolved (I removed the bad patch). I also see that in RE23 we had one more patch to fix some interaction > between slapo-rwm and back-meta for filter processing. I suggest you > test against the current RE23 code. I expect to push 2.3.35 out pretty > soon. Thank you. Sean ------=_Part_45311_2874873.1175811229646 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline <span class="gmail_quote">On 4/3/07, <b class="gmail_sendername">Howard Chu</b> <<a href="mailto:hyc@symas.com">hyc(a)symas.com</a>> wrote:</span><br><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> The log says that ITS#4638 was already fixed in 2.3.32. Why are you<br>still using that particular patch, given that an alternate solution is<br>already present in the release?</blockquote><div><br>I can't replicate ITS#4638 under 2.3.32, so you can mark ITS#4907 resolved (I removed the bad patch).<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I also see that in RE23 we had one more patch to fix some interaction <br>between slapo-rwm and back-meta for filter processing. I suggest you<br>test against the current RE23 code. I expect to push 2.3.35 out pretty soon.</blockquote><div><br>Thank you. <br></div><br></div>Sean ------=_Part_45311_2874873.1175811229646--

1 0

Re: (ITS#4913) configure & BerkleyDB
by ando＠sys-net.it 05 Apr '07

05 Apr '07

fredo(a)sundancer.us wrote: > Full_Name: Fred Obermann > Version: 2.3.34 > OS: linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (24.20.15.25) > > > I just downloaded, built and installed openldap-2.3.34 using BerkeleyDB-4.5.20. > > > There seems to be a disconnect between where openldap-2.3.34 'configure' expects > db.h is and where Oracle's build procedure puts db.h. > > For 4.5.20, db.h is located in "/usr/local/BerkeleyDB.4.5/include". Setting: > CPPFLAGS="I/usr/local/BerkeleyDB.4.5/include", prior to invoking 'configure' Perhaps adding a "-" before "I" could help. Please check and report. > does not seem to enable 'configure' to find 'db.h'. Providing soft link from > /usr/local/BerkeleyDB.4.5/include/db.h to /usr/include seems to fix this > problem > > Furthermore there seems to be a disconnect between the Oracle naming convention > for the BerkeleyDB libraries and what openldap's 'configure' utility seems to > expect. > > I set: > LIBS=-L/usr/local/BerkeleyDB.4.5/lib prior to invoking 'configure' > > But 'configure' is looking for libdb45.a or libdb-45.a or libdb4.5.a. > > However, what the Oracle build procedure produces are: libdb-4.5.a > libdb-4.5.la libdb-4.5.so libdb-4.so libdb.a libdb.so > > Creating a soft link from libdb-4.5.a to libdb45.a seems to fix this problem. > > Nonetheless, it would be better if the 'configure' script were expanded to > gracefully handle this latest release of BerkeleyDB from Oracle. > > > > > > 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#4913) configure & BerkleyDB
by hyc＠symas.com 05 Apr '07

05 Apr '07

fredo(a)sundancer.us wrote: > Full_Name: Fred Obermann > Version: 2.3.34 > OS: linux > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (24.20.15.25) > > > I just downloaded, built and installed openldap-2.3.34 using BerkeleyDB-4.5.20. > > > There seems to be a disconnect between where openldap-2.3.34 'configure' expects > db.h is and where Oracle's build procedure puts db.h. > > For 4.5.20, db.h is located in "/usr/local/BerkeleyDB.4.5/include". Setting: > CPPFLAGS="I/usr/local/BerkeleyDB.4.5/include", prior to invoking 'configure' > does not seem to enable 'configure' to find 'db.h'. Providing soft link from > /usr/local/BerkeleyDB.4.5/include/db.h to /usr/include seems to fix this > problem If that's exactly what you used, you're missing the "-" in CPPFLAGS="-I..." > Furthermore there seems to be a disconnect between the Oracle naming convention > for the BerkeleyDB libraries and what openldap's 'configure' utility seems to > expect. The configure script works perfectly fine with all 4.x releases of BerkeleyDB, including 4.6 which has not yet been publicly released. This ITS will be closed. -- -- 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

(ITS#4914) It's possible to add multiple config-Databases
by rhafer＠suse.de 05 Apr '07

05 Apr '07

Full_Name: Ralf Haferkamp Version: HEAD OS: Linux (Kernel 2.6) URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (89.166.166.70) Subject say it. You can add multiple olcDatabase=config Entries to the cn=config Backend. (With slapadd or through ldapadd) A fix is on the way to CVS. It will also make sure that olcDatabase=config always gets the Index 0.

1 0

(ITS#4913) configure & BerkleyDB
by fredo＠sundancer.us 04 Apr '07

04 Apr '07

Full_Name: Fred Obermann Version: 2.3.34 OS: linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (24.20.15.25) I just downloaded, built and installed openldap-2.3.34 using BerkeleyDB-4.5.20. There seems to be a disconnect between where openldap-2.3.34 'configure' expects db.h is and where Oracle's build procedure puts db.h. For 4.5.20, db.h is located in "/usr/local/BerkeleyDB.4.5/include". Setting: CPPFLAGS="I/usr/local/BerkeleyDB.4.5/include", prior to invoking 'configure' does not seem to enable 'configure' to find 'db.h'. Providing soft link from /usr/local/BerkeleyDB.4.5/include/db.h to /usr/include seems to fix this problem Furthermore there seems to be a disconnect between the Oracle naming convention for the BerkeleyDB libraries and what openldap's 'configure' utility seems to expect. I set: LIBS=-L/usr/local/BerkeleyDB.4.5/lib prior to invoking 'configure' But 'configure' is looking for libdb45.a or libdb-45.a or libdb4.5.a. However, what the Oracle build procedure produces are: libdb-4.5.a libdb-4.5.la libdb-4.5.so libdb-4.so libdb.a libdb.so Creating a soft link from libdb-4.5.a to libdb45.a seems to fix this problem. Nonetheless, it would be better if the 'configure' script were expanded to gracefully handle this latest release of BerkeleyDB from Oracle.

1 0

Re: (ITS#4911) slapadd uses slap_op_mutex uninitialized
by hyc＠symas.com 04 Apr '07

04 Apr '07

h.b.furuseth(a)usit.uio.no wrote: > Full_Name: Hallvard B Furuseth > Version: HEAD > OS: Linux > URL: > Submission from: (NULL) (129.240.202.105) > Submitted by: hallvard > > > slapadd uses slap_op_mutex uninitialized in operation.c:slap_op_time() Fixed. > Any hope of making the tools and slapd go through the same init/destroy code > in main(), maybe by making the server just another "tool"? Seems to me the > only hope of making bugs like this keep popping up... In the past the tools didn't use threads and didn't share as much code with slapd. As such, it seems a lot of subsystems really didn't need to be set up for tool mode. I guess things have changed since we now use Operation structures everywhere. Tools like slappasswd don't even read the slapd config. That means you can't use slappasswd with a dynamically loaded password-hash module. So yes, some of this structuring needs to be revisited. -- -- 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

ITS#4910 mirrormode
by hyc＠symas.com 04 Apr '07

04 Apr '07

The mirrormode functionality has changed in 2.4.4 (compared to 2.4.3 and earlier) since full multimaster is now supported. You must set a unique serverID on each server to enable replication. See slapd-config(5) for the olcServerID config item. -- -- 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#4912) test043 cores in bdb_locker_id_free()
by hyc＠symas.com 04 Apr '07

04 Apr '07

h.b.furuseth(a)usit.uio.no wrote: > Full_Name: Hallvard B Furuseth > Version: HEAD > OS: Linux > URL: > Submission from: (NULL) (129.240.202.105) > Submitted by: hallvard > > > test043 leaves behind two core files from a crash in bdb_locker_id_free(). Fixed. > > The test does succeed though. (Argh, I've got to dig up that test script > patch of mine, I don't even remember what the showstopper was anymore...) Would be nice to get that in. -- -- 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

(ITS#4912) test043 cores in bdb_locker_id_free()
by h.b.furuseth＠usit.uio.no 04 Apr '07

04 Apr '07

Full_Name: Hallvard B Furuseth Version: HEAD OS: Linux URL: Submission from: (NULL) (129.240.202.105) Submitted by: hallvard test043 leaves behind two core files from a crash in bdb_locker_id_free(). The test does succeed though. (Argh, I've got to dig up that test script patch of mine, I don't even remember what the showstopper was anymore...) >>>>> Starting 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... Using ldapadd to populate the producer directory... Waiting 15 seconds for syncrepl to receive changes... Stopping the provider, sleeping 10 seconds and restarting it... ./scripts/test043-delta-syncrepl: line 130: 5697 Segmentation fault (core dumped) $SLAPD -f $CONF1 -h $URI1 -d $LVL $TIMING >$LOG1 2>&1 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 succeeded ./scripts/test043-delta-syncrepl: line 356: 5715 Segmentation fault (core dumped) $SLAPD -f $CONF1 -h $URI1 -d $LVL $TIMING >>$LOG1 2>&1 >>>>> ./scripts/test043-delta-syncrepl completed OK. $ gdb ../servers/slapd/slapd core.5697 (the other crashes with the same backtrace) (gdb) thread apply all backtrace Thread 1 (process 5697): #0 0xdbdbdbdb in ?? () #1 0x08119e27 in bdb_locker_id_free (key=0x83536b0, data=0x7) at cache.c:1360 #2 0x0818e6ec in ldap_int_thread_pool_context_reset (vctx=0x8275160) at tpool.c:912 #3 0x081913a6 in ldap_pvt_thread_pool_context_reset (vctx=0x7) at thr_debug.c:1263 #4 0x080aad9f in slap_destroy () at init.c:271 #5 0x080670fb in main (argc=8, argv=0xbfffee84) at main.c:949 Configuration: CPPFLAGS='-DLDAP_REL_ENG -DLDAP_THREAD_DEBUG -DLDAP_RDWR_DEBUG' \ ./configure --prefix=/hbf/scratch/ldap/install/head \ --enable-crypt --enable-dynacl --enable-aci --enable-lmpasswd \ --enable-spasswd --enable-modules --enable-rlookups \ --enable-slapi --enable-slp --enable-wrappers \ --enable-backends --disable-sql --enable-overlays

1 0

(ITS#4911) slapadd uses slap_op_mutex uninitialized
by h.b.furuseth＠usit.uio.no 04 Apr '07

04 Apr '07

Full_Name: Hallvard B Furuseth Version: HEAD OS: Linux URL: Submission from: (NULL) (129.240.202.105) Submitted by: hallvard slapadd uses slap_op_mutex uninitialized in operation.c:slap_op_time() >>>>> Starting test049-sync-config ... running defines.sh == thr_debug: Leaked 1 mutexes. == Starting producer slapd on TCP/IP port 9011... thr_debug.c:432: ldap_pvt_thread_mutex_lock error: usage->magic is 0 ./scripts/test049-sync-config: line 47: 6207 Aborted (core dumped) $SLAPADD -F $CFPRO -n 0 -l $CONFLDIF Using ldapsearch to check that producer slapd is running... (gdb) backtrace ... #3 0x0818efbd in check_usage (usage=0x8253018, msg=0x6 "") at thr_debug.c:432 #4 0x08190779 in ldap_pvt_thread_mutex_lock (mutex=0x8253000) at thr_debug.c:978 #5 0x0809150e in slap_op_time (t=0xbfffd3a0, nop=0xbfffd3a4) at operation.c:125 #6 0x08080f54 in connection_fake_init2 (conn=0xbfffd548, op=0xbfffd398, ctx=0x8275160, newmem=0) at connection.c:2053 #7 0x08080db1 in connection_fake_init (conn=0x0, op=0x0, ctx=0x0) at connection.c:2000 #8 0x0806e870 in config_setup_ldif (be=0x82cb1e8, dir=0x8277008 "/usit/bombur/site/hbf/scratch/ldap/ldap/HEAD/tests/testrun/pro/slapd.d", readit=1) at bconfig.c:3451 #9 0x0806ec91 in read_config (fname=0x0, dir=0x8277008 "/usit/bombur/site/hbf/scratch/ldap/ldap/HEAD/tests/testrun/pro/slapd.d") at bconfig.c:3574 #10 0x080e04bc in slap_tool_init (progname=0x81cef70 "slapadd", tool=1, argc=10, argv=0xbfffee54) at slapcommon.c:510 #11 0x080de993 in slapadd (argc=0, argv=0x0) at slapadd.c:70 #12 0x08066142 in main (argc=10, argv=0xbfffee54) at main.c:645 (gdb) frame 3 #3 0x0818efbd in check_usage (usage=0x8253018, msg=0x6 "") at thr_debug.c:432 432 ERROR( usage->magic, msg ); (gdb) print *usage $2 = {magic = 0, self = 0, mem = {ptr = 0x0, num = 0}, state = 0} Configuration: CPPFLAGS='-DLDAP_REL_ENG -DLDAP_THREAD_DEBUG -DLDAP_RDWR_DEBUG' \ ./configure --prefix=/hbf/scratch/ldap/install/head \ --enable-crypt --enable-dynacl --enable-aci --enable-lmpasswd \ --enable-spasswd --enable-modules --enable-rlookups \ --enable-slapi --enable-slp --enable-wrappers \ --enable-backends --disable-sql --enable-overlays Any hope of making the tools and slapd go through the same init/destroy code in main(), maybe by making the server just another "tool"? Seems to me the only hope of making bugs like this keep popping up...

1 0

(ITS#4910) mirrormode prevents syncrepl engine from working
by ali.pouya＠free.fr 04 Apr '07

04 Apr '07

Full_Name: Ali Pouya Version: 2.4.4alpha OS: URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (82.227.144.113) mirrormode is essential to my new directory project, so I resubmit this issue. I mounted two servers A and B with openldap 2.4.4alpha. If I set "mirrormode on" in the config file of B it does not receive any syncrepl data from A. If I comment out the line and restart slapd on B, then it receives all outstanding modifications done on A. I think that mirrormode prevents syncrepl engine from working. I can provide any information required. Best regards Ali

1 0

(ITS#4909
by ali.pouya＠free.fr 04 Apr '07

04 Apr '07

I would like to bring a precision for ITS 4909. Contrarily to what I wrote in the problem description , the replica DOES NOT upload the written data to the master. Best regards Ali

1 0

Re: (ITS#4907) Syncrepl consumer failing to perform deletes
by hyc＠symas.com 03 Apr '07

03 Apr '07

Sean Burford wrote: > Hi, > > On 4/2/07, *Howard Chu* <hyc(a)symas.com <mailto:hyc@symas.com>> wrote: > > > I am attempting to set up syncrepl between two OpenLDAP 2.3.32 > servers. Adds > > and Modifies are replicated from the provider to the consumer, > but deletes > > result in thousands of "unknown filter type 136644788" messages > in the consumer > > log and no deletion. Commenting out the syncprov-sessionlog > directive works > > around the issue. > > I don't see this with 2.3.32 on Linux 2.6.18. You'll probably need to > trace the activity with gdb to see what's wrong with the filter. > > > Right you are. The patch for ITS#4638 (rejected here: > http://www.openldap.org/lists/openldap-bugs/200608/msg00043.html) > introduced the bug. I'll send in a corrected patch once it has been QA'd. The log says that ITS#4638 was already fixed in 2.3.32. Why are you still using that particular patch, given that an alternate solution is already present in the release? I also see that in RE23 we had one more patch to fix some interaction between slapo-rwm and back-meta for filter processing. I suggest you test against the current RE23 code. I expect to push 2.3.35 out pretty soon. -- -- 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#4907) Syncrepl consumer failing to perform deletes
by unix.gurus＠gmail.com 03 Apr '07

03 Apr '07

------=_Part_14849_31495008.1175634207921 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, On 4/2/07, Howard Chu <hyc(a)symas.com> wrote: > > > I am attempting to set up syncrepl between two OpenLDAP 2.3.32servers. Adds > > and Modifies are replicated from the provider to the consumer, but > deletes > > result in thousands of "unknown filter type 136644788" messages in the > consumer > > log and no deletion. Commenting out the syncprov-sessionlog directive > works > > around the issue. > > I don't see this with 2.3.32 on Linux 2.6.18. You'll probably need to > trace the activity with gdb to see what's wrong with the filter. Right you are. The patch for ITS#4638 (rejected here: http://www.openldap.org/lists/openldap-bugs/200608/msg00043.html) introduced the bug. I'll send in a corrected patch once it has been QA'd. -- Thanks, Sean Burford ------=_Part_14849_31495008.1175634207921 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi,<br><br><div><span class="gmail_quote">On 4/2/07, <b class="gmail_sendername">Howard Chu</b> <<a href="mailto:hyc@symas.com">hyc(a)symas.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> > I am attempting to set up syncrepl between two OpenLDAP 2.3.32 servers.  Adds<br>> and Modifies are replicated from the provider to the consumer, but deletes<br>> result in thousands of "unknown filter type 136644788" messages in the consumer <br>> log and no deletion.  Commenting out the syncprov-sessionlog directive works<br>> around the issue.<br><br>I don't see this with 2.3.32 on Linux 2.6.18. You'll probably need to<br>trace the activity with gdb to see what's wrong with the filter. </blockquote><div><br> Right you are.  The patch for ITS#4638 (rejected here: <a href="http://www.openldap.org/lists/openldap-bugs/200608/msg00043.html">http://www.openldap.org/lists/openldap-bugs/200608/msg00043.html</a>) introduced the bug.  I'll send in a corrected patch once it has been QA'd. <br><br></div></div>-- <br>Thanks,<br>Sean Burford ------=_Part_14849_31495008.1175634207921--

1 0

RE: (ITS#4908) bug ldapsearch.c
by Dale.Moore＠cs.cmu.edu 03 Apr '07

03 Apr '07

> The bug is still present. It is a consequence of naively assuming that > argv[] is NULL terminated, which is not required to be, AFAIK. My spec for ANSI C (ISO/IEC 9899:1990 (E)) says on section 5.1.2.2.1 (page 7) - argv[argc] shall be a null pointer. Maybe my C spec is a little out of date.

1 0

Re: (ITS#4908) bug ldapsearch.c
by h.b.furuseth＠usit.uio.no 03 Apr '07

03 Apr '07

ando(a)sys-net.it writes: > The bug is still present. It is a consequence of naively assuming that > argv[] is NULL terminated, which is not required to be, AFAIK. Yes it is. The C standard's "Program Startup" section requires argv[argc] == NULL. Though I suppose some systems may break it. And the standard does allow argc == 0 (and thus argv[0] == NULL), maybe some OpenLDAP code mishandles that. -- Regards, Hallvard

1 0

Re: (ITS#4908) bug ldapsearch.c
by ando＠sys-net.it 03 Apr '07

03 Apr '07

quanah(a)stanford.edu wrote: > --On Tuesday, April 03, 2007 3:01 PM +0000 buwalgui(a)etu.univ-rouen.fr wrote: > >> Full_Name: Guillaume BUWALDA >> Version: 2.2.3 >> OS: Linux ubuntu > > > The current released version of OpenLDAP is 2.3.34. OpenLDAP 2.2.x is a > historic release. As such, bugs against it will not be investigated. If > you can reproduce this issue with the current release, then please follow > up. The bug is still present. It is a consequence of naively assuming that argv[] is NULL terminated, which is not required to be, AFAIK. 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#4908) bug ldapsearch.c
by quanah＠stanford.edu 03 Apr '07

03 Apr '07

--On Tuesday, April 03, 2007 3:01 PM +0000 buwalgui(a)etu.univ-rouen.fr wrote: > Full_Name: Guillaume BUWALDA > Version: 2.2.3 > OS: Linux ubuntu The current released version of OpenLDAP is 2.3.34. OpenLDAP 2.2.x is a historic release. As such, bugs against it will not be investigated. If you can reproduce this issue with the current release, then please follow up. Regards, Quanah -- Quanah Gibson-Mount Senior Systems Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html

1 0

(ITS#4908) bug ldapsearch.c
by buwalgui＠etu.univ-rouen.fr 03 Apr '07

03 Apr '07

Full_Name: Guillaume BUWALDA Version: 2.2.3 OS: Linux ubuntu URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (62.23.181.151) Hello, I do not know where I can send this message, so I send it to you... I found a little error in the source file client/tools/ldapsearch.c . gdb give me this bt: [Cacher les citations] Program received signal SIGSEGV, Segmentation fault. > 0xb7eb3c53 in strlen () from /lib/tls/i686/cmov/libc.so.6 (gdb) bt > #0 0xb7eb3c53 in strlen () from /lib/tls/i686/cmov/libc.so.6 > #1 0xb7e40031 in ber_put_string () from /usr/lib/liblber.so.2 > #2 0xb7e40321 in ber_printf () from /usr/lib/liblber.so.2 > #3 0xb7f8a376 in ldap_build_search_req () from /usr/lib/libldap_r.so.2 > #4 0xb7f8a7fe in ldap_search_ext () from /usr/lib/libldap_r.so.2 when it calls the function ldap_search_ext(). I think the error comes from then "attrs" parameters of this function. At line 611 of the file: > if ( argv[optind] != NULL ) { > attrs = &argv[optind]; > } You may put the last element of the array at NULL. I did this and it work. I hope this message will help you, and I'm sorry for my very bad english... lol Good Luck Guillaume BUWALDA

1 0

Re: (ITS#4879) URL parse/unparse troubles
by h.b.furuseth＠usit.uio.no 03 Apr '07

03 Apr '07

Howard Chu writes: >> The url.c Novell kludge does not work (for the example URL). >> If the bug is old and nobody has complained, maybe it should be >> removed. If it's fixed instead, note that the code looks like >> it'll handle Novell URLs with '/' in components after hostport: >> ldap_url_parse_ext() does strchr( url, '/' ) very early to find >> the end of the hostport. > > Hm, I think I see what you mean, but I don't see what to do about that. I think we can just replace strchr(,'/') with strpbrk(,"/?") or strcspn and take it from there. And require '?' in ldapi filenames to be URL-escaped, if they are not already. Thank you, much easier to see now the rest of the mess is cleaned up:-) >> Converting "%00" to char* should return an error, since the char* >> will not match the source URL: >> >> ldapi://a%00b/cn=d%00e -> host "a", DN "cn=d" -> >> ldapi://a/cn=d??base > > I've left this alone for now. We can make ldap_pvt_hex_unescape() return success/failure instead of void (and the output URL would be undefined). At the same time also reject bad %escapes - see that function's comment * FIXME: what if '%' is followed * by non-hexpair chars? >> ================ >> >> The RFCs 4516/2255 hostport part has grammar [host [":" port]], >> but ldap_url_desc2str() produces [host][":" port]. >> >> ldap:// -> host NULL, port 389 -> >> ldap://:389/??base >> >> That's OK as an ldap_url_parse() OpenLDAP extension, but not as >> ldap_url_desc2str() output given to non-OpenLDAP applications. > > This is a mess. The ldap: scheme definition has always been broken, and > it certainly does not conform to the basic URI syntax in RFC3986 section > 3. In particular, RFC3986 forbids a URI from containing "//" when the > authority component is absent. Would it help to produce ldap://0:389/? Helps the syntax, but I don't know if host 0 or 0.0.0.0 for INADDR_ANY is OK or just another unportable hack. > Looks like RFC4516 should not have been approved in its current state. I'd say RFCs2255 should not have been, but RFC4516 should since it was too late; it didn't introduce any new bugs. -- Regards, Hallvard

1 0

Re: (ITS#4907) Syncrepl consumer failing to perform deletes
by hyc＠symas.com 02 Apr '07

02 Apr '07

unix.gurus(a)gmail.com wrote: > Full_Name: Sean Burford > Version: 2.3.32 > OS: Linux 2.4.20 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (65.57.245.11) > > > I am attempting to set up syncrepl between two OpenLDAP 2.3.32 servers. Adds > and Modifies are replicated from the provider to the consumer, but deletes > result in thousands of "unknown filter type 136644788" messages in the consumer > log and no deletion. Commenting out the syncprov-sessionlog directive works > around the issue. I don't see this with 2.3.32 on Linux 2.6.18. You'll probably need to trace the activity with gdb to see what's wrong with the filter. -- -- 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#4879) URL parse/unparse troubles
by hyc＠symas.com 02 Apr '07

02 Apr '07

h.b.furuseth(a)usit.uio.no wrote: > Full_Name: Hallvard B Furuseth > Version: HEAD > OS: Linux > URL: > Submission from: (NULL) (129.240.202.105) > Submitted by: hallvard > > > Here are some URLs parsing/building bugs in libldap/url.c. > Some may be design bugs. Possibly some fixes will need backwards > bug-compatibility. > > I show URLs converted from string to LDAPURLDesc format with > ldap_url_parse(), back to string format with ldap_url_desc2str() > when the result differs from the original, back to LDAPURLDesc... > > ================ > > The url.c Novell kludge does not work (for the example URL). > If the bug is old and nobody has complained, maybe it should be > removed. If it's fixed instead, note that the code looks like > it'll handle Novell URLs with '/' in components after hostport: > ldap_url_parse_ext() does strchr( url, '/' ) very early to find > the end of the hostport. Hm, I think I see what you mean, but I don't see what to do about that. > ldap://111.222.333.444:389??cn=abc,o=company -> > error 5 (LDAP_URL_ERR_BADURL) This now works. > > Example URL without port number: > > ldap://111.222.333.444??cn=abc,o=company -> > host "111.222.333.444??cn=abc,o=company", DN NULL -> > ldap://111.222.333.444??cn=abc,o=company:389/??base This now works. > > ================ > > ldap_url_desc2str() outputs IPv6 host addresses as "addr" rather > than "[addr]". (LDAPURLDesc does not contain the '[]'s in > .lud_host, nor any flag which says it's an IPv6 host address). > > I don't know the syntax of such addresses, but I seem to remember > they contains ':'s. If so the parser could fail if an IPv6 > address does not contains ':', and the URL builder could test for > ':' to determine if there should be [] around the host part. This now works. > > Also, what does stuff between the ']' and ':port' mean? > Should anything be allowed there? > > ldap://[::1]what's this:222/ -> host "::1", port 222 -> This is now correctly rejected. > ldap://::1:222/??base -> error 5 (LDAP_URL_ERR_BADURL) > > ================ > > Converting "%00" to char* should return an error, since the char* > will not match the source URL: > > ldapi://a%00b/cn=d%00e -> host "a", DN "cn=d" -> > ldapi://a/cn=d??base I've left this alone for now. > ================ > > The RFCs 4516/2255 hostport part has grammar [host [":" port]], > but ldap_url_desc2str() produces [host][":" port]. > > ldap:// -> host NULL, port 389 -> > ldap://:389/??base > > That's OK as an ldap_url_parse() OpenLDAP extension, but not as > ldap_url_desc2str() output given to non-OpenLDAP applications. This is a mess. The ldap: scheme definition has always been broken, and it certainly does not conform to the basic URI syntax in RFC3986 section 3. In particular, RFC3986 forbids a URI from containing "//" when the authority component is absent. Looks like RFC4516 should not have been approved in its current state. > ================ > > While I'm writing, I wonder if OpenLDAP 2.4 could omit defaults > and final "?"s from the ldap_url_desc2str() output. E.g. ldap:// > would become ldap:// and not ldap://:389/??base. But maybe we get > into trouble if ldap.conf has another port or something. I thought about changing this, but left it alone for now. Agreed, the interaction with ldap.conf isn't clear. > ================ > > ldapi URL (un)parsing has several problems: > > ldap_url_parse() always treats ':' as a host:port separator. > Thus one can produce an ldapi LDAPURLDesc with a meaningless port. > However ldap_url_desc2str() does not URL-escape ':', and it also > takes port!=0 to mean it is not an ldapi URL and needs no > '/'-escaping. Similarly filenames with initial '[' do not work. > > ldapi://%2Ftmp%2Ffoo%3A222/ -> host "/tmp/foo:222" (correct) -> > ldapi://%2Ftmp%2Ffoo:222/??base -> host "/tmp/foo", port 222 -> > ldapi:///tmp/foo:222/??base -> host NULL, DN "tmp/foo:222/" > > ldapi://%2Ftmp%2Ffoo:000/ -> host "/tmp/foo" -> > ldapi://%2Ftmp%2Ffoo/??base > > ldapi://%2Ftmp%2Ffoo:bar/ -> error 5 (LDAP_URL_ERR_BADURL) These are all fixed. Note that the "ldapi:///tmp/foo:222/" case simply means an ldapi:// URL with a DN of "tmp/foo:222/" which is legal in a URL parsing sense, even though DN validation would reject it. > > ==== > > The current implementation would handle some non-Unix ldapi > filenames wrong. (They'll need well-defined URL-escaping rules > if they get implemented, so it might as well be fixed now.) Of > course these can also be strange Unix relative filenames... > > Windows-like filenames: > > ldapi://C%3A%2Fldapi/ -> host "C:/ldapi" -> > ldapi://C:%2Fldapi/??base -> error 5 (LDAP_URL_ERR_BADURL) > > Tops-20-like filenames resemble IPv6 addresses (not that I expect > to port OpenLDAP to Tops-20:-) > > ldapi://[ldap.var.run]ldapi/ -> host "ldap.var.run" -> > ldapi://ldap.var.run/??base > > URL-escaping the '[' and ']' does not help; the '[' is lost: > > ldapi://%5Bldap.var.run%5Dldapi/ -> host "ldap.var.run]ldapi" -> > ldapi://ldap.var.run%5Dldapi/??base > These are all fixed. -- -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs