RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1150817 - Running db2index with no options breaks replication
Summary: Running db2index with no options breaks replication
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: 389-ds-base
Version: 6.0
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: pre-dev-freeze
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks: 1342382
TreeView+ depends on / blocked
 
Reported: 2014-10-09 02:47 UTC by Brian J. Atkisson
Modified: 2020-09-13 21:44 UTC (History)
8 users (show)

Fixed In Version: 389-ds-base-1.2.11.15-82.el6
Doc Type: Bug Fix
Doc Text:
When running the db2index script with no options, the script failed to handle on-disk RUV entries because these entries have no parent entries. The existing RUV was skipped and a new one was generated instead, which subsequently caused the next replication to fail due to an ID mismatch. This update fixes handling of RUV entries in db2index, and running this script without specifying any options no longer causes replication failures.
Clone Of:
: 1342382 (view as bug list)
Environment:
Last Closed: 2017-03-21 10:19:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 1914 0 None None None 2020-09-13 21:44:35 UTC
Red Hat Product Errata RHBA-2017:0667 0 normal SHIPPED_LIVE 389-ds-base bug fix update 2017-03-21 12:35:05 UTC

Comment 10 Noriko Hosoi 2016-05-26 17:13:38 UTC 
Upstream ticket:
https://fedorahosted.org/389/ticket/48854
Comment 11 Noriko Hosoi 2016-05-27 01:19:19 UTC 
It turned out it was a real bug in import_foreman which was not adjusted when the backend RUV entry was redesigned.
Comment 15 Sankar Ramalingam 2016-11-22 05:12:23 UTC 
1). Created 4 master and 2 consumer setup

2). Entries synced across all masters and consumers
[root@auto-hv-02-guest09 ~]# SUFF="ou=people,dc=passsync,dc=com"; for PORT in `echo "1189 1289"`; do /usr/bin/ldapsearch -x -p $PORT -h localhost -D "cn=Directory Manager" -w Secret123 -b $SUFF |grep -i dn: | wc -l ; done 
2116
2116

3). Stopped dirsrv instances and ran db2index.
[root@auto-hv-02-guest09 MMR_WINSYNC]# service dirsrv stop
[root@auto-hv-02-guest09 MMR_WINSYNC]# for MMR in `echo "M1 M2 M3 M4 C1 C2"`; do /usr/lib64/dirsrv/slapd-$MMR/db2index; done

4). Started dirsrv instances and checked the no of entries.
[root@auto-hv-02-guest09 MMR_WINSYNC]# service dirsrv start
[root@auto-hv-02-guest09 MMR_WINSYNC]# SUFF="ou=people,dc=passsync,dc=com"; for PORT in `echo "1189 1289"`; do /usr/bin/ldapsearch -x -p $PORT -h localhost -D "cn=Directory Manager" -w Secret123 -b $SUFF |grep -i dn: | wc -l ; done 
2125
2125

5). Added few entries to masters and checked if all masters/consumers are synced.

[root@auto-hv-02-guest09 MMR_WINSYNC]# PORT=1189; SUFF="ou=people,dc=passsync,dc=com"; for PORT in `echo "1189 1289 1389 1489 2189 2289"`; do /usr/bin/ldapsearch -x -p $PORT -h localhost -D "cn=Directory Manager" -w Secret123 -b $SUFF |grep -i dn: | wc -l ; done 
2125
2125
2125
2125
2125
2125

Replication is working fine after running db2index. Hence, marking the bug as Verified.

[root@auto-hv-02-guest09 MMR_WINSYNC]# rpm -qa |grep -i 389-ds
389-ds-base-1.2.11.15-85.el6.x86_64
389-ds-base-libs-1.2.11.15-85.el6.x86_64
Comment 17 errata-xmlrpc 2017-03-21 10:19:54 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.

https://rhn.redhat.com/errata/RHBA-2017-0667.html
Note You need to log in before you can comment on or make changes to this bug.