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.
Bug 1476162 - Change the retrochangelog default cache size. And also if possible, the default caches. [rhel-7.4.z]
Summary: Change the retrochangelog default cache size. And also if possible, the defau...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.4
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: mreynolds
QA Contact: Viktor Ashirov
Marc Muehlfeld
URL:
Whiteboard:
Depends On: 1466191
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-28 07:45 UTC by Oneata Mircea Teodor
Modified: 2022-07-09 08:51 UTC (History)
8 users (show)

Fixed In Version: 389-ds-base-1.3.6.1-17.el7
Doc Type: Bug Fix
Doc Text:
Due to a low default entry cache size value, the Directory Server database had to resolve many deadlocks during resource-intensive tasks. In certain situations, this could result in a "DB PANIC" error and the server no longer responded to requests. After the server was restarted, Directory Server started with a delay to recover the database. However, this recovery could fail, and the database could corrupt. This patch increases the default entry cache size in the nsslapd-cachememsize parameter to 200 MB. As a result, out-of-lock situations or "DB PANIC" errors no longer occur in the mentioned scenario.
Clone Of: 1466191
Environment:
Last Closed: 2017-09-05 11:23:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:2569 0 normal SHIPPED_LIVE Moderate: 389-ds-base security and bug fix update 2017-09-05 15:16:55 UTC

Description Oneata Mircea Teodor 2017-07-28 07:45:11 UTC 
This bug has been copied from bug #1466191 and has been proposed to be backported to 7.4 z-stream (EUS).
Comment 4 Viktor Ashirov 2017-08-14 12:07:15 UTC 
Build tested:
389-ds-base-1.3.6.1-18.el7_4.x86_64

# ldapmodify -D cn=Directory\ Manager -w Secret123 
dn: cn=Retro Changelog Plugin,cn=plugins,cn=config
changetype: modify
replace: nsslapd-pluginEnabled
nsslapd-pluginEnabled: on

modifying entry "cn=Retro Changelog Plugin,cn=plugins,cn=config"

# restart-dirsrv 
Restarting instance "standalone"

# ldapsearch -LLLx -D cn=Directory\ Manager -w Secret123 -s base -b 'cn=changelog,cn=ldbm database,cn=plugins,cn=config' nsslapd-cachememsize
dn: cn=changelog,cn=ldbm database,cn=plugins,cn=config
nsslapd-cachememsize: 209715200

Previously the default value of nsslapd-cachememsize was 2097152, now it's 100x times bigger. Marking as VERIFIED.
Comment 6 errata-xmlrpc 2017-09-05 11:23:30 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:2569
Note You need to log in before you can comment on or make changes to this bug.