Bug 1118079 - Multi master replication initialization incomplete after restore of one master
Summary: Multi master replication initialization incomplete after restore of one master
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
Depends On:
TreeView+ depends on / blocked
Reported: 2014-07-10 00:30 UTC by Noriko Hosoi
Modified: 2020-09-13 20:54 UTC (History)
2 users (show)

Fixed In Version: 389-ds-base-
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-03-05 09:36:35 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 992 0 None None None 2020-09-13 20:54:02 UTC
Red Hat Product Errata RHSA-2015:0416 0 normal SHIPPED_LIVE Important: 389-ds-base security, bug fix, and enhancement update 2015-03-05 14:26:33 UTC

Description Noriko Hosoi 2014-07-10 00:30:45 UTC
This bug is created as a clone of upstream ticket:

Initial configuration:
2 directories DS1 and DS2 with multimaster replication properly configured and working.
Around 3 millions of entries in these directories.

Steps to follow to reproduce :
1. Backup DS2 with db2bak.pl script 
See log "1.Backup_DS2.log"
[30/Dec/2013:11:12:06 +0100] - Beginning backup of 'ldbm database'

2. Restore this previous backup with bak2db command on DS2
See log "1.Restore_DS2.log"
[30/Dec/2013:13:03:51 +0100] - slapd shutting down - signaling operation threads

3. Initialize DS1 with DS2 data restored => initialization ends properly but only 400 000 entries are present in DS1
See logs "3.Init replication_DS*_KO.log"
[30/Dec/2013:13:18:38 +0100] NSMMReplicationPlugin - conn=11 op=3 repl="o=iah_extranet_msa": Begin total protocol

4. Wait for approximately 24 hours 
This log appears in DS2 error log : 
[31/Dec/2013:13:24:04 +0100] - Trimmed 1 changes from the changelog

Initialize consumer DS1 again with DS2 data => initialization ends properly and all the entries are present in DS1
See logs "4.Init replication_DS*_KO.log"

Comment 2 Sankar Ramalingam 2015-01-13 18:24:42 UTC
No issues reported from reliab15 executed for 389-ds-base- builds. Hence, marking the bug as Verified.

Comment 4 errata-xmlrpc 2015-03-05 09:36:35 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.


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