Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
customer's system are often updated for years, instead of adding fresh and clean and up to date RHEL-8 and RHEL-7 systems into an IdM topology.
this often result in some parameters that are no long properly tuned as databases and usage grow overtime.
one example is the IPA LDAP server with the configuration parameter called nsslapd-db-locks.
there has been a customer case and situation with an updated system to RHEL-7.8, but carrying an older setting.
dn: cn=config,cn=ldbm database,cn=plugins,cn=config
nsslapd-db-locks: 10000
the newer default had been 50K in RHEL-8.2 and RHEL-7.8
so the file
/usr/share/ipa/updates/10-config.update
could re-tune
dn: cn=config,cn=ldbm database,cn=plugins,cn=config
nsslapd-db-locks: 50000
but on the other hand, this may overwrite those deployments that had been manually tuned with higher values like 100 or 200K dblocks
the symptom is typically an IPA LDAP error with this string:
id2entry - db error 12 (Cannot allocate memory)
Version-Release number of selected component (if applicable):
RHEL-8
RHEL-7
389-ds-base
How reproducible:
N/A , this is about old configurations carried overtime by RHEL IdM application successive updates
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info: