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 1109354 - 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 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On: 1109352
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-13 18:04 UTC by Noriko Hosoi
Modified: 2020-09-13 21:02 UTC (History)
3 users (show)

Fixed In Version: 389-ds-base-1.3.3.1-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of: 1109352
Environment:
Last Closed: 2015-03-05 09:35:23 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:07 UTC
Red Hat Product Errata RHSA-2015:0416 0 normal SHIPPED_LIVE Important: 389-ds-base security, bug fix, and enhancement update 2015-03-05 14:26:33 UTC

Description Noriko Hosoi 2014-06-13 18:04:59 UTC 
+++ This bug was initially created as a clone of Bug #1109352 +++

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 2 Jenny Severance 2014-10-23 14:29:09 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 3 Viktor Ashirov 2014-12-10 16:44:45 UTC 
$ rpm -qa  | grep 389
389-ds-base-1.3.3.1-9.el7.x86_64
389-ds-base-debuginfo-1.3.3.1-9.el7.x86_64
389-ds-base-libs-1.3.3.1-9.el7.x86_64

I followed the steps in c#2, added 100k entries, deleted 1k, restarted the server and ran consumer initialization: 

[10/Dec/2014:17:35:24 +0100] - import userRoot: Processed 37314 entries -- average rate 1865.7/sec, recent rate 1865.7/sec, hit ratio 0%
[10/Dec/2014:17:35:49 +0100] - import userRoot: Processed 72966 entries -- average rate 1621.5/sec, recent rate 1621.4/sec, hit ratio 100%
[10/Dec/2014:17:36:05 +0100] - import userRoot: Workers finished; cleaning up...
[10/Dec/2014:17:36:06 +0100] - import userRoot: Workers cleaned up.
[10/Dec/2014:17:36:06 +0100] - import userRoot: Indexing complete.  Post-processing...
[10/Dec/2014:17:36:06 +0100] - import userRoot: Generating numsubordinates (this may take several minutes to complete)...
[10/Dec/2014:17:36:06 +0100] - import userRoot: Generating numSubordinates complete.
[10/Dec/2014:17:36:06 +0100] - import userRoot: Gathering ancestorid non-leaf IDs...
[10/Dec/2014:17:36:06 +0100] - import userRoot: Finished gathering ancestorid non-leaf IDs.
[10/Dec/2014:17:36:06 +0100] - import userRoot: Creating ancestorid index (new idl)...
[10/Dec/2014:17:36:06 +0100] - import userRoot: Created ancestorid index (new idl).
[10/Dec/2014:17:36:10 +0100] - import userRoot: Flushing caches...
[10/Dec/2014:17:36:10 +0100] - import userRoot: Closing files...
[10/Dec/2014:17:36:11 +0100] - import userRoot: Import complete.  Processed 100018 entries in 68 seconds. (1470.85 entries/sec)

Replica was successfully initialized, served didn't crash. Marking as VERIFIED.
Comment 5 errata-xmlrpc 2015-03-05 09:35:23 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/RHSA-2015-0416.html
Note You need to log in before you can comment on or make changes to this bug.