How to increase the number of DB locks on the 389 Directory

[Glenn Machin]

I am getting the error below form my Version 1.2.8.2 (Build 
2011.104.231) 389 Directory Server:
"libdb: Lock table is out of available locks"

The cn=database,cn=monitor,cn=ldbm database, cn=plugins,cn=config show 
the following:

    nsslapd-db-configured-locks: 10000
    nsslapd-db-current-locks: 40
    nsslapd-db-max-locks: 10000


Its clear I am reaching the max number of locks of 10000.   However I 
don't know how to increase the value of nsslapd-db-configured-locks


The RedHat Directory documentation talks about increasing the value 
through the attribute:
|cn=config,cn=ldbm database,cn=plugins,cn=config : nsslapd-db-locks

However this did not origiinally exist and even when it was added it did 
not change the value of |nsslapd-db-configured-locks


How do I increase the value of nsslapd-db-configured-locks?


Thanks for any help you can provide.


Glenn

|
||
|

[Glenn Machin]

Looking at the source code - I fixed the problem by doing the 
following.   If there is an easier way let me know.

Shutdown down the 389 directory

Edited /etc/dirsrv/slapd-SERVER/dse.ldif

Under dn: cn=config,cn=ldbm database,cn=plugins,cn=config
added attribute:
nsslapd-db-locks: 40000


Dumped the userRoot DB
/usr/lib64/dirsrv/slapd-SERVER/db2ldif -n userRoot

(Note this starts slapd so you have to stop the server again)

Reload userRoot
/usr/lib64/dirsrv/slapd-SERVER/ldif2db -n userRoot -i 
/var/lib/dirsrv/slapd-SERVER/ldif/SERVER-userRoot-DATE.ldif

Start the server

Looked at the configuration attributes:
ldapsearch -h localhost -p 389 -D "cn=directory manager" -W -x -b 
"cn=database,cn=monitor,cn=ldbm database, cn=plugins,cn=config" 
objectclass=* | grep lock


nsslapd-db-configured-locks is now set to 40000



Glenn


On 6/14/11 8:29 AM, Glenn Machin wrote:
>  I am getting the error below form my Version 1.2.8.2 (Build 
>  2011.104.231) 389 Directory Server:
>  "libdb: Lock table is out of available locks"
>
>  The cn=database,cn=monitor,cn=ldbm database, cn=plugins,cn=config show 
>  the following:
>
>      nsslapd-db-configured-locks: 10000
>      nsslapd-db-current-locks: 40
>      nsslapd-db-max-locks: 10000
>
>
>  Its clear I am reaching the max number of locks of 10000.   However I 
>  don't know how to increase the value of nsslapd-db-configured-locks
>
>
>  The RedHat Directory documentation talks about increasing the value 
>  through the attribute:
>  |cn=config,cn=ldbm database,cn=plugins,cn=config : nsslapd-db-locks
>
>  However this did not origiinally exist and even when it was added it 
>  did not change the value of |nsslapd-db-configured-locks
>
>
>  How do I increase the value of nsslapd-db-configured-locks?
>
>
>  Thanks for any help you can provide.
>
>
>  Glenn
>
>  |
>  ||
>  |
>
>
>  --
>  389 users mailing list
>  389-users(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/389-users

[Rich Megginson]

On 06/14/2011 11:03 AM, Glenn Machin wrote:
>  Looking at the source code - I fixed the problem by doing the 
>  following.   If there is an easier way let me know.
>
>  Shutdown down the 389 directory
>
>  Edited /etc/dirsrv/slapd-SERVER/dse.ldif
>
>  Under dn: cn=config,cn=ldbm database,cn=plugins,cn=config
>  added attribute:
>  nsslapd-db-locks: 40000
>
>
>  Dumped the userRoot DB
>  /usr/lib64/dirsrv/slapd-SERVER/db2ldif -n userRoot
>
>  (Note this starts slapd so you have to stop the server again) 
starts slapd?  Note
that db2ldif runs ns-slapd in database export mode - 
it's the same ns-slapd, but it doesn't run it in a mode that it acts as 
an LDAP server serving client connections.
>  Reload userRoot
>  /usr/lib64/dirsrv/slapd-SERVER/ldif2db -n userRoot -i 
>  /var/lib/dirsrv/slapd-SERVER/ldif/SERVER-userRoot-DATE.ldif 
Was it really necessary
to dump and reload the db?  I would have thought 
just
1) stop the server
2) edit dse.ldif
3) start the server
>  Start the server
>
>  Looked at the configuration attributes:
>  ldapsearch -h localhost -p 389 -D "cn=directory manager" -W -x -b 
>  "cn=database,cn=monitor,cn=ldbm database, cn=plugins,cn=config" 
>  objectclass=* | grep lock
>
>
>  nsslapd-db-configured-locks is now set to 40000
>
>
>
>  Glenn
>
>
>  On 6/14/11 8:29 AM, Glenn Machin wrote:
> > I am getting the error below form my Version 1.2.8.2 (Build 
> > 2011.104.231) 389 Directory Server:
> > "libdb: Lock table is out of available locks"
> >
> > The cn=database,cn=monitor,cn=ldbm database, cn=plugins,cn=config 
> > show the following:
> >
> >     nsslapd-db-configured-locks: 10000
> >     nsslapd-db-current-locks: 40
> >     nsslapd-db-max-locks: 10000
> >
> >
> > Its clear I am reaching the max number of locks of 10000.   However I 
> > don't know how to increase the value of nsslapd-db-configured-locks
> >
> >
> > The RedHat Directory documentation talks about increasing the value 
> > through the attribute:
> > |cn=config,cn=ldbm database,cn=plugins,cn=config : nsslapd-db-locks
> >
> > However this did not origiinally exist and even when it was added it 
> > did not change the value of |nsslapd-db-configured-locks
> >
> >
> > How do I increase the value of nsslapd-db-configured-locks?
> >
> >
> > Thanks for any help you can provide.
> >
> >
> > Glenn
> >
> > |
> > ||
> > |
> >
> >
> > --
> > 389 users mailing list
> > 389-users(a)lists.fedoraproject.org
> > https://admin.fedoraproject.org/mailman/listinfo/389-users
>
>
>  --
>  389 users mailing list
>  389-users(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/389-users