Bug 1109352

Summary:	Tombstone purging can crash the server if the backend is stopped/disabled
Product:	Red Hat Enterprise Linux 6	Reporter:	Noriko Hosoi <nhosoi>
Component:	389-ds-base	Assignee:	Noriko Hosoi <nhosoi>
Status:	CLOSED ERRATA	QA Contact:	Sankar Ramalingam <sramling>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0	CC:	jgalipea, mkubik, nkinder, rmeggins
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:
Clones:	1109354 (view as bug list)		Environment:
Last Closed:	2014-10-14 07:55:26 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:	1109354

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