Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 910581 - dse.ldif is 0 length after server kill or machine kill
dse.ldif is 0 length after server kill or machine kill
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
6.4
Unspecified Unspecified
urgent Severity high
: rc
: ---
Assigned To: Rich Megginson
Sankar Ramalingam
: ZStream
Depends On:
Blocks: 911469 913156
  Show dependency treegraph
 
Reported: 2013-02-12 16:51 EST by Nathan Kinder
Modified: 2013-11-21 16:04 EST (History)
5 users (show)

See Also:
Fixed In Version: 389-ds-base-1.2.11.15-14.el6_4
Doc Type: Bug Fix
Doc Text:
Previously, under certain conditions, the dse.ldif file had 0 bytes after a server termination or when the machine was powered off. Consequently, after the system was brought up, a DS or IdM system could be unable to restart, leading to production server outages. Now, the server mechanism by which the dse.ldif is written is more robust, and tries all available backup dse.ldif files, and outages no longer occur.
Story Points: ---
Clone Of:
: 913156 (view as bug list)
Environment:
Last Closed: 2013-11-21 16:04:15 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1653 normal SHIPPED_LIVE 389-ds-base bug fix update 2013-11-20 16:53:19 EST

  None (edit)
Description Nathan Kinder 2013-02-12 16:51:35 EST
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/518

Doing a kill -9 of ns-slapd, or doing a hard shutdown of a machine while ns-slapd is running, will cause a 0 length dse.ldif to be written
Comment 5 errata-xmlrpc 2013-11-21 16:04:15 EST
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-2013-1653.html

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