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.

Bug 1244970

Summary:	Crash while triming the retro changelog
Product:	Red Hat Enterprise Linux 6	Reporter:	Noriko Hosoi <nhosoi>
Component:	389-ds-base	Assignee:	Noriko Hosoi <nhosoi>
Status:	CLOSED ERRATA	QA Contact:	Viktor Ashirov <vashirov>
Severity:	high	Docs Contact:	Petr Bokoc <pbokoc>
Priority:	medium
Version:	6.0	CC:	jgalipea, mreynolds, nkinder, pbokoc, rmeggins, spichugi
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.2.11.15-67.el6	Doc Type:	Bug Fix
Doc Text:	Fixed a crash while trimming the retro changelog When trimming the retro changelog (`retroCL`), entries are first deleted from the changelog itself and then also from the cache. The 389-ds-base server was, however, missing a check to verify that the entries are actually present in the cache, which could lead to the server attempting to delete nonexistent entries and subsequently crash on systems where not all changelog entries could fit in the cache due to its small size. A check has been added to make sure only entries actually present in the cache are being deleted, and the server no longer crashes when trimming the retro changelog.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-10 19:19:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1272422

Description Noriko Hosoi 2015-07-20 22:27:22 UTC

When trimming the retroCL, it deletes an entry. Then retrieve the entry from the cache (no creation of tombstone) to remove it from the cache.
Apparently if the entry cachen is small, it can fail to retrieve it and not testing this special condition

Comment 1 mreynolds 2015-07-20 22:51:22 UTC

Fixed upstream

Comment 2 mreynolds 2015-07-21 13:47:53 UTC

Verification steps:

[1] Enable retro changelog plugin and set the retro changelog max age:

ldapmodify ....
dn: cn=retro changelog plugin,cn=plugins,cn=config
changetype: modify
replace: nsslapd-pluginEnabled
nsslapd-pluginEnabled: on
-
replace: nsslapd-changelogmaxage
nsslapd-changelogmaxage: 30

[2] Restart the server
[3] Set a very small entry cache size for the retro changelog backend

ldapmodify
dn: cn=changelog,cn=ldbm database,cn=plugins,cn=config
changetype: modify
replace: nsslapd-cachememsize
nsslapd-cachememsize: 512000

[4] Restart the server
[5] Add 2000 entries
[6] Wait 31 seconds
[7] Make sure server is still running(or did not crash during the adds)

Comment 4 Simon Pichugin 2016-03-22 17:00:15 UTC

Built tested:
389-ds-base-1.2.11.15-74.el6.x86_64

[1] Enable retro changelog plugin and set the retro changelog max age:
ldapmodify -D "cn=Directory Manager" -w Secret123 -h localhost -p 389 -x
dn: cn=retro changelog plugin,cn=plugins,cn=config
changetype: modify
replace: nsslapd-pluginEnabled
nsslapd-pluginEnabled: on
-
replace: nsslapd-changelogmaxage
nsslapd-changelogmaxage: 30

[2] Restart the server
sudo restart-dirsrv

[3] Set a very small entry cache size for the retro changelog backend
ldapmodify -D "cn=Directory Manager" -w Secret123 -h localhost -p 389 -x
dn: cn=changelog,cn=ldbm database,cn=plugins,cn=config
changetype: modify
replace: nsslapd-cachememsize
nsslapd-cachememsize: 512000

[4] Restart the server
sudo restart-dirsrv

[5] Add 2000 entries
ldclt -h localhost -p 389 -D "cn=Directory Manager" -w Secret123 -f cn=MrXXXX -b "dc=example,dc=com" -e add,person,incr,noloop,commoncounter -r1 -R2000

[6] Wait 31 seconds

[7] Make sure server is still running(or did not crash during the adds)
ldapsearch  -D "cn=Directory Manager" -w Secret123 -h localhost -p 389 -x -b "dc=example,dc=com" cn=Mr2000
# extended LDIF
#
# LDAPv3
# base <dc=example,dc=com> with scope subtree
# filter: cn=Mr2000
# requesting: ALL
#

# Mr2000, example.com
dn: cn=Mr2000,dc=example,dc=com
objectClass: person
objectClass: top
cn: Mr2000
sn: toto sn

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1

Marking as verified.

Comment 6 errata-xmlrpc 2016-05-10 19:19:56 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://rhn.redhat.com/errata/RHBA-2016-0737.html