389-ds-base

#47934 nsslapd-db-locks modify not taking into account.
Closed: wontfix Opened by gparente.

Closed: wontfix
Reopen Issue

Reproduce it like this:

  • stop server

  • modify nsslapd-db-locks under "cn=config,cn=ldbm database,cn=plugins,cn=config"

  • restart server

  • search for

nsslapd-db-configured-locks under "cn=database,cn=monitor,cn=ldbm database,cn=plugins,cn=config"

and verify the number has not changed.

Furthermore,

db_stat -c -h /var/lib/dirsrv/slapd-server3/db/ | grep locks
40002 Maximum number of locks possible

Shows the older value. So, Berkeley db has never been set with the new value.

Workaround:

  • stop server

  • remove temporary files or guardian file (CONFIRM SERVER IS STOPPED):

  • rm /var/lib/dirsrv/slapd-server3/db/__db.00*
    or

  • rm /var/lib/dirsrv/slapd-server3/db/guardian

  • start server

  • search for

nsslapd-db-configured-locks under "cn=database,cn=monitor,cn=ldbm database,cn=plugins,cn=config"

and verify the number is the new one.

the changes in db lock configuration should be handled like changes in cache size. value should be stored in the guardian file. at startup, if a guardian file exists, the max locks should be compared with the configured locks and if they are different the env should be recreated

Reviewed by Mark (Thank you!!)

Pushed to master:
f724b34..f4437de master -> master
commit f4437defacf8812c5f95869147a99f8412dc4a07

Pushed to 389-ds-base-1.3.3:
87c7b15..dc4185e 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit dc4185ea40e1f1b8527a67a0c854fcc29b8bafe7

Pushed to 389-ds-base-1.3.2:
20cb0c0..d1e4698 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
commit d1e4698530868532bd472c70ca8ccc4a317b4199

Pushed to 389-ds-base-1.3.1:
bf27455..86b728f 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit 86b728f88fe0d35f403c012166f98c3a0e69ad32

Pushed to 389-ds-base-1.2.11:
6b85c3a..295cf31 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit 295cf31602797b09a3b7a7c7e8d2feb71017522b

Metadata Update from @nhosoi:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.2.11.33

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1265

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)
Metadata
None
None
None
High
ack
RHCust
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.