Re: (ITS#4226) cn=accesslog reporting that it is out of available lockers when only root entry exists

[quanah@stanford.edu]

--On Tuesday, November 29, 2005 9:02 AM +0000 openldap-its@OpenLDAP.org 
wrote:

This is apparently being caused by the syncrepl client.

If I stop slapd on the master and the replica, recover the DB on the 
master, and then restart the master I see:

ldap-test0:/db/accesslog# db_stat -C A
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Lock region parameters
locker table size: 1031, object table size: 1031, obj_off: 401064,
osynch_off: 0, locker_off: 392808, lsynch_off: 0, need_dd: 0

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
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
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Locks grouped by lockers
Locker   Mode      Count Status  ----------------- Object ---------------
       1 dd= 0 locks held 1    write locks 0
       1 READ          1 HELD    id2entry.bdb             handle        0

       2 dd= 0 locks held 0    write locks 0
       3 dd= 0 locks held 1    write locks 0
       3 READ          1 HELD    dn2id.bdb                handle        0

       4 dd= 0 locks held 0    write locks 0
       5 dd= 0 locks held 0    write locks 0
       6 dd= 0 locks held 0    write locks 0
       8 dd= 0 locks held 0    write locks 0
       9 dd= 0 locks held 1    write locks 0
       9 READ          1 HELD    entryCSN.bdb             handle        0

       a dd= 0 locks held 0    write locks 0
       b dd= 0 locks held 0    write locks 0
       d dd= 0 locks held 0    write locks 0
       e dd= 0 locks held 1    write locks 0
       e READ          1 HELD    objectClass.bdb          handle        0

       f dd= 0 locks held 0    write locks 0
      10 dd= 0 locks held 0    write locks 0
      11 dd= 0 locks held 1    write locks 0
      11 READ          1 HELD    reqStart.bdb             handle        0

      12 dd= 0 locks held 0    write locks 0
      13 dd= 0 locks held 0    write locks 0
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
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

       e READ          1 HELD    objectClass.bdb          handle        0

       9 READ          1 HELD    entryCSN.bdb             handle        0

      11 READ          1 HELD    reqStart.bdb             handle        0

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Memory free list
0xfed10004: 120796



As soon as the client is started up, I get into the same issue again.

--Quanah


--
Quanah Gibson-Mount
Principal Software Developer
ITSS/Shared Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html