Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1523507 - IPA server replication broken, after DS stop-start, due to changelog reset [rhel-7.4.z]
IPA server replication broken, after DS stop-start, due to changelog reset [r...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
7.1
All Linux
urgent Severity urgent
: rc
: ---
Assigned To: mreynolds
Viktor Ashirov
Marc Muehlfeld
: ZStream
Depends On: 1192099
Blocks:
  Show dependency treegraph
 
Reported: 2017-12-08 02:38 EST by Oneata Mircea Teodor
Modified: 2018-01-25 07:22 EST (History)
12 users (show)

See Also:
Fixed In Version: 389-ds-base-1.3.6.1-25.el7_4
Doc Type: Bug Fix
Doc Text:
Previously, if Directory Server was stopped during an operation which created additional changes in the memory changelog, the Replication Update Vector (RUV) in the changelog was higher than the RUV in the database. As a consequence, Directory Server recreated the changelog when the server started. With this update, the server now writes the highest RUV to the changelog only if there is the highest Change Sequence Number (CSN) present in it. As a result, the database and the changelog RUV are consistent and the server does not need recreating the changelog at start up.
Story Points: ---
Clone Of: 1192099
Environment:
Last Closed: 2018-01-25 07:22:50 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 RHSA-2018:0163 normal SHIPPED_LIVE Important: 389-ds-base security and bug fix update 2018-01-25 11:21:13 EST

  None (edit)
Description Oneata Mircea Teodor 2017-12-08 02:38:06 EST
This bug has been copied from bug #1192099 and has been proposed to be backported to 7.4 z-stream (EUS).
Comment 2 Ludwig 2017-12-08 10:47:35 EST
backport completed
Comment 3 Ludwig 2017-12-08 10:53:17 EST
backport committed upstream
Comment 6 Amita Sharma 2018-01-04 04:43:17 EST
[root@qeos-14 export]# rpm -qa | grep 389
389-ds-base-snmp-1.3.6.1-25.el7_4.x86_64
389-ds-base-1.3.6.1-25.el7_4.x86_64
389-ds-base-libs-1.3.6.1-25.el7_4.x86_64
389-ds-base-debuginfo-1.3.6.1-25.el7_4.x86_64

Executing https://bugzilla.redhat.com/show_bug.cgi?id=1192099#c30 gives ::

[04/Jan/2018:04:41:11.517749394 -0500] - INFO - slapd_daemon - slapd shutting down - waiting for 1 thread to terminate
[04/Jan/2018:04:41:11.528844230 -0500] - ERR - memberof-plugin - memberof_postop_add - Failed to add dn(cn=test_Group3,dc=example,dc=com), error (-1)
[04/Jan/2018:04:41:11.556560165 -0500] - INFO - slapd_daemon - slapd shutting down - closing down internal subsystems and plugins
[04/Jan/2018:04:41:11.763525799 -0500] - ERR - NSMMReplicationPlugin - changelog program - _cl5WriteRUV - changelog maxRUV not found in changelog for file /var/lib/dirsrv/slapd-master1/changelogdb/a7dc180a-f13111e7-ac9cb6db-362b3857_5a4df3cb000000010000.db
[04/Jan/2018:04:41:11.768375858 -0500] - INFO - dblayer_pre_close - Waiting for 4 database threads to stop
[04/Jan/2018:04:41:12.065174442 -0500] - INFO - dblayer_pre_close - All database threads now stopped
[04/Jan/2018:04:41:12.076699068 -0500] - INFO - ldbm_back_instance_set_destructor - Set of instances destroyed
[04/Jan/2018:04:41:12.078359848 -0500] - INFO - connection_post_shutdown_cleanup - slapd shutting down - freed 1 work q stack objects - freed 1 op stack objects
[04/Jan/2018:04:41:12.113092100 -0500] - INFO - main - slapd stopped.
[04/Jan/2018:04:41:12.257476118 -0500] - INFO - main - 389-Directory/1.3.6.1 B2017.352.140 starting up
[04/Jan/2018:04:41:12.265740

Hence VERIFIED.
Comment 11 errata-xmlrpc 2018-01-25 07:22:50 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.

https://access.redhat.com/errata/RHSA-2018:0163

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