openldap-bugs December 2007

openldap-bugs@openldap.org

45 participants
166 discussions

Re: (ITS#5267) slapo-dds prevents slapd from starting in case of an empty DB
by ando＠sys-net.it 08 Dec '07

08 Dec '07

> bdb_dn2entry("ou=odd2006,dc=block-floete,dc=de") > => hdb_dn2id("ou=odd2006,dc=block-floete,dc=de") > <= hdb_dn2id: get failed: DB_NOTFOUND: No matching key/data pair found > (-30989) > send_ldap_result: conn=-1 op=0 p=0 > DDS expired objects lookup failed err=32 Makes sense to skip searching for expired entries in a non existing database... 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

(ITS#5267) slapo-dds prevents slapd from starting in case of an empty DB
by michael＠stroeder.com 08 Dec '07

08 Dec '07

Full_Name: Michael Ströder Version: HEAD OS: OpenSUSE Linux 10.2 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (83.124.3.18) Situation: 1. slapo-dds is defined for database ou=odd2006,dc=block-floete,dc=de in slapd.conf 2. entry ou=odd2006,dc=block-floete,dc=de does not yet exist => slapd does not start (see log below). For the ease of initial setup I'd prefer that slapd would start. bdb_dn2entry("ou=odd2006,dc=block-floete,dc=de") => hdb_dn2id("ou=odd2006,dc=block-floete,dc=de") <= hdb_dn2id: get failed: DB_NOTFOUND: No matching key/data pair found (-30989) send_ldap_result: conn=-1 op=0 p=0 DDS expired objects lookup failed err=32 backend_startup_one: bi_db_open failed! (1) slapd-odd2006 shutdown: initiated

1 0

Re: (ITS#5264) invalid printf of NULL
by hyc＠symas.com 07 Dec '07

07 Dec '07

Aaron Richton wrote: > "./run test044" is sufficient to reproduce 100% of the time. Maybe the > behavior's changed in S10 (or maybe gcc does some wrapping, I don't know) > but printf("%s", NULL) has been an instant SEGV in Sol9 as long as I can > remember... >>> (dbx) print assertDN->bv_val >>> assertDN->bv_val = (nil) >>> >>> don't do that... As I suspected, there's more wrong here than a bad printf argument. The assertDN should never be NULL. -- -- 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#5264) invalid printf of NULL
by hyc＠symas.com 07 Dec '07

07 Dec '07

Aaron Richton wrote: > "./run test044" is sufficient to reproduce 100% of the time. Maybe the > behavior's changed in S10 (or maybe gcc does some wrapping, I don't know) > but printf("%s", NULL) has been an instant SEGV in Sol9 as long as I can > remember... Yes, understood. That characteristic of Solaris hasn't changed. But test044 in HEAD exercises code that hasn't been included in RE24, and I was focusing on RE24. -- -- 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#5264) invalid printf of NULL
by richton＠nbcs.rutgers.edu 07 Dec '07

07 Dec '07

"./run test044" is sufficient to reproduce 100% of the time. Maybe the behavior's changed in S10 (or maybe gcc does some wrapping, I don't know) but printf("%s", NULL) has been an instant SEGV in Sol9 as long as I can remember... On Fri, 7 Dec 2007, Howard Chu wrote: > richton(a)nbcs.rutgers.edu wrote: >> Full_Name: Aaron Richton >> Version: HEAD >> OS: Solaris 9 >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (128.6.31.137) > > In a separate email you mentioned that you ran into this problem in > test044-dynlist. That test passes for me on Solaris 10/sparcv9. How exactly > did you get this to occur? > >> [5] slap_sasl_match(opx = 0x100a32c10, rule = 0x100a363e0, assertDN = >> 0x7fffffff7927c6c0, authc = 0x7fffffff7927c6c0), line 1668 in "saslauthz.c" >> >> 1660 struct berval base = BER_BVNULL; >> 1661 >> 1662 sm.dn = assertDN; >> 1663 sm.match = 0; >> 1664 cb.sc_private = &sm; >> 1665 >> 1666 Debug( LDAP_DEBUG_TRACE, >> 1667 "===>slap_sasl_match: comparing DN %s to rule %s\n", >> 1668 assertDN->bv_val, rule->bv_val, 0 ); >> 1669 >> 1670 /* NOTE: don't normalize rule if authz syntax is enabled */ >> >> (dbx) print assertDN->bv_val >> assertDN->bv_val = (nil) >> >> don't do that... >> >> >> . >> > > > -- > -- 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#5109) ldap_int_global_options not initialized
by lighthousej＠gmail.com 07 Dec '07

07 Dec '07

------=_Part_13800_24934559.1197042335995 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I think this issue is related to Oracle libraries. I got pretty much the same backtrace using openldap 2.3.32 with oracle 10g libs with my program. The code seems to want to copy an array of strings which contain attributes from the global variable. The problem is that the pointer to the attribute strings array isn't pointing to the address holding the first string pointer, it's actually pointing to the first character of a string. The code thinks the first four bytes (which are really the first four characters) is a memory address, tries to strlen that address and faults because it's out of bounds. I moved the oracle libs out of the way, soft symlinked the oracle filenames to zlib and the same exact binary worked fine. I'm trying out 2.4.6 right now but I wanted to relay this is potentially a bug related to including Oracle. ------=_Part_13800_24934559.1197042335995 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I think this issue is related to Oracle libraries. I got pretty much the same backtrace using openldap 2.3.32 with oracle 10g libs with my program. The code seems to want to copy an array of strings which contain attributes from the global variable.  The problem is that the pointer to the attribute strings array isn't pointing to the address holding the first string pointer, it's actually pointing to the first character of a string.  The code thinks the first four bytes (which are really the first four characters) is a memory address, tries to strlen that address and faults because it's out of bounds. I moved the oracle libs out of the way, soft symlinked the oracle filenames to zlib and the same exact binary worked fine. I'm trying out 2.4.6 right now but I wanted to relay this is potentially a bug related to including Oracle. ------=_Part_13800_24934559.1197042335995--

1 0

Re: (ITS#5264) invalid printf of NULL
by hyc＠symas.com 07 Dec '07

07 Dec '07

hyc(a)symas.com wrote: > richton(a)nbcs.rutgers.edu wrote: >> Full_Name: Aaron Richton >> Version: HEAD >> OS: Solaris 9 >> URL: ftp://ftp.openldap.org/incoming/ >> Submission from: (NULL) (128.6.31.137) > > In a separate email you mentioned that you ran into this problem in > test044-dynlist. That test passes for me on Solaris 10/sparcv9. How exactly > did you get this to occur? Never mind, I'm testing RE24, not HEAD. This part of dynlist isn't present in RE24. > >> [5] slap_sasl_match(opx = 0x100a32c10, rule = 0x100a363e0, assertDN = >> 0x7fffffff7927c6c0, authc = 0x7fffffff7927c6c0), line 1668 in "saslauthz.c" >> >> 1660 struct berval base = BER_BVNULL; >> 1661 >> 1662 sm.dn = assertDN; >> 1663 sm.match = 0; >> 1664 cb.sc_private = &sm; >> 1665 >> 1666 Debug( LDAP_DEBUG_TRACE, >> 1667 "===>slap_sasl_match: comparing DN %s to rule %s\n", >> 1668 assertDN->bv_val, rule->bv_val, 0 ); >> 1669 >> 1670 /* NOTE: don't normalize rule if authz syntax is enabled */ >> >> (dbx) print assertDN->bv_val >> assertDN->bv_val = (nil) >> >> don't do that... >> >> >> . >> > > -- -- 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#5259) SIGSEGV in slap_auxprop_store during SASL/OTP bind
by hyc＠symas.com 07 Dec '07

07 Dec '07

dwhite(a)olp.net wrote: > Full_Name: Dan White > Version: 2.3.39 > OS: Linux > URL: http://support.olp.net/ldap/log.txt > Submission from: (NULL) (65.161.252.42) Nice bit of debugging there. This could be a bit tricky because the slapd auxprop code assumes it's always executing on behalf of an LDAP operation (usually a Bind request). In this case, there is no active request; it's the cleanup action on a closed connection, and most of the state that slapd needed has already been torn down. It may take some restructuring to allow this to work, we never expected sasl_dispose() to be anything other than a pure destructor. > I'm experiencing crashes in slapd when attempting to bind via SASL using the OTP > mech. > > I'm using openldap version 2.3.39 for both slapd and my ldap utils (ldapsearch). > I'm using the bdb backend. > > I'm also using Debian Etch with the following versions of software: > > Cyrus SASL 2.1.22(.dfsg1-8) > libdb 4.2.52(+dfsg-2) > libc6 2.3.6(.ds1-13etch2) > > I've compiled cyrus sasl to use it's internal implementation of OTP, rather than > OPIE: > > --enable-otp > (--with-opie is not enabled) > > The problem I'm experiencing isn't when I successfully authenticate; that seems > to work fine. It's when I run an ldapsearch, but instead of entering an OTP > password, I press ctrl-c to cancel the search. > >>From the shell, when I perform an LDAP search, all appears normal: > > hiro:~# ldapsearch -Y OTP -U abrown(a)olp.net > SASL/OTP authentication started > Challenge: otp-md5 497 hi3182 ext > Please enter your one-time password:<ctrl-c> > hiro:~# > > However my slapd process dies. > > Here's a gdb backtrace of the server process: > > ... > Core was generated by `/usr/sbin/slapd'. > Program terminated with signal 11, Segmentation fault. > #0 0x080b448e in slap_auxprop_store (glob_context=0x0, sparams=0x820b2a0, > prctx=0x82351c0, user=0x820a148 "abrown(a)olp.net", ulen=14) > at > /usr/src/build/openldap/openldap2.3-2.3.39/servers/slapd/sasl.c:478 > 478 op.o_hdr = > conn->c_sasl_bindop->o_hdr; > (gdb) bt > #0 0x080b448e in slap_auxprop_store (glob_context=0x0, sparams=0x820b2a0, > prctx=0x82351c0, user=0x820a148 "abrown(a)olp.net", ulen=14) > at > /usr/src/build/openldap/openldap2.3-2.3.39/servers/slapd/sasl.c:478 > #1 0xb7eb17d7 in sasl_auxprop_store () from /usr/lib/libsasl2.so.2 > #2 0xb7973c89 in otp_server_plug_init () from /usr/lib/sasl2/libotp.so.2 > #3 0xb7ebde36 in sasl_server_new () from /usr/lib/libsasl2.so.2 > #4 0xb7eb6194 in sasl_dispose () from /usr/lib/libsasl2.so.2 > #5 0x080b2992 in slap_sasl_close (conn=0xb7ec3618) at > /usr/src/build/openldap/openldap2.3-2.3.39/servers/slapd/sasl.c:1331 > #6 0x0806cf27 in connection_close (c=0xb75b1148) at > /usr/src/build/openldap/openldap2.3-2.3.39/servers/slapd/connection.c:715 > #7 0x0806e116 in connection_read (s=12) at > /usr/src/build/openldap/openldap2.3-2.3.39/servers/slapd/connection.c:1458 > #8 0x0806a49f in slapd_daemon_task (ptr=0x0) at > /usr/src/build/openldap/openldap2.3-2.3.39/servers/slapd/daemon.c:2468 > #9 0xb7cd3240 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 > #10 0xb7c674ae in clone () from /lib/tls/i686/cmov/libc.so.6 > (gdb) quit > > I've added a debug statement within slap_auxprop_store, so the openldap debug > information below will include some additional information about what's being > modified. > > The output can be obtained from: > > http://support.olp.net/ldap/log.txt > > Notice the two lines: > > Dec 3 13:39:06 hiro slapd[11134]: slap_auxprop_store [conn=3]: Getting ready to > set cmusaslsecretOTP to > md5^I0499^Ihi5935^I0e81b33e30182715^I00000000001196711046. > Dec 3 13:39:07 hiro slapd[11134]: slap_auxprop_store [conn=-1]: Getting ready > to set cmusaslsecretOTP to > md5^I0499^Ihi5935^I0e81b33e30182715^I00000000000000000000. > > If I enter a good OTP password, I get this in my logs: > > Dec 3 13:43:26 hiro slapd[11159]: slap_auxprop_store [conn=3]: Getting ready to > set cmusaslsecretOTP to > md5^I0499^Ihi5865^Iec8123986aec6550^I00000000001196711306. > Dec 3 13:44:26 hiro slapd[11159]: slap_auxprop_store [conn=3]: Getting ready to > set cmusaslsecretOTP to > md5^I0498^Ihi5865^Ic3570f027cf46ed0^I00000000000000000000. > > If I enter an incorrect password, I get this: > > Dec 3 13:45:21 hiro slapd[11159]: slap_auxprop_store [conn=4]: Getting ready to > set cmusaslsecretOTP to > md5^I0498^Ihi5865^Ic3570f027cf46ed0^I00000000001196711421. > Dec 3 13:45:22 hiro slapd[11159]: slap_auxprop_store [conn=4]: Getting ready to > set cmusaslsecretOTP to > md5^I0498^Ihi5865^Ic3570f027cf46ed0^I00000000000000000000. > > So in the case where it's crashing, it appears the Cyrus SASL is attempting to > revert the OTP entry back to the previous version to "unlock" it. I assume that > the connection id of '-1' is relevant to the crash. -- -- 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#5264) invalid printf of NULL
by hyc＠symas.com 07 Dec '07

07 Dec '07

richton(a)nbcs.rutgers.edu wrote: > Full_Name: Aaron Richton > Version: HEAD > OS: Solaris 9 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (128.6.31.137) In a separate email you mentioned that you ran into this problem in test044-dynlist. That test passes for me on Solaris 10/sparcv9. How exactly did you get this to occur? > [5] slap_sasl_match(opx = 0x100a32c10, rule = 0x100a363e0, assertDN = > 0x7fffffff7927c6c0, authc = 0x7fffffff7927c6c0), line 1668 in "saslauthz.c" > > 1660 struct berval base = BER_BVNULL; > 1661 > 1662 sm.dn = assertDN; > 1663 sm.match = 0; > 1664 cb.sc_private = &sm; > 1665 > 1666 Debug( LDAP_DEBUG_TRACE, > 1667 "===>slap_sasl_match: comparing DN %s to rule %s\n", > 1668 assertDN->bv_val, rule->bv_val, 0 ); > 1669 > 1670 /* NOTE: don't normalize rule if authz syntax is enabled */ > > (dbx) print assertDN->bv_val > assertDN->bv_val = (nil) > > don't do that... > > > . > -- -- 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#5261) Samba4 can 'hang' OpenLDAP slapd
by abartlet＠samba.org 06 Dec '07

06 Dec '07

--=-ENBDdr/KGkLnrgJWYt0i Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2007-12-06 at 18:09 -0800, Howard Chu wrote: > db_stat -CA I've run this on all the databases. It seems clear to me the issue is with the 'user' db. [abartlet@naomi source]$ cd /home/data/samba/samba4/SAMBA_4_0/source/st/dc/private/ldap/db/user [abartlet@naomi user]$ db_stat -CA Default locking region information: 16 Last allocated locker ID 0x7fffffff Current maximum unused locker ID 9 Number of lock modes 1000 Maximum number of locks possible 1000 Maximum number of lockers possible 1000 Maximum number of lock objects possible 7 Number of current locks 11 Maximum number of locks at any one time 17 Number of current lockers 18 Maximum number of lockers at any one time 6 Number of current lock objects 9 Maximum number of lock objects at any one time 73 Total number of locks requested 66 Total number of locks released 0 Total number of locks upgraded 8 Total number of locks downgraded 1 Lock requests not available due to conflicts, for which we waited 0 Lock requests not available due to conflicts, for which we did not wait 0 Number of deadlocks 0 Lock timeout value 0 Number of locks that have timed out 0 Transaction timeout value 0 Number of transactions that have timed out 712KB The size of the lock region 0 The number of region locks that required waiting (0%) =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D Lock REGINFO information: Lock Region type 5 Region ID __db.005 Region name 0x2aaaaabef000 Original region address 0x2aaaaabef000 Region address 0x2aaaaabef068 Region primary address 0 Region maximum allocation 0 Region allocated Region allocations: 3005 allocations, 0 failures, 0 frees, 1 longest REGION_JOIN_OK Region flags =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D Lock region parameters: 163 Lock region region mutex [0/205 0% 360/46912496263136] 1031 locker table size 1031 object table size 584 obj_off 54296 locker_off 0 need_dd =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D Lock conflict matrix: 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 1 0 1 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 1 1 0 0 1 0 0 0 0 0 1 0 1 1 0 0 0 0 1 1 0 0 1 0 1 0 1 0 0 0 1 1 0 1 1 1 0 1 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D Locks grouped by lockers: Locker Mode Count Status ----------------- Object --------------- 1 dd=3D16 locks held 1 write locks 0 pid/thread 347/46912500832560 =20 1 READ 1 HELD id2entry.bdb handle 0 2 dd=3D15 locks held 0 write locks 0 pid/thread 347/46912500832560 =20 3 dd=3D14 locks held 1 write locks 0 pid/thread 347/46912500832560 =20 3 READ 1 HELD dn2id.bdb handle 0 4 dd=3D13 locks held 0 write locks 0 pid/thread 347/1090525520 =20 5 dd=3D12 locks held 0 write locks 0 pid/thread 347/46912500832560 =20 6 dd=3D11 locks held 0 write locks 0 pid/thread 347/46912500832560 =20 7 dd=3D10 locks held 0 write locks 0 pid/thread 347/46912500832560 =20 8 dd=3D 9 locks held 0 write locks 0 pid/thread 347/1090525520 =20 9 dd=3D 8 locks held 1 write locks 0 pid/thread 347/1090525520 =20 9 READ 1 HELD 0x59310 len: 9 data: 0x010000000000000000 a dd=3D 7 locks held 0 write locks 0 pid/thread 347/1107310928 =20 b dd=3D 6 locks held 1 write locks 0 pid/thread 347/1090525520 =20 b READ 1 HELD objectClass.bdb handle 0 c dd=3D 5 locks held 0 write locks 0 pid/thread 347/1090525520 =20 d dd=3D 4 locks held 0 write locks 0 pid/thread 347/1090525520 =20 e dd=3D 3 locks held 1 write locks 0 pid/thread 347/1090525520 =20 e READ 1 HELD objectCategory.bdb handle 0 f dd=3D 2 locks held 0 write locks 0 pid/thread 347/1090525520 =20 10 dd=3D 1 locks held 0 write locks 0 pid/thread 347/1090525520 =20 8000000b dd=3D 0 locks held 1 write locks 1 pid/thread 347/1090525520 =20 8000000b WRITE 1 WAIT 0x59310 len: 9 data: 0x010000000000000000 8000000b WRITE 1 HELD id2entry.bdb page 1 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D Locks grouped by object: Locker Mode Count Status ----------------- Object --------------- 8000000b WRITE 1 HELD id2entry.bdb page 1 1 READ 1 HELD id2entry.bdb handle 0 3 READ 1 HELD dn2id.bdb handle 0 b READ 1 HELD objectClass.bdb handle 0 e READ 1 HELD objectCategory.bdb handle 0 9 READ 1 HELD 0x59310 len: 9 data: 0x010000000000000000 8000000b WRITE 1 WAIT 0x59310 len: 9 data: 0x010000000000000000 [abartlet@naomi schema]$ pwd /home/data/samba/samba4/SAMBA_4_0/source/st/dc/private/ldap/db/schema [abartlet@naomi schema]$ db_stat -CA Default locking region information: 9 Last allocated locker ID 0x7fffffff Current maximum unused locker ID 9 Number of lock modes 1000 Maximum number of locks possible 1000 Maximum number of lockers possible 1000 Maximum number of lock objects possible 2 Number of current locks 4 Maximum number of locks at any one time 9 Number of current lockers 9 Maximum number of lockers at any one time 2 Number of current lock objects 4 Maximum number of lock objects at any one time 31 Total number of locks requested 29 Total number of locks released 0 Total number of locks upgraded 4 Total number of locks downgraded 0 Lock requests not available due to conflicts, for which we waited 0 Lock requests not available due to conflicts, for which we did not wait 0 Number of deadlocks 0 Lock timeout value 0 Number of locks that have timed out 0 Transaction timeout value 0 Number of transactions that have timed out 712KB The size of the lock region 0 The number of region locks that required waiting (0%) =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D Lock REGINFO information: Lock Region type 5 Region ID __db.005 Region name 0x2aaaaabef000 Original region address 0x2aaaaabef000 Region address 0x2aaaaabef068 Region primary address 0 Region maximum allocation 0 Region allocated Region allocations: 3016 allocations, 0 failures, 11 frees, 1 longest REGION_JOIN_OK Region flags =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D Lock region parameters: 163 Lock region region mutex [0/96 0% 363/46912496263136] 1031 locker table size 1031 object table size 584 obj_off 54296 locker_off 0 need_dd =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D Lock conflict matrix: 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 1 0 1 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 1 1 0 0 1 0 0 0 0 0 1 0 1 1 0 0 0 0 1 1 0 0 1 0 1 0 1 0 0 0 1 1 0 1 1 1 0 1 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D Locks grouped by lockers: Locker Mode Count Status ----------------- Object --------------- 1 dd=3D 0 locks held 1 write locks 0 pid/thread 347/46912500832560 =20 1 READ 1 HELD id2entry.bdb handle 0 2 dd=3D 0 locks held 0 write locks 0 pid/thread 347/46912500832560 =20 3 dd=3D 0 locks held 1 write locks 0 pid/thread 347/46912500832560 =20 3 READ 1 HELD dn2id.bdb handle 0 4 dd=3D 0 locks held 0 write locks 0 pid/thread 347/1098918224 =20 5 dd=3D 0 locks held 0 write locks 0 pid/thread 347/46912500832560 =20 6 dd=3D 0 locks held 0 write locks 0 pid/thread 347/46912500832560 =20 7 dd=3D 0 locks held 0 write locks 0 pid/thread 347/1090525520 =20 8 dd=3D 0 locks held 0 write locks 0 pid/thread 347/1090525520 =20 9 dd=3D 0 locks held 0 write locks 0 pid/thread 347/1098918224 =20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D Locks grouped by object: Locker Mode Count Status ----------------- Object --------------- 1 READ 1 HELD id2entry.bdb handle 0 3 READ 1 HELD dn2id.bdb handle 0 [abartlet@naomi config]$ pwd /home/data/samba/samba4/SAMBA_4_0/source/st/dc/private/ldap/db/config [abartlet@naomi config]$ db_stat -CA Default locking region information: 9 Last allocated locker ID 0x7fffffff Current maximum unused locker ID 9 Number of lock modes 1000 Maximum number of locks possible 1000 Maximum number of lockers possible 1000 Maximum number of lock objects possible 2 Number of current locks 4 Maximum number of locks at any one time 9 Number of current lockers 9 Maximum number of lockers at any one time 2 Number of current lock objects 4 Maximum number of lock objects at any one time 31 Total number of locks requested 29 Total number of locks released 0 Total number of locks upgraded 4 Total number of locks downgraded 0 Lock requests not available due to conflicts, for which we waited 0 Lock requests not available due to conflicts, for which we did not wait 0 Number of deadlocks 0 Lock timeout value 0 Number of locks that have timed out 0 Transaction timeout value 0 Number of transactions that have timed out 712KB The size of the lock region 0 The number of region locks that required waiting (0%) =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D Lock REGINFO information: Lock Region type 5 Region ID __db.005 Region name 0x2aaaaabef000 Original region address 0x2aaaaabef000 Region address 0x2aaaaabef068 Region primary address 0 Region maximum allocation 0 Region allocated Region allocations: 3016 allocations, 0 failures, 11 frees, 1 longest REGION_JOIN_OK Region flags =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D Lock region parameters: 163 Lock region region mutex [0/96 0% 366/46912496263136] 1031 locker table size 1031 object table size 584 obj_off 54296 locker_off 0 need_dd =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D Lock conflict matrix: 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 1 0 1 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 1 1 0 0 1 0 0 0 0 0 1 0 1 1 0 0 0 0 1 1 0 0 1 0 1 0 1 0 0 0 1 1 0 1 1 1 0 1 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D Locks grouped by lockers: Locker Mode Count Status ----------------- Object --------------- 1 dd=3D 0 locks held 1 write locks 0 pid/thread 347/46912500832560 =20 1 READ 1 HELD id2entry.bdb handle 0 2 dd=3D 0 locks held 0 write locks 0 pid/thread 347/46912500832560 =20 3 dd=3D 0 locks held 1 write locks 0 pid/thread 347/46912500832560 =20 3 READ 1 HELD dn2id.bdb handle 0 4 dd=3D 0 locks held 0 write locks 0 pid/thread 347/1115703632 =20 5 dd=3D 0 locks held 0 write locks 0 pid/thread 347/46912500832560 =20 6 dd=3D 0 locks held 0 write locks 0 pid/thread 347/46912500832560 =20 7 dd=3D 0 locks held 0 write locks 0 pid/thread 347/1090525520 =20 8 dd=3D 0 locks held 0 write locks 0 pid/thread 347/1090525520 =20 9 dd=3D 0 locks held 0 write locks 0 pid/thread 347/1115703632 =20 =3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D Locks grouped by object: Locker Mode Count Status ----------------- Object --------------- 1 READ 1 HELD id2entry.bdb handle 0 3 READ 1 HELD dn2id.bdb handle 0 --=20 Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc. --=-ENBDdr/KGkLnrgJWYt0i Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD4DBQBHWLFwz4A8Wyi0NrsRAsZVAJi3+Vq41t9uwEfIKjzPFyzEUIOBAJ9B744l fc4tt0W/CKELwgwaxKzTxw== =5an3 -----END PGP SIGNATURE----- --=-ENBDdr/KGkLnrgJWYt0i--

1 0

← Newer
1
...
8
9
10
11
12
13
14
...
17
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs December 2007