-
Bug
-
Resolution: Done-Errata
-
Undefined
-
rhel-9.6
-
None
-
389-ds-base-2.6.1-11.el9_6
-
No
-
Low
-
rhel-idm-ds
-
0
-
False
-
False
-
-
None
-
None
-
Pass
-
Automated
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
The healthcheck tool is reporting errors about some LMDB parameters when the LDAP server is configured to use LMDB.
# dsconf <INSTANCE> backend config get | grep implement:
nsslapd-backend-implement: mdb
#
# dsctl <INSTANCE> healthcheck
...
[1] DS Lint Error: DSBLE0005
--------------------------------------------------------------------------------
Severity: LOW
Affects:
-- nsslapd-mdb-max-size
-- nsslapd-mdb-max-readers
-- nsslapd-mdb-max-dbsDetails:
-----------
Found configuration attributes that are not applicable for the configured backend type.Resolution:
-----------
Review the backend configuration and remove or adjust the incorrect attributes.
...
#
What is the impact of this issue to you?
Getting error messages about needed parameters.
Please provide the package NVR for which the bug is seen:
# rpm -qa | grep ^389-ds 389-ds-base-libs-2.6.1-9.el9_6.x86_64 389-ds-base-2.6.1-9.el9_6.x86_64 #
How reproducible is this bug?:
Always.
Steps to reproduce
- Enable LDMB
- Run the LDAP healthcheck
Expected results
Working command.
Actual results
Getting errors.
- links to
-
RHBA-2025:154222
389-ds-base update
