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 1109352 - Tombstone purging can crash the server if the backend is stopped/disabled
Summary: Tombstone purging can crash the server if the backend is stopped/disabled
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base
Version: 6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Sankar Ramalingam
URL:
Whiteboard:
Depends On:
Blocks: 1109354
TreeView+ depends on / blocked
 
Reported: 2014-06-13 18:03 UTC by Noriko Hosoi
Modified: 2020-09-13 21:02 UTC (History)
4 users (show)

Fixed In Version: 389-ds-base-1.2.11.15-34.el6
Doc Type: Bug Fix
Doc Text:
Cause: The tomstone purge thread issues a callback search that will start reading id2entry, even if the backend is stopped. Consequence: This can crash the server. Fix: When performing a search and returning entries, check if the backend is started before reading id2entry. Result: Even if the tombstone purge occurs while the backend is stopped, the server does not crash.
Clone Of:
: 1109354 (view as bug list)
Environment:
Last Closed: 2014-10-14 07:55:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1098 0 None None None 2020-09-13 21:02:12 UTC
Red Hat Product Errata RHBA-2014:1385 0 normal SHIPPED_LIVE 389-ds-base bug fix and enhancement update 2014-10-14 01:27:42 UTC

Description Noriko Hosoi 2014-06-13 18:03:28 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47766

If the tombstone purging thread fires up while a backend has an online import occurring(backend state is STOPPED), the server will crash.

Comment 1 Noriko Hosoi 2014-06-17 18:11:51 UTC
STEPS:

Set up MMR.

Add large enough number of entries (e.g., 100KB) to make sure the future consumer initialization takes enough time to have tombstone purging while the initialization is running.

Set small number (e.g., 10 sec) to these config params on all the servers.
nsds5ReplicaPurgeDelay
nsds5ReplicaTombstonePurgeInterval

Delete some entries.

Restart the server.

Run consumer initialization.

If the initialization is successfully done, the fix is verified.

Comment 4 errata-xmlrpc 2014-10-14 07:55:26 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.

http://rhn.redhat.com/errata/RHBA-2014-1385.html


Note You need to log in before you can comment on or make changes to this bug.