On Thu, Jul 03, 2025 at 01:50:24PM +0000, Windl, Ulrich wrote:
Ondřej,
Good spotting!
Actually I had a duplicate rid=112 in olcSyncrepl, but I never would have thought that monitor_back_register_entry is related to syncrepl. Problem was caused by a configuration script using the wrong variable...
Hi Ulrich, the code expects that rids are unique in a server (and documents as such), there is nothing to check that you have complied with this requirement but I would expect your replication might be impacted as well if you configured it thus.
The consumer status is also exported via cn=monitor, which had a conflict claiming the monitor DN as you just saw.
Regards,