- openldap-bugs - openldap.org

Re: (ITS#6325) test054: test failed - producer and consumer databases differ
by hyc＠symas.com 15 Nov '09

15 Nov '09

hyc(a)symas.com wrote: > michael(a)stroeder.com wrote: >> Download testrun/ here: >> >> http://www.stroeder.com/temp/openldap/its6325-test054-testrun.tar.gz > > It's certainly a mystery. The *.flt shows that an entry is missing on the > slave. The slapd.1.log shows that the provider sent the entry. The slapd.4.log > shows that the consumer received the entry and ignored it. (See slapd.4.log > line 3307-3313. Compare with the previously received entry, lines 3161-3169.) > > The most puzzling part is that every code path in the consumer that rejects an > entry logs an error message, and there is no error message in the log file. > Without any means to reproduce this there's not much we can do. Setting a > higher debug level might be useful, but any error messages in this path should > have shown up regardless. The same problem is in your ITS#6126 logs. The entry was received on the consumer but skipped without any error message. I see now, the entry was skipped because its CSN was too old. (And that CSN too old message is only logged with SYNC debug is enabled.) This should be fixed by the patch for ITS#6346. It was also suggested that we should only reject mods if their CSN is actually older than the target entry's CSN. That's still a possibility if the current patch is insufficient. -- -- 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#6200) slapd crashes under load w/ syncrepl
by hyc＠symas.com 15 Nov '09

15 Nov '09

joacim.breiler(a)hgo.se wrote: > Thanks for your fast replies! The 'make install STRIP=""' did the trick. > > I ran the server for about a week with no segfaults, then I decided that > I couldn't wait for it any longer. So I connected to the server using an > LDAP browser, and then after about ten minutes it segfaulted. So to > reproduce I need one connection that is reading/updating/creating > entries. And one connection that does an occasional read, otherwise the > server will keep on running. > > The traceback from gdb gives: This trace looks like the problem fixed in ITS#6335. The fix is in CVS HEAD and RE24 (2.4.20 pre-release). > > 0x00007f96c3fc00ad in syncprov_op_mod (op=0x7f9688000ac0, rs=0x44688c80) > at syncprov.c:1970 > 1970 for ( m2 = mt->mt_mods; m2->mi_next != mi; > (gdb) where > #0 0x00007f96c3fc00ad in syncprov_op_mod (op=0x7f9688000ac0, > rs=0x44688c80) at syncprov.c:1970 > #1 0x00000000004c438a in overlay_op_walk (op=0x7f9688000ac0, > rs=0x44688c80, which=op_modify, oi=0x12293c0, on=0x12295a0) at > backover.c:659 > #2 0x00000000004c4667 in over_op_func (op=0x7f9688000ac0, > rs=0x44688c80, which=op_modify) at backover.c:721 > #3 0x00000000004c47ac in over_op_modify (op=0x7f9688000ac0, > rs=0x44688c80) at backover.c:760 > #4 0x000000000045bb21 in fe_op_modify (op=0x7f9688000ac0, > rs=0x44688c80) at modify.c:301 > #5 0x000000000045b430 in do_modify (op=0x7f9688000ac0, rs=0x44688c80) > at modify.c:175 > #6 0x000000000043c3ec in connection_operation (ctx=0x44688de0, > arg_v=0x7f9688000ac0) at connection.c:1123 > #7 0x000000000043c975 in connection_read_thread (ctx=0x44688de0, > argv=0x17) at connection.c:1259 > #8 0x0000000000525193 in ldap_int_thread_pool_wrapper (xpool=0x1190290) > at tpool.c:685 > #9 0x00007f96c49613ea in start_thread () from /lib/libpthread.so.0 > #10 0x00007f96c44b9cbd in clone () from /lib/libc.so.6 > #11 0x0000000000000000 in ?? () > > /J -- -- 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#6325) test054: test failed - producer and consumer databases differ
by hyc＠symas.com 15 Nov '09

15 Nov '09

michael(a)stroeder.com wrote: > Download testrun/ here: > > http://www.stroeder.com/temp/openldap/its6325-test054-testrun.tar.gz It's certainly a mystery. The *.flt shows that an entry is missing on the slave. The slapd.1.log shows that the provider sent the entry. The slapd.4.log shows that the consumer received the entry and ignored it. (See slapd.4.log line 3307-3313. Compare with the previously received entry, lines 3161-3169.) The most puzzling part is that every code path in the consumer that rejects an entry logs an error message, and there is no error message in the log file. Without any means to reproduce this there's not much we can do. Setting a higher debug level might be useful, but any error messages in this path should have shown up regardless. -- -- 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: RE : (ITS#6367) syncprov ... changed by peer, ignored
by hyc＠symas.com 15 Nov '09

15 Nov '09

CHIROSSEL Olivier wrote: > sorry for this > > the url is ok now Thanks. This is now fixed in HEAD. > > Cdt, > > Olivier > ________________________________________ > De : Howard Chu [hyc(a)symas.com] > Date d'envoi : vendredi 13 novembre 2009 23:33 > À : CHIROSSEL Olivier > Cc : openldap-its(a)openldap.org > Objet : Re: (ITS#6367) syncprov ... changed by peer, ignored > > olivier.chirossel(a)sfr.com wrote: >> Full_Name: olivier chirossel >> Version: 2.4.17 and 2.4.19 >> OS: linux >> URL: http://86.64.145.174:8080/ >> Submission from: (NULL) (62.39.9.251) >> >> >> in refreshend persist mode, the replication is incorrect for an entry which be >> delete/add after master restart and before the reconnection of the slave. > >> 2) master set up >> >> on /etc/openldap tar xvf slapd_master.tar (get on the url ) > > The URL you provided always times out for me, so I've been unable to set up > this test. > -- -- 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#6362) slapd 2.4.19 Segmentation fault under load
by hyc＠symas.com 15 Nov '09

15 Nov '09

alexs(a)ulgsm.ru wrote: > Full_Name: Aleksey > Version: 2.4.19 > OS: Freebsd7.2 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (93.93.136.26) > > > Openldap 2.4.19 installed from freebsd ports. All configs in defauls > Freebsd 7.2 amd64 > Slapd built with the "-g" flag and install with the make install STRIP="" > > Used backends db46-4.6.21.4, db47-4.7.25.4 latest from freebsd ports. > In slapd config added using hdb as backend and indexes. > > Testing database consist of 1000 users accounts with minimum attributes. > > On stress test load slapd Segmentation fault in 10-30 sec. Looks like you've had a stack overrun. The "be" parameter should be the same in your frame 0 and frame 1. > #gdb /usr/local/libexec/slapd > (gdb) run -d 0 > Starting program: /usr/local/libexec/slapd -d 0 > [New LWP 100311] > [New Thread 0x801a020b0 (LWP 100311)] > [New Thread 0x801a02880 (LWP 100073)] > [New Thread 0x8034040b0 (LWP 100076)] > [New Thread 0x803404240 (LWP 100077)] > [New Thread 0x8034043d0 (LWP 100078)] > [New Thread 0x803404560 (LWP 100116)] > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x803404560 (LWP 100116)] > 0x0000000802d5aa4b in hdb_idl_fetch_key (be=Error accessing memory address > 0x7ffffd9f9f38: Bad s. > ) at idl.c:511 > 511 { > (gdb) > (gdb) > (gdb) where > #0 0x0000000802d5aa4b in hdb_idl_fetch_key (be=Error accessing memory > address 0x7ffffd9f9f38: dress. > ) at idl.c:511 > #1 0x0000000802d50dc5 in hdb_key_read (be=0x801a853d0, db=0x803519800, > txn=0x80352b040, k=0x8069005 > 70, ids=0x806a00000, saved_cursor=0x0, get_flag=0) at key.c:50 > #2 0x0000000802d5363c in equality_candidates (op=0x803521000, rtxn=0x80352b040, > ava=0x7ffffda7a4f0, > ids=0x806c00000, tmp=0x806a00000) at filterindex.c:788 > #3 0x0000000802d51d10 in hdb_filter_candidates (op=0x803521000, > rtxn=0x80352b040, f=0x7ffffda7a550, > ids=0x806c00000, tmp=0x806a00000, stack=0x806d00000) at filterindex.c:154 > #4 0x0000000802d5297f in list_candidates (op=0x803521000, rtxn=0x80352b040, > flist=0x7ffffda7a5 f > type=161, ids=0x806b00000, tmp=0x806a00000, save=0x806c00000) at > filterindex.c:581 > #5 0x0000000802d5229c in hdb_filter_candidates (op=0x803521000, > rtxn=0x80352b040, f=0x7ffffda7a530, > ids=0x806b00000, tmp=0x806a00000, stack=0x806c00000) at filterindex.c:204 > #6 0x0000000802d5297f in list_candidates (op=0x803521000, rtxn=0x80352b040, > flist=0x7ffffda7a5 f > type=160, ids=0x7ffffdafa760, tmp=0x806a00000, save=0x806b00000) at > filterindex.c:581 > #7 0x0000000802d521e4 in hdb_filter_candidates (op=0x803521000, > rtxn=0x80352b040, f=0x7ffffda7a570, > ids=0x7ffffdafa760, tmp=0x806a00000, stack=0x806b00000) at filterindex.c: > #8 0x0000000802d4dca9 in search_candidates (op=0x803521000, rs=0x7ffffdbfab30, > e=0x7ffffda7a71 tx > n=0x80352b040, ids=0x7ffffdafa760, scopes=0x7ffffda7a760) at search.c:1206 > #9 0x0000000802d4befa in hdb_search (op=0x803521000, rs=0x7ffffdbfab30) at > search.c:586 > #10 0x0000000000439bb5 in fe_op_search (op=0x803521000, rs=0x7ffffdbfab30) at > search.c:366 > #11 0x0000000000439520 in do_search (op=0x803521000, rs=0x7ffffdbfab30) at > search.c:217 > #12 0x000000000043613d in connection_operation (ctx=0x7ffffdbfac70, > arg_v=0x803521000) at connection > .c:1123 > #13 0x00000000004366d9 in connection_read_thread (ctx=0x7ffffdbfac70, argv=0x12) > at connection.c:125 > 9 > #14 0x0000000800797052 in ldap_int_thread_pool_wrapper () from > /usr/local/lib/libldap_r-2.4.so. > #15 0x000000080164b4d1 in pthread_getprio () from /lib/libthr.so.3 > #16 0x0000000000000000 in ?? () > Error accessing memory address 0x7ffffdbfb000: Bad address. -- -- 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#6381) connection_fake_init() from db_open() is unsafe
by hyc＠OpenLDAP.org 15 Nov '09

15 Nov '09

Full_Name: Howard Chu Version: 2.4 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (76.91.220.157) Submitted by: hyc Originally the db_open() handlers only ran from slapd's main context, at startup time before threading was active. But with back-config, backends and overlays can be added at runtime and the db_open() handler then runs in a back-config operation thread. If a db_open handler calls connection_fake_init() using its current thread context, it will get the current sl_malloc memory context as well, and reset it to zero. Any sl_mallocs called up to that point will be forgotten and they'll be overwritten by subsequent calls in that thread. We never saw any problems with this prior to ITS#6380, because the prior mallocs tended to be higher up in the sl_malloc heap. So even though the heap was reset, the new mallocs didn't collide with the old ones. This is already fixed in HEAD: back-sql/init.c, back-monitor/init.c, and overlays/{dds.c, pcache.c, syncprov.c}

1 0

(ITS#6380) slap_sl_free is too lazy
by hyc＠OpenLDAP.org 15 Nov '09

15 Nov '09

Full_Name: Howard Chu Version: 2.4 OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (76.91.220.157) Submitted by: hyc slap_sl_free() would only reclaim memory if you were freeing the last allocated block. If you wanted to free a chain of alloc'd memory you would have to free them in the exact reverse order of allocation. Calling slap_sl_free() out of order would be a no-op. This was OK most of the time because a single operation would seldom live long enough to use much memory. But for long-lived tasks (like syncrepl or syncprov) it would often run out and allocs would fallback to ch_malloc. sl_malloc.c in HEAD has been changed to mark freed blocks no matter what order they're freed in. It still only reclaims from the last block forward, but it's more effective now.

1 0

Re: (ITS#6377) test058-syncrepl-asymmetric failed for bdb (exit 3)
by hyc＠symas.com 15 Nov '09

15 Nov '09

Michael Ströder wrote: > hyc(a)symas.com wrote: >> hyc(a)symas.com wrote: >>> I'm seeing the same problem here. Still haven't identified the cause, looking... >>> >> Fixed. > > HEAD now has a different issue. Is this related to this fix? Now fixed. >>>>>> Starting test003-search for bdb... -- -- 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#6377) test058-syncrepl-asymmetric failed for bdb (exit 3)
by hyc＠symas.com 15 Nov '09

15 Nov '09

Michael Ströder wrote: > hyc(a)symas.com wrote: >> hyc(a)symas.com wrote: >>> I'm seeing the same problem here. Still haven't identified the cause, looking... >>> >> Fixed. > > HEAD now has a different issue. Is this related to this fix? Since test003 doesn't involve sync replication in any way, no. This ITS is fixed, closing. File a separate ITS for different issues... -- -- 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#6377) test058-syncrepl-asymmetric failed for bdb (exit 3)
by michael＠stroeder.com 15 Nov '09

15 Nov '09

hyc(a)symas.com wrote: > hyc(a)symas.com wrote: >> I'm seeing the same problem here. Still haven't identified the cause, looking... >> > Fixed. HEAD now has a different issue. Is this related to this fix? Ciao, Michael. >>>>> Starting test003-search for bdb... running defines.sh Running slapadd to build slapd database... Running slapindex to index slapd database... Starting slapd on TCP/IP port 9011... Testing slapd searching... Testing exact searching... Testing approximate searching... Testing OR searching... *** glibc detected *** /usr/src/michael/openldap/HEAD/openldap/servers/slapd/.libs/lt-slapd: free(): invalid pointer: 0x000000000 097fb28 *** ======= Backtrace: ========= /lib64/libc.so.6[0x2b2f801d5c76] /lib64/libc.so.6(cfree+0x6c)[0x2b2f801da96c] /usr/src/michael/openldap/HEAD/openldap/libraries/liblber/.libs/liblber-2-devel.so.0(ber_bvarray_free_x+0x63)[0x2b2f7e30f273] ../servers/slapd/back-bdb/.libs/back_bdb-2-devel.so.0(bdb_filter_candidates+0x1752)[0x2b2f82889842] ../servers/slapd/back-bdb/.libs/back_bdb-2-devel.so.0[0x2b2f82889f07] ../servers/slapd/back-bdb/.libs/back_bdb-2-devel.so.0(bdb_filter_candidates+0x5aa)[0x2b2f8288869a] ../servers/slapd/back-bdb/.libs/back_bdb-2-devel.so.0[0x2b2f82889f07] ../servers/slapd/back-bdb/.libs/back_bdb-2-devel.so.0(bdb_filter_candidates+0x5aa)[0x2b2f8288869a] ../servers/slapd/back-bdb/.libs/back_bdb-2-devel.so.0[0x2b2f82889f07] ../servers/slapd/back-bdb/.libs/back_bdb-2-devel.so.0(bdb_filter_candidates+0x79a)[0x2b2f8288888a] ../servers/slapd/back-bdb/.libs/back_bdb-2-devel.so.0(bdb_search+0xe96)[0x2b2f82882cf6] /usr/src/michael/openldap/HEAD/openldap/servers/slapd/.libs/lt-slapd(fe_op_search+0x259)[0x436c29] /usr/src/michael/openldap/HEAD/openldap/servers/slapd/.libs/lt-slapd(do_search+0x6ac)[0x43743c] /usr/src/michael/openldap/HEAD/openldap/servers/slapd/.libs/lt-slapd[0x434a01] /usr/src/michael/openldap/HEAD/openldap/servers/slapd/.libs/lt-slapd[0x435285] /usr/src/michael/openldap/HEAD/openldap/libraries/libldap_r/.libs/libldap_r-2-devel.so.0[0x2b2f7e0cb1b8] /lib64/libpthread.so.0[0x2b2f7ecdc65d] /lib64/libc.so.6(clone+0x6d)[0x2b2f8023414d] ======= Memory map: ======== 00400000-00529000 r-xp 00000000 08:05 524931 /usr/src/michael/openldap/HEAD/openldap/servers/slapd/.l ibs/lt-slapd 00728000-00729000 r--p 00128000 08:05 524931 /usr/src/michael/openldap/HEAD/openldap/servers/slapd/.l ibs/lt-slapd 00729000-00730000 rw-p 00129000 08:05 524931 /usr/src/michael/openldap/HEAD/openldap/servers/slapd/.l ibs/lt-slapd 00730000-00aa2000 rw-p 00000000 00:00 0 [heap] 2b2f7de9a000-2b2f7deb8000 r-xp 00000000 08:05 145546 /lib64/ld-2.10.1.so 2b2f7deb8000-2b2f7deba000 rw-p 00000000 00:00 0 2b2f7e0b7000-2b2f7e0b8000 r--p 0001d000 08:05 145546 /lib64/ld-2.10.1.so 2b2f7e0b8000-2b2f7e0b9000 rw-p 0001e000 08:05 145546 /lib64/ld-2.10.1.so 2b2f7e0b9000-2b2f7e102000 r-xp 00000000 08:05 524531 /usr/src/michael/openldap/HEAD/openldap/libraries/liblda p_r/.libs/libldap_r-2-devel.so.0.0.0 2b2f7e102000-2b2f7e301000 ---p 00049000 08:05 524531 /usr/src/michael/openldap/HEAD/openldap/libraries/liblda p_r/.libs/libldap_r-2-devel.so.0.0.0 2b2f7e301000-2b2f7e302000 r--p 00048000 08:05 524531 /usr/src/michael/openldap/HEAD/openldap/libraries/liblda p_r/.libs/libldap_r-2-devel.so.0.0.0 2b2f7e302000-2b2f7e304000 rw-p 00049000 08:05 524531 /usr/src/michael/openldap/HEAD/openldap/libraries/liblda p_r/.libs/libldap_r-2-devel.so.0.0.0 2b2f7e304000-2b2f7e307000 rw-p 00000000 00:00 0 2b2f7e307000-2b2f7e314000 r-xp 00000000 08:05 524374 /usr/src/michael/openldap/HEAD/openldap/libraries/liblbe r/.libs/liblber-2-devel.so.0.0.0 2b2f7e314000-2b2f7e513000 ---p 0000d000 08:05 524374 /usr/src/michael/openldap/HEAD/openldap/libraries/liblbe r/.libs/liblber-2-devel.so.0.0.0 2b2f7e513000-2b2f7e514000 r--p 0000c000 08:05 524374 /usr/src/michael/openldap/HEAD/openldap/libraries/liblbe r/.libs/liblber-2-devel.so.0.0.0 2b2f7e514000-2b2f7e515000 rw-p 0000d000 08:05 524374 /usr/src/michael/openldap/HEAD/openldap/libraries/liblbe r/.libs/liblber-2-devel.so.0.0.0 2b2f7e531000-2b2f7e532000 rw-p 00000000 00:00 0 2b2f7e532000-2b2f7e535000 r-xp 00000000 08:05 166857 /lib64/libuuid.so.1.3.0 2b2f7e535000-2b2f7e735000 ---p 00003000 08:05 166857 /lib64/libuuid.so.1.3.0 2b2f7e735000-2b2f7e736000 r--p 00003000 08:05 166857 /lib64/libuuid.so.1.3.0 2b2f7e736000-2b2f7e737000 rw-p 00004000 08:05 166857 /lib64/libuuid.so.1.3.0 2b2f7e737000-2b2f7e866000 r-xp 00000000 08:05 198841 /usr/lib64/libdb-4.5.so 2b2f7e866000-2b2f7ea65000 ---p 0012f000 08:05 198841 /usr/lib64/libdb-4.5.so 2b2f7ea65000-2b2f7ea68000 r--p 0012e000 08:05 198841 /usr/lib64/libdb-4.5.so 2b2f7ea68000-2b2f7ea6b000 rw-p 00131000 08:05 198841 /usr/lib64/libdb-4.5.so 2b2f7ea6b000-2b2f7eacd000 r-xp 00000000 08:05 235428 /usr/lib64/libodbc.so.1.0.0 2b2f7eacd000-2b2f7eccc000 ---p 00062000 08:05 235428 /usr/lib64/libodbc.so.1.0.0 2b2f7eccc000-2b2f7eccd000 r--p 00061000 08:05 235428 /usr/lib64/libodbc.so.1.0.0 2b2f7eccd000-2b2f7ecd4000 rw-p 00062000 08:05 235428 /usr/lib64/libodbc.so.1.0.0 2b2f7ecd4000-2b2f7ecd6000 rw-p 00000000 00:00 0 2b2f7ecd6000-2b2f7ecec000 r-xp 00000000 08:05 156951 /lib64/libpthread-2.10.1.so 2b2f7ecec000-2b2f7eeec000 ---p 00016000 08:05 156951 /lib64/libpthread-2.10.1.so 2b2f7eeec000-2b2f7eeed000 r--p 00016000 08:05 156951 /lib64/libpthread-2.10.1.so 2b2f7eeed000-2b2f7eeee000 rw-p 00017000 08:05 156951 /lib64/libpthread-2.10.1.so 2b2f7eeee000-2b2f7eef2000 rw-p 00000000 00:00 0 2b2f7eef2000-2b2f7ef0a000 r-xp 00000000 08:05 173123 /usr/lib64/libslp.so.1.0.0 2b2f7ef0a000-2b2f7f109000 ---p 00018000 08:05 173123 /usr/lib64/libslp.so.1.0.0 2b2f7f109000-2b2f7f10a000 r--p 00017000 08:05 173123 /usr/lib64/libslp.so.1.0.0 2b2f7f10a000-2b2f7f10b000 rw-p 00018000 08:05 173123 /usr/lib64/libslp.so.1.0.0 2b2f7f10b000-2b2f7f124000 r-xp 00000000 08:05 185973 /usr/lib64/libsasl2.so.2.0.23 2b2f7f124000-2b2f7f323000 ---p 00019000 08:05 185973 /usr/lib64/libsasl2.so.2.0.23 2b2f7f323000-2b2f7f324000 r--p 00018000 08:05 185973 /usr/lib64/libsasl2.so.2.0.23 2b2f7f324000-2b2f7f325000 rw-p 00019000 08:05 185973 /usr/lib64/libsasl2.so.2.0.23./scripts/test003-search: l ine 93: 9220 Aborted (core dumped) $SLAPD -f $CONF1 -h $URI1 -d $LVL $TIMING > $LOG1 2>&1 ldapsearch failed (255)! ./scripts/test003-search: line 96: kill: (9220) - No such process >>>>> ./scripts/test003-search 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'

1 0

RE : (ITS#6367) syncprov ... changed by peer, ignored
by olivier.chirossel＠sfr.com 14 Nov '09

14 Nov '09

sorry for this the url is ok now Cdt, Olivier ________________________________________ De : Howard Chu [hyc(a)symas.com] Date d'envoi : vendredi 13 novembre 2009 23:33 =C0 : CHIROSSEL Olivier Cc : openldap-its(a)openldap.org Objet : Re: (ITS#6367) syncprov ... changed by peer, ignored olivier.chirossel(a)sfr.com wrote: > Full_Name: olivier chirossel > Version: 2.4.17 and 2.4.19 > OS: linux > URL: http://86.64.145.174:8080/ > Submission from: (NULL) (62.39.9.251) > > > in refreshend persist mode, the replication is incorrect for an entry whi= ch be > delete/add after master restart and before the reconnection of the slave. > 2) master set up > > on /etc/openldap tar xvf slapd_master.tar (get on the url ) The URL you provided always times out for me, so I've been unable to set up this test. -- -- 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#6377) test058-syncrepl-asymmetric failed for bdb (exit 3)
by hyc＠symas.com 14 Nov '09

14 Nov '09

hyc(a)symas.com wrote: > I'm seeing the same problem here. Still haven't identified the cause, looking... > Fixed. -- -- 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#6377) test058-syncrepl-asymmetric failed for bdb (exit 3)
by hyc＠symas.com 14 Nov '09

14 Nov '09

michael(a)stroeder.com wrote: > Full_Name: Michael Ströder > Version: HEAD synced now > OS: openSUSE Linux 11.2 (x86_64) > URL: > Submission from: (NULL) (84.163.61.118) > > > Stopping central master and site2 servers to test start with emtpy db... > Starting site2 master slapd on TCP/IP port 9013... > Using ldapsearch to check that site2 master slapd is running... > Starting site2 search slapd on TCP/IP port 9016... > Using ldapsearch to check that site2 search slapd is running... > Starting central master slapd on TCP/IP port 9011... > Using ldapsearch to check that central master slapd is running... > Using ldapsearch to check that site2 master received base... > Using ldapsearch to check that site2 search received base... > Waiting 1 seconds for syncrepl to receive changes... > Checking contextCSN after site2 servers repopulated... > Found 3 errors >>>>>> ./scripts/test058-syncrepl-asymmetric failed for bdb (exit 3) > make[2]: *** [bdb-mod] Error 3 > 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 > > I'm seeing the same problem here. Still haven't identified the cause, looking... -- -- 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#6378) Slapadd core dump
by michael＠stroeder.com 14 Nov '09

14 Nov '09

acirulli(a)gmail.com wrote: > Full_Name: Andrea Cirulli > Version: 2.4.16 > OS: Solaris 9 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (62.77.56.182) > > > Problem with slapadd 2.4.16 using an ldif provided by slapcat 2.3.39 > > SLAPADD goes always in core dump on entry of ldif such the following: > > registeredAddress:: MTEzLjIxMS4yMjUuMTgxIAA= > > The base 64 value once converted is "113.211.225.181" + " " + '\0' Not sure whether slapcat 2.3.39 falsely added the NULL-byte at the end or whether it's part of your data. Could you please cross-check that with ldapsearch reading that particular entry? Nevertheless slapadd should not crash. Rather an error should be reported. But please try to reproduce the issue with a recent release (at least 2.4.19, preferrably CVS branch OPENLDAP_REL_ENG_2_4). Another option would be to provide sanitized test data to let others try to reproduce it. Ciao, Michael.

1 0

Re: (ITS#6361) Failed assertion in slapd when running on OpenWRT/glibc
by mike＠flyn.org 14 Nov '09

14 Nov '09

> Please provide stack traces for each of these assertions. In this case it > sounds like connection_closing() got called multiple times for the same > connection, after it had already been fully closed. A trace would help > confirm > that. This is a little odd: (gdb) run -d 255 Starting program: /usr/sbin/slapd -d 255 must compile with LDAP_DEBUG for debugging *** "CRASH" *** Program exited normally. (gdb) ba No stack. I have been running a script, while ldapsearch -x; do sleep 10; done, that eventually crashes slapd. But gdb provides little feedback, as noted above. >> One things to note is that, in addition to being on MIPS32, my platform >> has only 32MB of memory. I also have a swap file that is 64MB. > > In such an environment you won't have enough memory for more than 1 or 2 > server threads. Have you already configured this? I have just reconfigured slapd to use one thread and removed all indexes from the configuration. So far, I have not seen a crash. I am no using two clients to query slapd and have removed that sleep statements so that the server is continuously queried. I've been running this for about one hour and will report back if there are any negative results.

1 0

Re: (ITS#6365) Bad slapcat output when slapd running
by masarati＠aero.polimi.it 14 Nov '09

14 Nov '09

> Howard Chu wrote: >> Peter Mogensen wrote: >>> This is mirrormode. >>> There's no "provider" as such. However, there's one server which is >>> used >>> for application access and to minimize disk load on that server, the >>> plan was to take most backups from the other. >>> I can't see any difference between what you call "initializing" and >>> normal running state, except that the difference between server-1 and >>> server-2 is (somewhat) larger. >> >> If the problem is as Ando suggests, then it's because in the syncrepl >> Refresh >> phase it's receiving entries out-of-order from the provider. Ando is >> suggesting that the problem is caused when a child entry is replicated >> before >> its parent. Once the Refresh phase ends and it transitions to the >> Persist >> phase, all entries' parents will exist and so this particular condition >> will >> no longer occur. >> >> Of course, no one is saying for certain that this is the explanation, >> yet. > > It sounds reasonable to me :) > But unless you are not in any way allowed to - ever - make writes to > more than one server in a mirromode setup, this could (as I hear it) > potentially happen at any time. > The only reason I have to only make writes to one server is that I > currently (this will change) have an application which is dependant on > making writes and immediately reading back the entry. > > As I hear what you're saying is that any write to a server in a > mirrormode setup could invalidate a slapcat running on the other. > This would mean that you can never write to more that one server at all > and that's the only server you can slapcat while running. > That takes a lot of the "mirror" out of "mirrormode". Doesn't it? Based on my *very incomplete and possibly wrong* analysis, the problem would be automatically cured by using back-bdb. Also, fixing back-hdb *if it's broken at all* should be possible. p.

1 0

(ITS#6378) Slapadd core dump
by acirulli＠gmail.com 14 Nov '09

14 Nov '09

Full_Name: Andrea Cirulli Version: 2.4.16 OS: Solaris 9 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (62.77.56.182) Problem with slapadd 2.4.16 using an ldif provided by slapcat 2.3.39 SLAPADD goes always in core dump on entry of ldif such the following: registeredAddress:: MTEzLjIxMS4yMjUuMTgxIAA= The base 64 value once converted is "113.211.225.181" + " " + '\0' The output of the slapadd in verbose mode is: Assertion failed: p == &normalized->bv_val[normalized->bv_len], file schema_init.c, line 2225 Abort (core dumped) 

1 0

Re: (ITS#6377) test058-syncrepl-asymmetric failed for bdb (exit 3)
by michael＠stroeder.com 14 Nov '09

14 Nov '09

See testrun/ http://www.stroeder.com/temp/openldap/openldap-its-6377-testrun.tar.gz

1 0

(ITS#6377) test058-syncrepl-asymmetric failed for bdb (exit 3)
by michael＠stroeder.com 14 Nov '09

14 Nov '09

Full_Name: Michael Ströder Version: HEAD synced now OS: openSUSE Linux 11.2 (x86_64) URL: Submission from: (NULL) (84.163.61.118) Stopping central master and site2 servers to test start with emtpy db... Starting site2 master slapd on TCP/IP port 9013... Using ldapsearch to check that site2 master slapd is running... Starting site2 search slapd on TCP/IP port 9016... Using ldapsearch to check that site2 search slapd is running... Starting central master slapd on TCP/IP port 9011... Using ldapsearch to check that central master slapd is running... Using ldapsearch to check that site2 master received base... Using ldapsearch to check that site2 search received base... Waiting 1 seconds for syncrepl to receive changes... Checking contextCSN after site2 servers repopulated... Found 3 errors >>>>> ./scripts/test058-syncrepl-asymmetric failed for bdb (exit 3) make[2]: *** [bdb-mod] Error 3 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#6365) Bad slapcat output when slapd running
by apm＠mutex.dk 14 Nov '09

14 Nov '09

Howard Chu wrote: > Peter Mogensen wrote: >> This is mirrormode. >> There's no "provider" as such. However, there's one server which is used >> for application access and to minimize disk load on that server, the >> plan was to take most backups from the other. >> I can't see any difference between what you call "initializing" and >> normal running state, except that the difference between server-1 and >> server-2 is (somewhat) larger. > > If the problem is as Ando suggests, then it's because in the syncrepl Refresh > phase it's receiving entries out-of-order from the provider. Ando is > suggesting that the problem is caused when a child entry is replicated before > its parent. Once the Refresh phase ends and it transitions to the Persist > phase, all entries' parents will exist and so this particular condition will > no longer occur. > > Of course, no one is saying for certain that this is the explanation, yet. It sounds reasonable to me :) But unless you are not in any way allowed to - ever - make writes to more than one server in a mirromode setup, this could (as I hear it) potentially happen at any time. The only reason I have to only make writes to one server is that I currently (this will change) have an application which is dependant on making writes and immediately reading back the entry. As I hear what you're saying is that any write to a server in a mirrormode setup could invalidate a slapcat running on the other. This would mean that you can never write to more that one server at all and that's the only server you can slapcat while running. That takes a lot of the "mirror" out of "mirrormode". Doesn't it? >> If I can't trust slapcat during this >> phase, how can I trust slapcat for backups? > > Does slapcat behave this way on the active server? I've taking that test setup down now to test other stuff, so I can't say 100%. /Peter

1 0

Re: (ITS#6365) Bad slapcat output when slapd running
by hyc＠symas.com 14 Nov '09

14 Nov '09

Peter Mogensen wrote: > Howard Chu wrote: >> apm(a)mutex.dk wrote: >>> Pierangelo Masarati wrote: >>>> You appear to be using back-hdb. >>> Yes. >>> >>>> My guess is that if this can fail, e.g. because entries are being >>>> sync'ed out of order, the DN does not get fixed. If this is the case (I >>>> couldn't inspect code deep enough to make sure), I'd expect that the DN >>>> get fixed anyway, though, because missing entries should exist as "glue" >>>> objects. >>> yes. But if you plan to use slapcat as a backup mechanism, then it's >>> still a problem. >> >> Sounds like a low priority issue at best. Taking backups of a replica while it >> is initializing is pointless, just take a backup of the provider instead. > > This is mirrormode. > There's no "provider" as such. However, there's one server which is used > for application access and to minimize disk load on that server, the > plan was to take most backups from the other. > I can't see any difference between what you call "initializing" and > normal running state, except that the difference between server-1 and > server-2 is (somewhat) larger. If the problem is as Ando suggests, then it's because in the syncrepl Refresh phase it's receiving entries out-of-order from the provider. Ando is suggesting that the problem is caused when a child entry is replicated before its parent. Once the Refresh phase ends and it transitions to the Persist phase, all entries' parents will exist and so this particular condition will no longer occur. Of course, no one is saying for certain that this is the explanation, yet. > If I can't trust slapcat during this > phase, how can I trust slapcat for backups? Does slapcat behave this way on the active server? -- -- 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#6365) Bad slapcat output when slapd running
by apm＠mutex.dk 14 Nov '09

14 Nov '09

Howard Chu wrote: > apm(a)mutex.dk wrote: >> Pierangelo Masarati wrote: >>> You appear to be using back-hdb. >> Yes. >> >>> My guess is that if this can fail, e.g. because entries are being >>> sync'ed out of order, the DN does not get fixed. If this is the case (I >>> couldn't inspect code deep enough to make sure), I'd expect that the DN >>> get fixed anyway, though, because missing entries should exist as "glue" >>> objects. >> yes. But if you plan to use slapcat as a backup mechanism, then it's >> still a problem. > > Sounds like a low priority issue at best. Taking backups of a replica while it > is initializing is pointless, just take a backup of the provider instead. This is mirrormode. There's no "provider" as such. However, there's one server which is used for application access and to minimize disk load on that server, the plan was to take most backups from the other. I can't see any difference between what you call "initializing" and normal running state, except that the difference between server-1 and server-2 is (somewhat) larger. If I can't trust slapcat during this phase, how can I trust slapcat for backups? /Peter

1 0

(ITS#6376) memleak in 2.3
by mbackes＠symas.com 14 Nov '09

14 Nov '09

Full_Name: Matthew Backes Version: 2.3 only OS: any URL: Submission from: (NULL) (76.88.99.93) In 2.3, if you have a lot of fast writes such that syncprov_sendresp's op tmp memory is exhausted and it has resorted to malloc()s AND controls are asserted, the rs.sr_ctrls free at the end of the function leaks. To duplicate: Set up a master and a replica. Do mods like crazy with some control asserted, e.g. manageDSAIT. 2.4/head handle this differently so it isn't a problem there. Patch versus OPENLDAP_REL_ENG_2_3: RCS file: /repo/OpenLDAP/pkg/ldap/servers/slapd/overlays/syncprov.c,v retrieving revision 1.56.2.51 diff -u -u -r1.56.2.51 syncprov.c --- syncprov.c 9 Jul 2008 20:53:13 -0000 1.56.2.51 +++ syncprov.c 14 Nov 2009 04:14:26 -0000 @@ -803,6 +803,7 @@ } /* In case someone else freed it already? */ if ( rs.sr_ctrls ) { + op->o_tmpfree( rs.sr_ctrls[0]->ldctl_value.bv_val, op->o_tmpmemctx ); op->o_tmpfree( rs.sr_ctrls[0], op->o_tmpmemctx ); rs.sr_ctrls = NULL; } -- Matthew Backes Symas Corporation mbackes(a)symas.com

1 0

Re: ITS#6375
by jose.oliveira＠mailondemand.com.pt 14 Nov '09

14 Nov '09

This is a multi-part message in MIME format. --------------020401060209020404040703 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Hi,<br> <br> I am sorry for the mistake and inconvenience.<br> Thanks for pointing out right direction.<br> <br> Best regards,<br> <br> <b style=""><span style="font-size: 8pt; font-family: "Verdana","sans-serif";"><font style="color: black;" size="+1">José Vicente Fonseca de Oliveira<br> <img style="width: 125px; height: 108px;" alt="logo mailondemand" src="cid:part1.09010807.09040809@mailondemand.com.pt"><br> </font></span></b><span style="font-family: sans-serif; color: black;"></span><a href="mailto:jose.oliveira@mailondemand.com.pt" target="_blank"><span style="color: rgb(51, 51, 255);"><span style="font-family: sans-serif;">jose.oliveira(a)mailondemand.com.pt</span></span></a><br style="font-family: sans-serif; color: black;"> <a href="http://www.mailondemand.com.pt" target="_blank"><span style="color: rgb(51, 51, 255);"><span style="font-family: sans-serif;">http://www.mailondemand.com.pt</span></span></a><br style="font-family: sans-serif; color: black;"> <br style="font-family: sans-serif; color: black;"> <span style="font-family: sans-serif; color: black;">Av. Miguel Bombarda nº133, 7ºD</span><br style="font-family: sans-serif; color: black;"> <span style="font-family: sans-serif; color: black;">1050-164 Lisboa</span><br style="font-family: sans-serif; color: black;"> <br style="font-family: sans-serif; color: black;"> <span style="font-family: sans-serif; color: black;">Tel: + 351 925440544</span><br style="font-family: sans-serif; color: black;"> <span style="font-family: sans-serif; color: black;"></span><span style="font-family: sans-serif;"><span style="color: black;">Skype + jvf_oliveira</span></span><br> <br> Pierangelo Masarati wrote: <blockquote cite="mid:4AFD95FF.8070209@aero.polimi.it" type="cite">The ITS is to track software bugs.  Please direct software usage questions to <a class="moz-txt-link-rfc2396E" href="mailto:openldap-solftware@openldap.org"><openldap-solftware(a)openldap.org></a> and software interoperation questions to <a class="moz-txt-link-rfc2396E" href="mailto:openldap-technical@openldap.org"><openldap-technical(a)openldap.org></a>. <br> <br> This ITS will be closed. <br> <br> p. <br> <br> _________________________ <br> This email was transferred using an evaluation version <br> of AXIGEN Mail Server. <br> <br> <br> </blockquote> <br> <br> <div class="moz-signature">-- <br> <meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"> <title>JO_Letitwork</title> <b style=""><span style="font-size: 8pt; font-family: "Verdana","sans-serif";"></span></b><span style="font-family: sans-serif;"><span style="color: black;"></span></span><b style=""><span style="font-size: 7pt; font-family: "Verdana","sans-serif"; color: rgb(51, 153, 102);"></span></b><b style=""><span style="font-size: 7pt; font-family: "Verdana","sans-serif"; color: rgb(51, 153, 102);" lang="EN-GB"><br> </span></b></div> </body> </html> <br><br>_________________________<br>This email was transferred using an evaluation version<br>of AXIGEN Mail Server.<br><br> --------------020401060209020404040703 Content-Type: image/jpeg; name="modlogo_small.jpg" Content-Transfer-Encoding: base64 Content-ID: <part1.09010807.09040809(a)mailondemand.com.pt> Content-Disposition: inline; filename="modlogo_small.jpg" /9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAUDBAQEAwUEBAQFBQUGBwwIBwcHBw8LCwkMEQ8S EhEPERETFhwXExQaFRERGCEYGh0dHx8fExciJCIeJBweHx7/2wBDAQUFBQcGBw4ICA4eFBEU Hh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh4eHh7/wAAR CABsAH0DASIAAhEBAxEB/8QAHAAAAAcBAQAAAAAAAAAAAAAAAAECAwQFBgcI/8QANxAAAQMD AwIDBgUDBAMAAAAAAQIDBAAFEQYSIRMxByJRFDJBYXGBI0KRobFSctEVM0PBFjRj/8QAFAEB AAAAAAAAAAAAAAAAAAAAAP/EABQRAQAAAAAAAAAAAAAAAAAAAAD/2gAMAwEAAhEDEQA/APZd ChQoBQos/Ki3UCqFNGQ1uKd6cjuM0sLSRkEGgVQot1FuGaBVCi3fKjBzQChQoUAoj3zR0KAg aOiPHNGDQCklXf5UqknuaCI/LUlvdHZLxzykKwRVLOmz1FSSh1tBOQNhyPuKsXsoeUUfA+Ye opaFhaeDgenpQZpTylKJWrzH1V/mnG3XRyhxz7Z/6rRqQ0oAKSk/Uc0yu3wlqyqOjJ+IGKCo TPlo49oV+v8AkVIRdpYI8yVj5p/xUpVojf8AG68j5b8j96Ycsqtx2voV/e3/AIoHU3p1PvsJ P0JH8in2r4yfeZWPoQarlWqWn3Etq/scI/Y005DmI9+M6oeuAqgvkXaGrupSfqmnm50VZwl5 B+9ZUjYcLBb/ALkKTS0HdwCFfRYV/NBrA6k9lJP3pQVmsXOnIhIUOOpgZyMYHrwavNJOqfsz T6lFRcJOSfnQXVFg0dCgFFjnvR0KCrleSQv9qZPHmT3/AJp25cSftUfefWgfbdCxkdx3HpTu 7jNRFA53oICv5pbLoWnnj1FBJCsjmnAeKjbh8KWFHsDQSEq+dGD8QTUZbqGk7nFgAdyTTXXe e/2ElCf61D+BQS33W205dIAPrUN1lMn3YzTaMZ3qTyfoKdYYSlW9eVr/AKlc0uY504j6z2Q2 on9KDkd5uBU44hBIAJH7mup6Oa6Om4CTnJaBP35riLznVd79zx9zXerS30bZGZ+KGkj9qCbQ oUKDO6p1tpbTExqHfbyxCkvR1yGmVJUpbjaFJSpSUpBKsFQyBzjJ7AkR7Z4g6Nud2YtVs1DC mS5DPWYQ0oqS6naFeVeNqiEqBKQcgHJFV9xs053xvtOpVRErtcXTkyGqQVIyh9yTGUlITndy htzkDHGCeQDz7SujtQWvSvhbAftiI79hny3rkhLzR6CXGJSQrKVYXlbqPdyfNk9jgNdfvEDq 3Z6NYNPzryiM6Y70lEhiOx1U+82hTq09RQwc7QQCCM8Go7niBDVpOTeo0Uofiy4sWRDnPBhT Snnm20kqAUCCHApJTlK+ACM5HFLlCjt3kQLzD07NkQrPKtJh3uYmN7I8t9biZ7O9KgsOJKcq RhQKQMjBxorBpK+XbwYjIhm2zphj2GCy3AmJcbW1b5TJddLitqSSEOqwOMJABUTQdh0lqQX6 4akiGH7ObJeF2zd1N3W2sMu9TGBt/wB7G3n3c55wE3DXGkrfqAWOZfobNyK0NlpW7CFr9xCl 42oUrIwlRBORiq3w/tNxtV31rInx+i3c9RuToZ3pV1GTFjNhXBO3zNrGDg8dsEVi77pfVy7f q3SMTTzUuLqK6Klt3tU1pLcZDnT3dRsnqlxvYdm1KgcJ5FB0O7+IuibPdJNqumo4cSbFcbak tOBX4ClpSpG8gYQCFpwokDnGc1orjLTFhuynHW2GWUlx111QSlCAMlRJ4AA5zXLL5o69SbZ4 xstW1Lr2pYiWrSVOtgylJtaGBklXkw6FDz7fXtzWp1vp6fqLwln6YZcaanybWlhPWVlHUCU+ VRGfKSnaSM8E96CNpzxF07ftcw9P2SS1c0yLXIuLkvepBaDbjKEp6akjKVB0kLBx5eM5yNBp /W2k79dja7NfIsyYEqWltG4dRKThSmyQA4ASMlBIFc8cs+r9Ua7RdZ+lHNMw/wDxWdaVPLnx 33EvvOMFOA0o+QBCik9+DkJyAS8K9I3a33fTov1i1GhyxMltubIv7D8FKun0yWWknqYUM8KS nHzxQbWD4reHk1tLkTVlvdQtj2hsgL/FRlI8mU+dWVJBSnKgSBinNR6406jw9c1JDuCZ8KYh TEIxUla5Lp3J6aE99wKVZBxt2qzjBrC6F0Lf7ZZvBiNOs7bTmmESv9WT1mlezKXDdQkjCjvJ dUnlG7nk8DNU2qrFetM6Tud0ucZyNETqW9v72lJdMePNWroSsIJwBkZHdIcJIGDQZ+26s2XS Gi72WVbozshLXtC32XUoO5I/ECFko5IBJGBkZxXoG7eI2h7HOetd11DEizIgbElpSVEshaQU qWQCEpI/McD51420rpw3K+afs9vZ0tDcetki1SZEW4BxcjqJQDI2pRlSsJWoZ5yeSBivSj2m ru8fFFSLehZv8BqPblF1vMgpiKbKTk+UbzjzYHOe3NB0TUWttKaemxIV5vkSHIloLrSFEn8M EAuKwDsbyR51YT86Lwz1MdZ6AseqzB9g/wBVhok+zdXqdLcM7d2Bn64Fc8tdk1fp3US7lE0u 3qFF401b7W8lyay37A/HS6FJc3nzMK62SW96spPlORWx8D7Jc9N+EOlrDeo3stxgW1piSz1E r2LSORuSSk/UEig0cg5SaqZ5wDjvVxIAKTVZKa3ZyKDB6otMW6Ae3Q48nZ7nWaC9v0yOKz64 06CoKhSXmMDACVHH6dq6LNiBWeKqZlvBHYUGaias1BCwmQGpaB/WMH9RV3A1/BXhM6K9HV8S BuFQ5NrB7Jqsk2gEny0HQbdf7RPA9mnsLUfylWD+hq0QoiuMP2jBKgnB+XFORJd9t3/qT5CQ PyqVuH6Gg7MlfPejJwdzf3Fcyha6vDGBNiMygO5RlBP/AFWgt+u7NIUEyA9DX/8AROR+ooNg leeQeKzviY9s0m8M4K1oT+9WMS4QpWFw5TT2e4SofxWb8V5ATp9htIV+LIAGB6A0HO9MoiwL 63Ihw4zasnqltsJJ+pA5rsFonIkISoHFcx09bHdyVrB3HGeK3tmjrbSO9Bsoi8gYqe2Vbe9U 9vztHNW7OdnagQ63x2qI80DxirMjNNONjvQUz0cEcioL0UHvV+40DTDkfPwFBm3oXHaojsAH 4VqnIwNMKij0oMg9bQfy/tUR21A/l/atouIk00qCPSgw7tnTn3f2plVhSr/jz9q3nsA9KUiA PSgwcXTQDgUjc2fVPBrRMWcOMIalLXICFbkhw5wa0TMNKfhzUhEYA9qCni2uO37rYFWkaClP apTbAB7CpTLWKBMeOE9hUwBIGKShO0c0a/hmgXREZo6FAkoBpBbBp2kUDSmvjikKaHfFScmj wKCF0BntRFgH4VO2ihtFBA9nHpSkx0/Gpu0UNooIyY4+ApYZA+FOng4FDJ9aBAbA+FObR8BS aWKBOPnSXCvjakH6mnD2pIoP/9k= --------------020401060209020404040703--

1 0

Re: (ITS#6368) Bug in deleting entry in MirrorMode
by hyc＠symas.com 13 Nov '09

13 Nov '09

pitpalme(a)gmail.com wrote: > masarati(a)aero.polimi.it wrote: > >> pitpalme(a)gmail.com wrote: >> >>> I do see attributes reflecting state after "modify" (which changes >>> "sn" attribute). >>> Where exactly should I expect to see a note about "glue state"? >>> Is output from "-d Any" helpful to figure what's going on (or wrong)? >> >> My understanding of your previous message was that you got a positive >> result from delete, but an "Already exists" from a subsequent add. > > That=92s korrekt. > >> I inferred that you checked about the existence of the object and =20 >> you got >> a negative result. > > In my current test scenario I do not check. > I assume a non-error on =84delete=93 in fact =84deletes=93, so I just = > check if =20 > response > code success (in Perl: '$res->code =3D=3D Net::LDAP::LDAP_SUCCESS=91). > >> Apparently, my guess was wrong. In that case, you probably hit >> ITS#6097 <http://www.openldap.org/its?findid=3D6097>. > > *hmmm* Good idea, thanks. > But after reading ITS description I don=92t think it=92s what troubles = > me. > We don=92t actually neither have =84multi master mode=93, but =84mirror = > mode=93 =20 > and writes are done only on exactly one server, so there should not be =20= > > a problem with second server producing a concurrent write/modify. > I=92d expect the delete to be correctly propagated, but I can=92t check = > it =20 > is is, simply because I have to little knowledge to read debug log =20 > correctly. > =97 Paste the debug log somewhere we can see it then. Might as well use debug level -1 while executing this sequence. And provide the debug output from both 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#6361) Failed assertion in slapd when running on OpenWRT/glibc
by hyc＠symas.com 13 Nov '09

13 Nov '09

mike(a)flyn.org wrote: > Yes, I have just been able to recreate this in 2.4.19. The line in > daemon.c at which the assertion occurs in this version is 994. > > I have also seen: > > ldap_write: want=22 error=Broken pipe > ... > slapd: connection.c:786: connection_closing: Assertion 'c->c_struct_state > == SLAP_C_USED' failed Please provide stack traces for each of these assertions. In this case it sounds like connection_closing() got called multiple times for the same connection, after it had already been fully closed. A trace would help confirm that. > One things to note is that, in addition to being on MIPS32, my platform > has only 32MB of memory. I also have a swap file that is 64MB. In such an environment you won't have enough memory for more than 1 or 2 server threads. Have you already configured this? -- -- 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#6367) syncprov ... changed by peer, ignored
by hyc＠symas.com 13 Nov '09

13 Nov '09

olivier.chirossel(a)sfr.com wrote: > Full_Name: olivier chirossel > Version: 2.4.17 and 2.4.19 > OS: linux > URL: http://86.64.145.174:8080/ > Submission from: (NULL) (62.39.9.251) > > > in refreshend persist mode, the replication is incorrect for an entry which be > delete/add after master restart and before the reconnection of the slave. > 2) master set up > > on /etc/openldap tar xvf slapd_master.tar (get on the url ) The URL you provided always times out for me, so I've been unable to set up this test. -- -- 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#6365) Bad slapcat output when slapd running
by hyc＠symas.com 13 Nov '09

13 Nov '09

apm(a)mutex.dk wrote: > Pierangelo Masarati wrote: >> You appear to be using back-hdb. > > Yes. > >> My guess is that if this can fail, e.g. because entries are being >> sync'ed out of order, the DN does not get fixed. If this is the case (I >> couldn't inspect code deep enough to make sure), I'd expect that the DN >> get fixed anyway, though, because missing entries should exist as "glue" >> objects. > > yes. But if you plan to use slapcat as a backup mechanism, then it's > still a problem. Sounds like a low priority issue at best. Taking backups of a replica while it is initializing is pointless, just take a backup of the provider instead. -- -- 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#6365) Bad slapcat output when slapd running
by apm＠mutex.dk 13 Nov '09

13 Nov '09

Pierangelo Masarati wrote: > You appear to be using back-hdb. Yes. > My guess is that if this can fail, e.g. because entries are being > sync'ed out of order, the DN does not get fixed. If this is the case (I > couldn't inspect code deep enough to make sure), I'd expect that the DN > get fixed anyway, though, because missing entries should exist as "glue" > objects. yes. But if you plan to use slapcat as a backup mechanism, then it's still a problem. /Peter

1 0

Re: (ITS#6365) Bad slapcat output when slapd running
by masarati＠aero.polimi.it 13 Nov '09

13 Nov '09

apm(a)mutex.dk wrote: > Full_Name: Peter Mogensen > Version: 2.4.19 > OS: Debian Lenny > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (95.166.36.16) > > > Using openldap 2.4.17 and 2.4.19 linked with libdb4.6 and libdb4.8 in a > mirrormode setup: > > * Load the database with slapadd on server-1, start server-1 > The LDIF being loaded is generated with slapcat from a slapd 2.3.30-5+etch2 > Running on Debian Etch. I have no reason to suspect that it is not loaded > correctly into server1 > > * Start server-2 and monitor the progress of replication with slapcat, for > example: > > # for ((I=1;I<=20;I++)); do slapcat > out-$I; done > > * Look at the output: > > # for ((I=1;I<=20;I++)); do wc -l out-$I; done > > I would expect the generated files to be strictly increasing in size. > However, some times there's a file which is smaller than the previous. > In it I see LDIF entries like this: > > dn: > objectClass: top > objectClass: NamedObject > objectClass: simpleSecurityObject > uid: rieke > userPassword:: e1NBU0x..... > structuralObjectClass: NamedObject > entryUUID: e46b680e-e5f5-102b-93c9-79162adc1d46 > creatorsName: dc=admin,dc=example,dc=com > createTimestamp: 20070823185333Z > entryCSN: 20070823185333.000000Z#000002#000#000000 > modifiersName: dc=admin,dc=example,dc=com > modifyTimestamp: 20070823185333Z > > ... with an empty DN line. You appear to be using back-hdb. I note that in bdb_tool_entry_get() there is code specific to back-hdb that tries to lookup the parent of the current entry and, if found, "fixes" its DN. My guess is that if this can fail, e.g. because entries are being sync'ed out of order, the DN does not get fixed. If this is the case (I couldn't inspect code deep enough to make sure), I'd expect that the DN get fixed anyway, though, because missing entries should exist as "glue" objects. I apologize for the rather incomplete analysis, I can't dig further right now. I hope this provides some hint to others, unless completely wrong. p.

1 0

ITS#6375
by masarati＠aero.polimi.it 13 Nov '09

13 Nov '09

The ITS is to track software bugs. Please direct software usage questions to <openldap-solftware(a)openldap.org> and software interoperation questions to <openldap-technical(a)openldap.org>. This ITS will be closed. p.

1 0

(ITS#6375) Master Replica Synchronization
by jose.oliveira＠mailondemand.com.pt 13 Nov '09

13 Nov '09

Full_Name: Jose Vicente Fonseca de Oliveira Version: 2.4.11-1 OS: Debian 5.03 URL: ftp://mailondemand.com.pt Submission from: (NULL) (81.193.248.175) Dear Team, We have a PineApp antispam appliance that can authenticate users with our LDAP master server but cannot authenticate users with our LDAP replica server. For us everything seems OK but PineApp appliance just can't authenticate with our replica. PineApp refuses to give us further help saying that something is wrong in LDAP replication. Please, could you help us with that issue: the replica has the same information that master server has? We thank OpenLDAP Team in advance. Best regards, Jose Oliveira

1 0

Re: (ITS#6374) LDAP
by michael＠stroeder.com 13 Nov '09

13 Nov '09

atzig(a)mail2tim.com wrote: > Full_Name: Tim > Version: ? > OS: Win2003 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (216.62.17.129) > > > "Error 10: Referral" > > Unable to perform LDAP search - Error 10: Referral > This error means that the user's record in Active Directory was located on some > other server. > A "referral" in LDAP is simply a pointer or redirection to some other location > (or server). The "Error 10: Referral" error is usually caused by a misconfigured > LDAPBaseDN setting > > > LDAP was working correctly...started to receive this error after upgrading from > win2003 AD to Win2008. Could you please elaborate on what's the issue is with OpenLDAP client libs and/or tools? Ciao, Michael.

1 0

(ITS#6374) LDAP
by atzig＠mail2tim.com 12 Nov '09

12 Nov '09

Full_Name: Tim Version: ? OS: Win2003 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (216.62.17.129) "Error 10: Referral" Unable to perform LDAP search - Error 10: Referral This error means that the user's record in Active Directory was located on some other server. A "referral" in LDAP is simply a pointer or redirection to some other location (or server). The "Error 10: Referral" error is usually caused by a misconfigured LDAPBaseDN setting LDAP was working correctly...started to receive this error after upgrading from win2003 AD to Win2008.

1 0

Re: (ITS#6368) Bug in deleting entry in MirrorMode
by pitpalme＠gmail.com 12 Nov '09

12 Nov '09

--001636988beae98b80047830ba81 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable pitpalme(a)gmail.com wrote: > masarati(a)aero.polimi.it wrote: > > pitpalme(a)gmail.com wrote: >> >> I do see attributes reflecting state after "modify" (which changes >>> "sn" attribute). >>> Where exactly should I expect to see a note about "glue state"? >>> Is output from "-d Any" helpful to figure what's going on (or wrong)? >>> >> >> My understanding of your previous message was that you got a positive >> result from delete, but an "Already exists" from a subsequent add. >> > > That=92s korrekt. > > > I inferred that you checked about the existence of the object and you go= t >> a negative result. >> > > In my current test scenario I do not check. > I assume a non-error on =84delete=93 in fact =84deletes=93, so I just che= ck if > response > code success (in Perl: '$res->code =3D=3D Net::LDAP::LDAP_SUCCESS=91). > > > Apparently, my guess was wrong. In that case, you probably hit >> ITS#6097 <http://www.openldap.org/its?findid=3D6097>. >> > > *hmmm* Good idea, thanks. > But after reading ITS description I don=92t think it=92s what troubles m= e. > We don=92t actually neither have =84multi master mode=93, but =84mirror m= ode=93 and > writes are done only on exactly one server, so there should not be a prob= lem > with second server producing a concurrent write/modify. > I=92d expect the delete to be correctly propagated, but I can=92t check i= t is > is, simply because I have to little knowledge to read debug log correctly= . Follow up: I modified my test Perl script to do a 'ldapSearch' after deleting and it returns zero as number of found entries. Sadly I have no idea, how to emulate '-MM' when using 'Net::LDAP' and it's search function, so I can't check for 'glue' entries this way. --=20 Regards, Peter --001636988beae98b80047830ba81 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: quoted-printable <div class=3D"gmail_quote"><span dir=3D"ltr"><a href=3D"mailto:pitpalme@gma= il.com">pitpalme(a)gmail.com</a></span>=A0wrote:<br><blockquote class=3D"gmai= l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left= :1ex;"><div class=3D"im"> <a href=3D"mailto:masarati@aero.polimi.it" target=3D"_blank">masarati(a)aero.= polimi.it</a> wrote:<br> <br> </div><div class=3D"im"><blockquote class=3D"gmail_quote" style=3D"margin:0= 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <a href=3D"mailto:pitpalme@gmail.com" target=3D"_blank">pitpalme(a)gmail.com<= /a> wrote:<br> <br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> I do see attributes reflecting state after "modify" (which change= s<br> "sn" attribute).<br> Where exactly should I expect to see a note about "glue state"?<b= r> Is output from "-d Any" helpful to figure what's going on (or= wrong)?<br> </blockquote> <br> My understanding of your previous message was that you got a positive<br> result from delete, but an "Already exists" from a subsequent add= .<br> </blockquote> <br></div> That=92s korrekt.<div class=3D"im"><br> <br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> I inferred that you checked about the existence of the object and you got<b= r> a negative result.<br> </blockquote> <br></div> In my current test scenario I do not check.<br> I assume a non-error on =84delete=93 in fact =84deletes=93, so I just check= if response<br> code success (in Perl: '$res->code =3D=3D Net::LDAP::LDAP_SUCCESS=91= ).<div class=3D"im"><br> <br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> Apparently, my guess was wrong. =A0In that case, you probably hit<br> ITS#6097 <<a href=3D"http://www.openldap.org/its?findid=3D6097" target= =3D"_blank">http://www.openldap.org/its?findid=3D6097</a>>.<br> </blockquote> <br></div> *hmmm* Good idea, thanks.<br> But after reading ITS description I don=92t think it=92s =A0what troubles m= e.<br> We don=92t actually neither have =84multi master mode=93, but =84mirror mod= e=93 and writes are done only on exactly one server, so there should not be= a problem with second server producing a concurrent write/modify.<br> I=92d expect the delete to be correctly propagated, but I can=92t check it = is is, simply because I have to little knowledge to read debug log correctl= y.</blockquote></div><div><br></div>Follow up:<div><br></div><div>I modifie= d my test Perl script to do a 'ldapSearch' after deleting and it re= turns zero as number of found entries.</div> <div>Sadly I have no idea, how to emulate '-MM' when using 'Net= ::LDAP' and it's search function, so I can't check for 'glu= e' entries this way.</div><div>-- <br>Regards, <div>Peter</div></div> --001636988beae98b80047830ba81--

1 0

Re: (ITS#6368) Bug in deleting entry in MirrorMode
by pitpalme＠gmail.com 12 Nov '09

12 Nov '09

masarati(a)aero.polimi.it wrote: > pitpalme(a)gmail.com wrote: > >> I do see attributes reflecting state after "modify" (which changes >> "sn" attribute). >> Where exactly should I expect to see a note about "glue state"? >> Is output from "-d Any" helpful to figure what's going on (or wrong)? > > My understanding of your previous message was that you got a positive > result from delete, but an "Already exists" from a subsequent add. That=92s korrekt. > I inferred that you checked about the existence of the object and =20 > you got > a negative result. In my current test scenario I do not check. I assume a non-error on =84delete=93 in fact =84deletes=93, so I just = check if =20 response code success (in Perl: '$res->code =3D=3D Net::LDAP::LDAP_SUCCESS=91). > Apparently, my guess was wrong. In that case, you probably hit > ITS#6097 <http://www.openldap.org/its?findid=3D6097>. *hmmm* Good idea, thanks. But after reading ITS description I don=92t think it=92s what troubles = me. We don=92t actually neither have =84multi master mode=93, but =84mirror = mode=93 =20 and writes are done only on exactly one server, so there should not be =20= a problem with second server producing a concurrent write/modify. I=92d expect the delete to be correctly propagated, but I can=92t check = it =20 is is, simply because I have to little knowledge to read debug log =20 correctly. =97 Regards, Peter

1 0

Re: (ITS#6368) Bug in deleting entry in MirrorMode
by masarati＠aero.polimi.it 12 Nov '09

12 Nov '09

pitpalme(a)gmail.com wrote: > I do see attributes reflecting state after "modify" (which changes > "sn" attribute). > Where exactly should I expect to see a note about "glue state"? > Is output from "-d Any" helpful to figure what's going on (or wrong)? My understanding of your previous message was that you got a positive result from delete, but an "Already exists" from a subsequent add. I inferred that you checked about the existence of the object and you got a negative result. Apparently, my guess was wrong. In that case, you probably hit ITS#6097 <http://www.openldap.org/its?findid=6097>. p.

1 0

Re: (ITS#6368) Bug in deleting entry in MirrorMode
by pitpalme＠gmail.com 11 Nov '09

11 Nov '09

masarati(a)aero.polimi.it wrote: > pitpalme+openldap(a)gmail.com wrote: >> [...] >> When adding, modifying and deleting an entry it can happend I do >> get a positive >> return from delete, but a subsequent "add" fails with "code=68: >> Already >> exists". > > Can you check whether the entry actually exist, although in "glue" > state? You can do this by searching (e.g. with ldapsearch) as the > rootdn, to bypass access checking, and using the manageDSAit control > (-MM). I modified my test perl script to exit if adding the entry failed, albeit a preceding delete should have removed it. Then I manually ran ldapsearch -D "rootdn" ... -b "TestBaseDN" -MM "cn=TestEntry" I got ==== 8>< ========================== [...] # with manageDSAit critical control [...] dn: cn=TestEntry,TestBaseDN objectClass: inetOrgPerson description: oldValue [...] # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 ==== 8>< ========================== I do see attributes reflecting state after "modify" (which changes "sn" attribute). Where exactly should I expect to see a note about "glue state"? Is output from "-d Any" helpful to figure what's going on (or wrong)? -- Regards, Peter

1 0

Re: (ITS#6300) Add kqueue support to slapd
by bduncan＠apple.com 11 Nov '09

11 Nov '09

On Nov 11, 2009, at 9:45 AM, Quanah Gibson-Mount wrote: > --On Wednesday, November 11, 2009 9:36 AM -0800 Bryan Duncan = <bduncan(a)apple.com> wrote: >=20 >>=20 >> On Nov 11, 2009, at 9:04 AM, Quanah Gibson-Mount wrote: >>=20 >>> --On Tuesday, September 22, 2009 2:40 PM -0700 Bryan Duncan >>> <bduncan(a)apple.com> wrote: >>>=20 >>>=20 >>>> It was tested on OS X 10.6. Should work on all BSDs; nothing >>>> OSX-specific about the kqueue usage in the patch. As far as kqueue >>>> support in OS X 10.5, from what I see, most everything is there. >>>> Certainly all of the kqueue features in this patch are supported in = OS X >>>> 10.5. >>>=20 >>> Hi Bryan, >>>=20 >>> The URL to the patch you submitted with this ITS doesn't work. Can = you >>> please put the patch somewhere accessible and let us know where it = is? >>>=20 >>> Thanks, >>> Quanah >>=20 >> Hi Quanah, >>=20 >> My apologies for the bad URL. >>=20 >> The new URL is: >> http://public.me.com/bryan.duncan/bryan-duncan.kqueue.090922.patch If = you >> use a web browser to get it, there are extra steps: select the file >> "bryan-duncan.kqueue.090922.patch" and click download. ftp & curl = can >> pull it down directly with no extra steps. >=20 > Hi Bryan, >=20 > Thanks for the quick response. Hopefully we can get this incorporated = for OpenLDAP 2.5 series, and I'm interested in playing with it against = 2.4 to see how things change when used with Mac. >=20 > Thanks! >=20 > --Quanah Awesome! I look forward to seeing it OpenLDAP. If there's anything I = can do to help, please let me know. Thanks.=20 -- Bryan

1 0

Re: (ITS#6300) Add kqueue support to slapd
by quanah＠zimbra.com 11 Nov '09

11 Nov '09

--On Wednesday, November 11, 2009 9:36 AM -0800 Bryan Duncan <bduncan(a)apple.com> wrote: > > On Nov 11, 2009, at 9:04 AM, Quanah Gibson-Mount wrote: > >> --On Tuesday, September 22, 2009 2:40 PM -0700 Bryan Duncan >> <bduncan(a)apple.com> wrote: >> >> >>> It was tested on OS X 10.6. Should work on all BSDs; nothing >>> OSX-specific about the kqueue usage in the patch. As far as kqueue >>> support in OS X 10.5, from what I see, most everything is there. >>> Certainly all of the kqueue features in this patch are supported in OS X >>> 10.5. >> >> Hi Bryan, >> >> The URL to the patch you submitted with this ITS doesn't work. Can you >> please put the patch somewhere accessible and let us know where it is? >> >> Thanks, >> Quanah > > Hi Quanah, > > My apologies for the bad URL. > > The new URL is: > http://public.me.com/bryan.duncan/bryan-duncan.kqueue.090922.patch If you > use a web browser to get it, there are extra steps: select the file > "bryan-duncan.kqueue.090922.patch" and click download. ftp & curl can > pull it down directly with no extra steps. Hi Bryan, Thanks for the quick response. Hopefully we can get this incorporated for OpenLDAP 2.5 series, and I'm interested in playing with it against 2.4 to see how things change when used with Mac. Thanks! --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#6300) Add kqueue support to slapd
by bduncan＠apple.com 11 Nov '09

11 Nov '09

On Nov 11, 2009, at 9:04 AM, Quanah Gibson-Mount wrote: > --On Tuesday, September 22, 2009 2:40 PM -0700 Bryan Duncan = <bduncan(a)apple.com> wrote: >=20 >=20 >> It was tested on OS X 10.6. Should work on all BSDs; nothing >> OSX-specific about the kqueue usage in the patch. As far as kqueue >> support in OS X 10.5, from what I see, most everything is there. >> Certainly all of the kqueue features in this patch are supported in = OS X >> 10.5. >=20 > Hi Bryan, >=20 > The URL to the patch you submitted with this ITS doesn't work. Can = you please put the patch somewhere accessible and let us know where it = is? >=20 > Thanks, > Quanah Hi Quanah, My apologies for the bad URL. The new URL is: = http://public.me.com/bryan.duncan/bryan-duncan.kqueue.090922.patch If you use a web browser to get it, there are extra steps: select the = file "bryan-duncan.kqueue.090922.patch" and click download. ftp & curl = can pull it down directly with no extra steps. -- Bryan=

1 0

Re: (ITS#6300) Add kqueue support to slapd
by quanah＠zimbra.com 11 Nov '09

11 Nov '09

--On Tuesday, September 22, 2009 2:40 PM -0700 Bryan Duncan <bduncan(a)apple.com> wrote: > It was tested on OS X 10.6. Should work on all BSDs; nothing > OSX-specific about the kqueue usage in the patch. As far as kqueue > support in OS X 10.5, from what I see, most everything is there. > Certainly all of the kqueue features in this patch are supported in OS X > 10.5. Hi Bryan, The URL to the patch you submitted with this ITS doesn't work. Can you please put the patch somewhere accessible and let us know where it is? Thanks, Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

1 0

Re: (ITS#6362) slapd 2.4.19 Segmentation fault under load
by alexs＠ulgsm.ru 11 Nov '09

11 Nov '09

--IJpNTDwzlM2Ie8A6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * mbackes(a)symas.com <mbackes(a)symas.com> [2009-11-10 22:55:10 +0000]: > Hello, Aleksey. >=20 > > Openldap 2.4.19 installed from freebsd ports. All configs in defauls = =20 > > Freebsd 7.2 amd64 Slapd built with the "-g" flag and install with =20 > > the make install STRIP=3D"" >=20 > Okay. >=20 > > Used backends db46-4.6.21.4, db47-4.7.25.4 latest from freebsd ports. >=20 > > libdb-4.6.so.0 =3D> /usr/local/lib/libdb-4.6.so.0 (0x800a97000) >=20 > At the same time? Your ldd list below shows only berkeley db 4.6. =20 > These don't mix... Not same time. I tried with both backends. Results are same. >=20 > > In slapd config added using hdb as backend and indexes. Testing =20 > > database consist of 1000 users accounts with minimum attributes. On = =20 > > stress test load slapd Segmentation fault in 10-30 sec. >=20 > What sort of operations? Reading (Binds and searches).=20 Test script is loop of id command checking ldap via nss_ldap. >=20 > > Program received signal SIGSEGV, Segmentation fault. > > [Switching to Thread 0x803404560 (LWP 100116)] > > 0x0000000802d5aa4b in hdb_idl_fetch_key (be=3DError accessing memory = =20 > > address > > 0x7ffffd9f9f38: Bad s. > > ) at idl.c:511 >=20 > Does it always fail at the same location? How reproducible is this? Often it is fail in "hdb_idl_fetch_key (be=3DError accessing memory address= ". 100% Reproducible on different hardware. On our normal work, slapd fails every 2-3 hours, on stress test slapd fail in 10-30 sec. Problem on freebsd7.x,8 and openldap2.3.43,2.4.18,2.4.19=20 I tryed on debian lenny and openldap2.4.11 and netbsd5.0.1 and openldap2.4.16 it rock stable. I think problem some where in freebsd and bdb backends.=20 Because freebsd7.1 openldap2.3.43 with depricated ldbm don`t fail on reading.=20 Ask if need any information.=20 Also I can give a shell access to testing server. =20 >=20 > Matthew Backes > Symas Corporation > mbackes(a)symas.com --=20 Email: alexs(a)ulgsm.ru Email/Jabber: alexs(a)ulgsm.ru --IJpNTDwzlM2Ie8A6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iQEcBAEBAgAGBQJK+lahAAoJELAIdrQw5JcdnyYIAJrpD8OhUgzabzlAfcSmOZhH XUM+vzujX4N/czArACk/dXibX3D2AqQxv1CeUs0pI7Bo+iHLG0gsP6UD8k1fvDEg NecNe1zigD7JEGJDetHTMSXHjYkOvSJsqdBcWjNPuJZn62mg5hVs0S3XdGtqMRxw 4Ck+MwyWiAVQmCDYaXSCEEl6IyGehtD6f5liyNVakHIHG7bZ5MFSm0yP2oMtgxw2 W5vY7nUYK7w3l8ZXqx5pyjQBVBHoUCLFaqHXdXTcBHe3WJ2TQMx6utyvWi3uuqaR HFmg2NMvJSVnTnQsscxZgd2qILAmAx0SE2wd4D312ywsYZvFSGkzjX50JNpklT0= =s9Mn -----END PGP SIGNATURE----- --IJpNTDwzlM2Ie8A6--

1 0

ITS#5944 configure options --program-prefix and --program-suffix
by hyc＠symas.com 11 Nov '09

11 Nov '09

The OpenLDAP configure script and Makefiles don't do anything with these options. Sounds like you're looking at a RedHat-specific issue. This ITS will be closed. -- -- 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#6373) syncrepl subentry support
by hyc＠OpenLDAP.org 11 Nov '09

11 Nov '09

Full_Name: Howard Chu Version: 2.4/HEAD OS: Linux URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (76.91.220.157) Submitted by: hyc As discussed in this email thread http://www.openldap.org/lists/openldap-software/200910/msg00059.html in some situations it's necessary to store the syncrepl contextCSNs in a subentry of the database, instead of the context entry. Syncrepl in 2.2 used to do this but most of that code was removed in 2.3. It needs to be resurrected and usable as an option.

1 0

Re: (ITS#6312)
by hyc＠symas.com 11 Nov '09

11 Nov '09

neustradamus(a)hotmail.com wrote: > --_add76be3-02e1-47b1-b978-259bce59b479_ > Content-Type: text/plain; charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > > You must change in configure and \include\PORTABLE.H : > > #define vsnprintf _vsnprintf > > with > > #if _MSC_VER < 1500 // 1500 =3D=3D VC++ 9.0 > #define vsnprintf _vsnprintf > #endif > > or > > #if _MSC_VER < 1500 > #define vsnprintf _vsnprintf > #endif You reported this issue against 2.2.16, which is several years obsolete. (Current version is 2.4.19.) The configure script has checked for vsnprintf and _vsnprintf for many years; it will not setup this #define if it doesn't need to. Closing this ITS. -- -- 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#6309) missing SEARCH information
by hyc＠symas.com 11 Nov '09

11 Nov '09

quanah(a)zimbra.com wrote: > Full_Name: Quanah Gibson-Mount > Version: 2.4.18 > OS: Linux 2.6 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (75.111.29.239) > > > I see the following logged at level 256: > > Sep 28 17:35:23 ldap1 slapd[18015]: conn=409 fd=117 ACCEPT from > IP=171.67.219.70:51122 (IP=0.0.0.0:389) > Sep 28 17:35:23 ldap1 slapd[18015]: conn=409 op=0 BIND dn="" method=163 > Sep 28 17:35:23 ldap1 slapd[18015]: conn=409 op=0 RESULT tag=97 err=14 > text=SASL(0): successful result: > Sep 28 17:35:23 ldap1 slapd[18015]: conn=409 op=1 BIND dn="" method=163 > Sep 28 17:35:23 ldap1 slapd[18015]: conn=409 op=1 RESULT tag=97 err=14 > text=SASL(0): successful result: > Sep 28 17:35:23 ldap1 slapd[18015]: conn=409 op=2 BIND dn="" method=163 > Sep 28 17:35:23 ldap1 slapd[18015]: conn=409 op=2 BIND > authcid="service/vacation(a)stanford.edu" authzid="service/vacation(a)stanford.edu" > Sep 28 17:35:23 ldap1 slapd[18015]: conn=409 op=2 BIND > dn="cn=vacation,cn=service,cn=applications,dc=stanford,dc=edu" mech=GSSAPI > sasl_ssf=56 ssf=56 > Sep 28 17:35:23 ldap1 slapd[18015]: conn=409 op=2 RESULT tag=97 err=0 text= > Sep 28 17:35:23 ldap1 slapd[18015]: conn=409 op=3 do_search: invalid dn > (basedn) > Sep 28 17:35:23 ldap1 slapd[18015]: conn=409 op=3 SEARCH RESULT tag=101 err=34 > nentries=0 text=invalid DN > Sep 28 17:35:23 ldap1 slapd[18015]: conn=409 fd=117 closed (connection lost) > > > Since the actual search is not logged, there is no way to determine what the > invalid DN being used is in this case. This seems faulty. I'd expect to see > some additional logging like: The invalid DN *was* logged, it was "basedn". Sounds like you have a really badly configured client out there somewhere. Closing this ITS... -- -- 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#6372) slapd lockup on shutdown
by quanah＠zimbra.com 11 Nov '09

11 Nov '09

Full_Name: Quanah Gibson-Mount Version: 2.4.19 OS: Linux 2.6 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (75.111.29.239) Had an idle slapd lock up during shutdown. Backtrace as follows: Thread 10 (process 627): #0 0x0000003c0c70b04f in __write_nocancel () from /lib64/tls/libpthread.so.0 #1 0x0000000000431d3e in slap_sig_shutdown (sig=2) at daemon.c:2926 #2 <signal handler called> #3 0x0000003c0c70b04d in __write_nocancel () from /lib64/tls/libpthread.so.0 #4 0x0000000000431d3e in slap_sig_shutdown (sig=15) at daemon.c:2926 #5 <signal handler called> #6 0x0000003c0c706ffb in pthread_join () from /lib64/tls/libpthread.so.0 #7 0x0000002a956b2408 in ldap_pvt_thread_join (thread=1082132832, thread_return=0x0) at thr_posix.c:197 #8 0x0000000000431c8c in slapd_daemon () at daemon.c:2835 #9 0x00000000004146d8 in main (argc=10, argv=0x7fbfffae38) at main.c:950 Thread 9 (process 637): #0 0x0000003c0c7089ba in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/tls/libpthread.so.0 #1 0x0000002a956b24b0 in ldap_pvt_thread_cond_wait (cond=0x932030, mutex=0x932008) at thr_posix.c:277 #2 0x0000002a956b0fbf in ldap_int_thread_pool_wrapper (xpool=0x932000) at tpool.c:672 #3 0x0000003c0c70610a in start_thread () from /lib64/tls/libpthread.so.0 #4 0x0000003c0b8c68c3 in clone () from /lib64/tls/libc.so.6 Thread 8 (process 636): #0 0x0000003c0c70b04f in __write_nocancel () from /lib64/tls/libpthread.so.0 #1 0x0000000000431d3e in slap_sig_shutdown (sig=15) at daemon.c:2926 #2 <signal handler called> #3 0x0000003c0c7089ba in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/tls/libpthread.so.0 #4 0x0000002a956b24b0 in ldap_pvt_thread_cond_wait (cond=0x932030, mutex=0x932008) at thr_posix.c:277 #5 0x0000002a956b0fbf in ldap_int_thread_pool_wrapper (xpool=0x932000) at tpool.c:672 #6 0x0000003c0c70610a in start_thread () from /lib64/tls/libpthread.so.0 #7 0x0000003c0b8c68c3 in clone () from /lib64/tls/libc.so.6 Thread 7 (process 635): #0 0x0000003c0c7089ba in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/tls/libpthread.so.0 #1 0x0000002a956b24b0 in ldap_pvt_thread_cond_wait (cond=0x932030, mutex=0x932008) at thr_posix.c:277 #2 0x0000002a956b0fbf in ldap_int_thread_pool_wrapper (xpool=0x932000) at tpool.c:672 #3 0x0000003c0c70610a in start_thread () from /lib64/tls/libpthread.so.0 #4 0x0000003c0b8c68c3 in clone () from /lib64/tls/libc.so.6 Thread 6 (process 634): #0 0x0000003c0c7089ba in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/tls/libpthread.so.0 #1 0x0000002a956b24b0 in ldap_pvt_thread_cond_wait (cond=0x932030, mutex=0x932008) at thr_posix.c:277 #2 0x0000002a956b0fbf in ldap_int_thread_pool_wrapper (xpool=0x932000) at tpool.c:672 #3 0x0000003c0c70610a in start_thread () from /lib64/tls/libpthread.so.0 #4 0x0000003c0b8c68c3 in clone () from /lib64/tls/libc.so.6 Thread 5 (process 633): #0 0x0000003c0c7089ba in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/tls/libpthread.so.0 #1 0x0000002a956b24b0 in ldap_pvt_thread_cond_wait (cond=0x932030, mutex=0x932008) at thr_posix.c:277 #2 0x0000002a956b0fbf in ldap_int_thread_pool_wrapper (xpool=0x932000) at tpool.c:672 #3 0x0000003c0c70610a in start_thread () from /lib64/tls/libpthread.so.0 #4 0x0000003c0b8c68c3 in clone () from /lib64/tls/libc.so.6 Thread 4 (process 632): #0 0x0000003c0c7089ba in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/tls/libpthread.so.0 #1 0x0000002a956b24b0 in ldap_pvt_thread_cond_wait (cond=0x932030, mutex=0x932008) at thr_posix.c:277 #2 0x0000002a956b0fbf in ldap_int_thread_pool_wrapper (xpool=0x932000) at tpool.c:672 #3 0x0000003c0c70610a in start_thread () from /lib64/tls/libpthread.so.0 #4 0x0000003c0b8c68c3 in clone () from /lib64/tls/libc.so.6 Thread 3 (process 631): #0 0x0000003c0c7089ba in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/tls/libpthread.so.0 #1 0x0000002a956b24b0 in ldap_pvt_thread_cond_wait (cond=0x932030, mutex=0x932008) at thr_posix.c:277 #2 0x0000002a956b0fbf in ldap_int_thread_pool_wrapper (xpool=0x932000) at tpool.c:672 #3 0x0000003c0c70610a in start_thread () from /lib64/tls/libpthread.so.0 #4 0x0000003c0b8c68c3 in clone () from /lib64/tls/libc.so.6 Thread 2 (process 630): #0 0x0000003c0c7089ba in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/tls/libpthread.so.0 #1 0x0000002a956b24b0 in ldap_pvt_thread_cond_wait (cond=0x932030, mutex=0x932008) at thr_posix.c:277 #2 0x0000002a956b0fbf in ldap_int_thread_pool_wrapper (xpool=0x932000) at tpool.c:672 #3 0x0000003c0c70610a in start_thread () from /lib64/tls/libpthread.so.0 #4 0x0000003c0b8c68c3 in clone () from /lib64/tls/libc.so.6 Thread 1 (process 629): #0 0x0000003c0c70b04f in __write_nocancel () from /lib64/tls/libpthread.so.0 #1 0x0000000000431d3e in slap_sig_shutdown (sig=15) at daemon.c:2926 #2 <signal handler called> #3 0x0000003c0c70b04d in __write_nocancel () from /lib64/tls/libpthread.so.0 #4 0x000000000042d17d in slapd_clr_write (s=4113, wake=1) at daemon.c:951 #5 0x0000000000433ae8 in connection_wake_writers (c=0x1451ec0) at connection.c:778 #6 0x0000000000433c40 in connection_closing (c=0x1451ec0, why=0x4e3ee2 "slapd shutdown") at connection.c:806 #7 0x00000000004322bb in connections_shutdown () at connection.c:209 #8 0x0000000000431b31 in slapd_daemon_task (ptr=0x0) at daemon.c:2761 #9 0x0000003c0c70610a in start_thread () from /lib64/tls/libpthread.so.0 #10 0x0000003c0b8c68c3 in clone () from /lib64/tls/libc.so.6

1 0

Re: (ITS#6362) slapd 2.4.19 Segmentation fault under load
by mbackes＠symas.com 10 Nov '09

10 Nov '09

Hello, Aleksey. > Openldap 2.4.19 installed from freebsd ports. All configs in defauls > Freebsd 7.2 amd64 Slapd built with the "-g" flag and install with > the make install STRIP="" Okay. > Used backends db46-4.6.21.4, db47-4.7.25.4 latest from freebsd ports. > libdb-4.6.so.0 => /usr/local/lib/libdb-4.6.so.0 (0x800a97000) At the same time? Your ldd list below shows only berkeley db 4.6. These don't mix... > In slapd config added using hdb as backend and indexes. Testing > database consist of 1000 users accounts with minimum attributes. On > stress test load slapd Segmentation fault in 10-30 sec. What sort of operations? > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x803404560 (LWP 100116)] > 0x0000000802d5aa4b in hdb_idl_fetch_key (be=Error accessing memory > address > 0x7ffffd9f9f38: Bad s. > ) at idl.c:511 Does it always fail at the same location? How reproducible is this? Matthew Backes Symas Corporation mbackes(a)symas.com

1 0

(ITS#6371) problem with ber_flatten2
by dave.daugherty＠centrify.com 10 Nov '09

10 Nov '09

Full_Name: Dave Daugherty Version: 2.2.6 and 2.4.17 OS: RedHat EL3 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (63.170.119.248) We use ber_flatten2 in an unusual way, but I think this issue is generic int ber_flatten2( BerElement *ber, struct berval *bv, int alloc ) { /* copy the berval */ ber_len_t len = ber_pvt_ber_write( ber ); if ( alloc ) { bv->bv_val = (char *) ber_memalloc_x( len + 1, ber->ber_memctx ); if ( bv->bv_val == NULL ) { return -1; } AC_MEMCPY( bv->bv_val, ber->ber_buf, len ); } else { bv->bv_val = ber->ber_buf; } bv->bv_val[len] = '\0'; <- ???? bv->bv_len = len; The problem I have is a crash, because of the bv->bv_val[len] = \0 when alloc is set to zero, AND the buffer that was passed in was generated by ber_realloc, which did not leave an extra byte at the end, resulting in a write beyond the allocated memory block. The questions I have are: 1) Is the zero terminator really necessary? 2) If so, seems like it should only be done if we actually allocated a new buffer (which does leave one byte at the end).

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs