The script was doing a scope "one" search and it was not returning the RUV tombstone entry. There were recent changes around how to the RUV/tombstone entry was returned, and this impacted the tool.
This affects master, and maybe 1.3.7/1.3.6.
The fix is just to do a "sub" search:
$ruv = $conn->search($replicaroot, "sub", "(&(nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff)(bjectClass=nsTombstone))", 0, qw(nsds50ruv nsruvReplicaLastModified nsds5AgmtMaxCSN));
This only seems to impact 1.4.0
<img alt="0001-Ticket-49596-repl-monitor.pl-fails-to-find-db-tombst.patch" src="/389-ds-base/issue/raw/files/f6a2c1a621d1612d23e113bb064d63f5ee86a6ebf7818515bd2c4ac9b25c3e9c-0001-Ticket-49596-repl-monitor.pl-fails-to-find-db-tombst.patch" />
Metadata Update from @mreynolds: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to review - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @firstyear: - Custom field reviewstatus adjusted to ack (was: review)
Thanks William!
e6cc278..5e3f428 master -> master
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2655
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.