Bug 788140 – cannot set repl referrals or state

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 788140 - cannot set repl referrals or state

Summary:	cannot set repl referrals or state

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	389-ds-base (Show other bugs)
Sub Component:
Version:	6.3
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Rich Megginson
QA Contact:	IDM QE LIST
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	749275 755094
	Show dependency tree / graph

Reported:	2012-02-07 10:15 EST by Rich Megginson
Modified:	2013-03-20 09:24 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	389-ds-base-1.2.10.0-1.el6
Doc Type:	Bug Fix
Doc Text:	Cause: Using replication, with suffixes that have a space in them (e.g. dc=example, dc=com instead of dc=example,dc=com). Consequence: Directory server error log fills up with errors like this: NSMMReplicationPlugin - repl_set_mtn_referrals: could not set referrals for replica dc=example,dc=com: 32 Fix: Correctly normalize the DN values used for the suffix so the server does not think they are missing (32). Result: Replication does not cause server error log to fill with bogus error messages.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2012-06-20 03:13:15 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2012:0813	normal	SHIPPED_LIVE	Low: 389-ds-base security, bug fix, and enhancement update	2012-06-19 15:29:15 EDT

Groups: None (edit)

Description Rich Megginson 2012-02-07 10:15:05 EST

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/277

Setting up replication leads to many errors like this:
[01/Feb/2012:20:56:00 -0700] NSMMReplicationPlugin - repl_set_mtn_referrals: could not set referrals for replica dc=example,dc=com: 32

Comment 3 Jenny Galipeau 2012-02-14 10:12:50 EST

Please add steps to reproduce/verify this bug

Comment 4 Rich Megginson 2012-04-16 11:06:47 EDT

1) set up replication with 2 masters - for the replica root, use an unnormalized suffix i.e. use dc=example, dc=com instead of dc=example,dc=com
2) do some updates to either server - look for errors in the errors log like
[01/Feb/2012:20:56:00 -0700] NSMMReplicationPlugin - repl_set_mtn_referrals: could not set referrals for replica dc=example,dc=com: 32

Comment 7 Amita Sharma 2012-05-24 11:22:19 EDT

[root@dhcp201-194 slapd-dhcp201-1942]# grep -i replicaroot /etc/dirsrv/slapd-dhcp201-1942/dse.ldif
nsDS5ReplicaRoot: dc=example,dc=com
nsDS5ReplicaRoot: dc=example,dc=com

Comment 8 Rich Megginson 2012-05-24 12:00:06 EDT

(In reply to comment #7)
> [root@dhcp201-194 slapd-dhcp201-1942]# grep -i replicaroot
> /etc/dirsrv/slapd-dhcp201-1942/dse.ldif
> nsDS5ReplicaRoot: dc=example,dc=com
> nsDS5ReplicaRoot: dc=example,dc=com

Try this:
1) service dirsrv stop
2) edit the dse.ldif - change these to
nsDS5ReplicaRoot: dc=example, dc=com
nsDS5ReplicaRoot: dc=example, dc=com

That is, add a space after the comma

3) service dirsrv start

Comment 9 Rich Megginson 2012-05-24 19:12:26 EDT

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: Using replication, with suffixes that have a space in them (e.g. dc=example, dc=com instead of dc=example,dc=com).
Consequence: Directory server error log fills up with errors like this:
NSMMReplicationPlugin - repl_set_mtn_referrals: could not set referrals for replica dc=example,dc=com: 32
Fix: Correctly normalize the DN values used for the suffix so the server does not think they are missing (32).
Result: Replication does not cause server error log to fill with bogus error messages.

Comment 10 Amita Sharma 2012-05-25 03:49:08 EDT

[root@dhcp201-194 ~]# grep -i replicaroot /etc/dirsrv/slapd-dhcp201-1942/dse.ldif
nsDS5ReplicaRoot: dc=example,  dc=com
nsDS5ReplicaRoot: dc=example,  dc=com
[root@dhcp201-194 ~]# grep -i replicaroot /etc/dirsrv/slapd-dhcp201-1943/dse.ldif
nsDS5ReplicaRoot: dc=example,  dc=com
nsDS5ReplicaRoot: dc=example,  dc=com

[root@dhcp201-194 ~]# vim /etc/dirsrv/slapd-dhcp201-1942/dse.ldif
[root@dhcp201-194 ~]# vim /etc/dirsrv/slapd-dhcp201-1943/dse.ldif
[root@dhcp201-194 ~]# grep -i replicaroot /etc/dirsrv/slapd-dhcp201-1942/dse.ldif
nsDS5ReplicaRoot: dc=example,  dc=com
nsDS5ReplicaRoot: dc=example,  dc=com
[root@dhcp201-194 ~]# grep -i replicaroot /etc/dirsrv/slapd-dhcp201-1943/dse.ldif
nsDS5ReplicaRoot: dc=example,  dc=com
nsDS5ReplicaRoot: dc=example,  dc=com
[root@dhcp201-194 ~]# service dirsrv start
Starting dirsrv: 
    dhcp201-194...                                         [  OK  ]
    dhcp201-1942...                                        [  OK  ]
    dhcp201-1943...                                        [  OK  ]
    dhcp201-1944...                                        [  OK  ]
    ldap-localdomain1...                                   [  OK  ]
    ldap-localdomain2...                                   [  OK  ]
[root@dhcp201-194 ~]# tail -f /var/log/dirsrv/slapd-dhcp201-1943/errors
[25/May/2012:12:25:14 +051800] - slapd stopped.
[25/May/2012:12:31:39 +051800] - 389-Directory/1.2.10.2 B2012.144.1937 starting up
[25/May/2012:12:31:39 +051800] - slapd started.  Listening on All Interfaces port 2389 for LDAP requests
[25/May/2012:12:36:59 +051800] - slapd shutting down - signaling operation threads
[25/May/2012:12:36:59 +051800] - slapd shutting down - closing down internal subsystems and plugins
[25/May/2012:12:36:59 +051800] - Waiting for 4 database threads to stop
[25/May/2012:12:37:00 +051800] - All database threads now stopped
[25/May/2012:12:37:00 +051800] - slapd stopped.
[25/May/2012:12:42:35 +051800] - 389-Directory/1.2.10.2 B2012.144.1937 starting up
[25/May/2012:12:42:36 +051800] - slapd started.  Listening on All Interfaces port 2389 for LDAP requests
^C
[root@dhcp201-194 ~]# tail -f /var/log/dirsrv/slapd-dhcp201-1942/errors
[25/May/2012:12:25:12 +051800] - slapd stopped.
[25/May/2012:12:31:38 +051800] - 389-Directory/1.2.10.2 B2012.144.1937 starting up
[25/May/2012:12:31:38 +051800] - slapd started.  Listening on All Interfaces port 1389 for LDAP requests
[25/May/2012:12:36:57 +051800] - slapd shutting down - signaling operation threads
[25/May/2012:12:36:57 +051800] - slapd shutting down - closing down internal subsystems and plugins
[25/May/2012:12:36:58 +051800] - Waiting for 4 database threads to stop
[25/May/2012:12:36:58 +051800] - All database threads now stopped
[25/May/2012:12:36:58 +051800] - slapd stopped.
[25/May/2012:12:42:34 +051800] - 389-Directory/1.2.10.2 B2012.144.1937 starting up
[25/May/2012:12:42:34 +051800] - slapd started.  Listening on All Interfaces port 1389 for LDAP requests
^C
[root@dhcp201-194 ~]# grep -i replicaroot /etc/dirsrv/slapd-dhcp201-1943/dse.ldif
nsDS5ReplicaRoot: dc=example,dc=com
nsDS5ReplicaRoot: dc=example,dc=com


Not sure whats happening here..
After restart its again taking it as dc=example,dc=com..

Comment 11 Rich Megginson 2012-05-25 11:04:22 EDT

Right.  The directory server will normalize the DNs.

Comment 12 Amita Sharma 2012-05-25 11:32:48 EDT

So I shd mark the bug as VERIFIED?
Still can't see the error mentioned in comment#4.

Comment 13 Rich Megginson 2012-05-25 11:40:11 EDT

(In reply to comment #12)
> So I shd mark the bug as VERIFIED?
> Still can't see the error mentioned in comment#4.

I don't understand.  You are trying to verify that you _do not_ see those errors any more.  The server was fixed to _not_ log those errors, and to handle replica root DN normalization correctly.  I guess that wasn't clear enough.

Comment 14 Amita Sharma 2012-05-25 12:32:01 EDT

Marking the bug as VERIFIED.

Comment 15 errata-xmlrpc 2012-06-20 03:13:15 EDT

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-2012-0813.html

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