It seems if one configures 389ds 2.x instance with mdb backend, one loses the ability to run "dsconf <instance> monitor dbmon", with "Error: list index out of range". This is a known issue: https://github.com/389ds/389-ds-base/issues/6614 .
"dsconf <instance> monitor ldbm" appears to provide some of the same information, in particular with normalizeddncachehitratio, but not necessarily for the backend entry cache information, or am I mistaken? Outside of upgrading to the latest version, is there an alternative means of retrieving the same information that "monitor dbmon" provides? Or, should I stick to bdb until I get around to upgrading to 389ds 3.x? This issue observed with: % rpm -qi 389-ds|head -n3 Name : 389-ds Version : 2.5.3~git144.95b15d57c Release : 150700.3.6.1 on SLES15_sp7 % dsconf dev backend config get |grep nsslapd-backend-implement nsslapd-backend-implement: mdb % dsconf dev monitor dbmon Error: list index out of range Thanks, Bob -- _______________________________________________ 389-users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
