Bug 1883708

Summary: tune nsslapd-db-locks in 10-config.update
Product: Red Hat Enterprise Linux 8 Reporter: Marc Sauton <msauton>
Component: ipaAssignee: Thomas Woerner <twoerner>
Status: CLOSED DUPLICATE QA Contact: ipa-qe <ipa-qe>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.2CC: fcami, ksiddiqu, rcritten, tscherf
Target Milestone: rc   
Target Release: 8.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 13:05:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Marc Sauton 2020-09-29 23:33:17 UTC 
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:
Comment 1 Rob Crittenden 2020-09-30 00:19:38 UTC 
In other words, if it is the default 10000 then bump it up to 50k, correct?
Comment 2 Kaleem 2020-09-30 07:54:33 UTC 
(In reply to Rob Crittenden from comment #1)
> In other words, if it is the default 10000 then bump it up to 50k, correct?

Is this not being taken care of in https://bugzilla.redhat.com/show_bug.cgi?id=1882340 ?
Comment 4 Rob Crittenden 2020-09-30 14:22:51 UTC 
Yes, exactly. That is why I was trying to get clarification on the request.
Comment 7 François Cami 2020-10-27 13:05:00 UTC 

*** This bug has been marked as a duplicate of bug 1882340 ***
Comment 8 Red Hat Bugzilla 2023-09-14 06:08:56 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days