Bug 911469
| Summary: | dse.ldif is 0 length after server kill or machine kill | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jiri Pallich <jpallich> |
| Component: | 389-ds-base | Assignee: | Rich Megginson <rmeggins> |
| Status: | CLOSED ERRATA | QA Contact: | Sankar Ramalingam <sramling> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.4 | CC: | abienven, dpal, jgalipea, jwest, lkrispen, mkubik, nhosoi, nkinder, pm-eus, rmeggins, tlavigne |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | 389-ds-base-1.2.11.15-12.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: | Environment: | ||
| Last Closed: | 2013-03-11 18:38:48 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: | 910581, 913156 | ||
| Bug Blocks: | |||
|
Description
Jiri Pallich
2013-02-15 06:32:52 UTC
Server [hp-ml370g5-01] is alive. Sending SIGKILL to PID [13887]. Server should be killed. Server successfully killed. Checking dse.ldif file [/etc/dirsrv/slapd-hp-ml370g5-01/dse.ldif] [/etc/dirsrv/slapd-hp-ml370g5-01/dse.ldif] has 2429 lines. TestCase [bug910581] result-> [PASS] $ rpm -qa 389* 389-ds-base-libs-1.2.11.15-12.el6_4.x86_64 389-ds-base-1.2.11.15-12.el6_4.x86_64 Checked both by automated test as well as force off of the testing machine. Marking verified. 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/RHSA-2013-0628.html |