Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dual winsync paths results in LDAP DEL collision on DS #146

Closed
389-ds-bot opened this issue Sep 12, 2020 · 5 comments
Closed

Dual winsync paths results in LDAP DEL collision on DS #146

389-ds-bot opened this issue Sep 12, 2020 · 5 comments
Labels
closed: won't fix Migration flag - Issue
Milestone

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/146


https://bugzilla.redhat.com/show_bug.cgi?id=184155

Description of problem:
In a configuration with two DS in MMR (M1 and M2) and two AD in the same domain
(AD1 and AD2), if we configure M1 to sync with AD1 and M2 to sync with AD2, we
have a ring configuration with good availability.  Changes will be available
everywhere even if a server crashes.

If you delete a user on AD1, M1 will pick up that update within 5 minutes.  It
will send the change to M2, and M2 will attempt to replay it on AD2.  However,
because of the 5 minute lag, AD1 will already have deleted the entry from AD2
so
M2 will log errors, retrying every couple of seconds.  The error is a reference
to the garbage collection fqdn, which is usually not resolvable unless the RHDS
is using ADS based DNS, but I don't think we even want to touch the garbage
collector anyway.

This is similar to the problem with LDAP ADD in a dual winsync topology:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=182515

[06/Mar/2006:13:34:24 -0800] NSMMReplicationPlugin - changelog program -
agmt="c
n=hpntc782" (hpntc782:636): CSN 440ca1c3000000010000 found, position set for
rep
lay
[06/Mar/2006:13:34:24 -0800] agmt="cn=hpntc782" (hpntc782:636) - load=1 rec=1
cs
n=440ca2ed000100010000
[06/Mar/2006:13:34:24 -0800] NSMMReplicationPlugin - agmt="cn=hpntc782"
(hpntc78
2:636): windows_replay_update: Looking at delete operation local
dn="uid=fbar3,o
u=winsync,dc=cup,dc=hp,dc=com" (ours,user,not group)
[06/Mar/2006:13:34:24 -0800] NSMMReplicationPlugin - agmt="cn=hpntc782"
(hpntc78
2:636): windows_replay_update: Processing delete operation local
dn="uid=fbar3,o
u=winsync,dc=cup,dc=hp,dc=com" remote
dn="<GUID=91598cbce3e2004e90a75ac8f6474ef2
>"
[06/Mar/2006:13:34:24 -0800] NSMMReplicationPlugin - agmt="cn=hpntc782"
(hpntc78
2:636): Received result code 10 (0000202B: RefErr: DSID-031006E0, data 0, 1
acce
ss points       ref 1: 'gc._msdcs.ulftest.net:3268' ) for delete operation
[06/Mar/2006:13:34:24 -0800] NSMMReplicationPlugin - agmt="cn=hpntc782"
(hpntc78
2:636): windows_replay_update: deleted remote entry,
dn="<GUID=91598cbce3e2004e9
0a75ac8f6474ef2>", result=1
[06/Mar/2006:13:34:24 -0800] NSMMReplicationPlugin - agmt="cn=hpntc782"
(hpntc78
2:636): Consumer failed to replay change (uniqueid
41485081-ad5311da-8013a4b8-9c
ccd5f1, CSN 440ca2ed000100010000): Referral received. Will retry later.
[06/Mar/2006:13:34:24 -0800] agmt="cn=hpntc782" (hpntc782:636) - session end:
st
ate=0 load=1 sent=1 skipped=0

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
@389-ds-bot 389-ds-bot added the closed: won't fix Migration flag - Issue label Sep 12, 2020
@389-ds-bot 389-ds-bot added this to the FUTURE milestone Sep 12, 2020
@389-ds-bot
Copy link
Author

Comment from rmeggins (@richm) at 2012-01-10 06:12:04

batch update moving tickets to future

@389-ds-bot
Copy link
Author

Comment from rmeggins (@richm) at 2012-08-14 19:56:22

set default ticket origin to Community

@389-ds-bot
Copy link
Author

Comment from nkinder (@nkinder) at 2012-08-28 04:14:31

Added initial screened field value.

@389-ds-bot
Copy link
Author

Comment from nkinder (@nkinder) at 2017-02-11 23:11:06

Metadata Update from @nkinder:

  • Issue set to the milestone: FUTURE

@389-ds-bot
Copy link
Author

Comment from mreynolds (@mreynolds389) at 2020-03-25 16:56:32

Metadata Update from @mreynolds389:

  • Custom field reviewstatus adjusted to None (was: Needs Review)
  • Issue close_status updated to: wontfix
  • Issue status updated to: Closed (was: Open)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: won't fix Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant