Bug 1568462 – disk monitoring setting the wrong default error log level

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1568462 - disk monitoring setting the wrong default error log level

Summary:	disk monitoring setting the wrong default error log level

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	389-ds-base (Show other bugs)
Sub Component:
Version:	7.5
Hardware:	x86_64 Linux

Priority	unspecified Severity high
Target Milestone:	rc
Target Release:	---
Assigned To:	mreynolds
QA Contact:	RHDS QE
Docs Contact:	Marc Muehlfeld

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-04-17 10:44 EDT by Amita Sharma
Modified:	2018-10-30 06:14 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:	389-ds-base-1.3.8.4-1.el7
Doc Type:	Bug Fix
Doc Text:	The Disk Monitoring feature shuts down Directory Server on low disk space Due to changes in the way Directory Server sets the error log level, the Disk Monitoring feature in Directory Server failed to detect that the error log level was set to the default level. As a consequence, Directory Server did not correctly shut down when the file system was full. The way the Disk Monitoring feature checks the error level has been updated. As a result, Disk Monitoring now correctly shuts down the server if the disk space is low.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-10-30 06:13:48 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2018:3127	None	None	None	2018-10-30 06:14 EDT

Groups: None (edit)

Comment 2 mreynolds 2018-04-17 10:48:18 EDT

Problem is that we are using SLAPD_DEFAULT_ERRORLOG_LEVEL instead of 16384

Comment 3 mreynolds 2018-04-27 11:10:01 EDT

Upstream ticket:
https://pagure.io/389-ds-base/issue/49654

Comment 4 mreynolds 2018-06-21 09:19:40 EDT

Really this has been fixed in:

https://pagure.io/389-ds-base/issue/49734

Comment 11 errata-xmlrpc 2018-10-30 06:13:48 EDT

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-2018:3127

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