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... Kind regards, Ulrich Windl > -----Original Message----- > From: Ondřej Kuzník <[email protected]> > Sent: Thursday, July 3, 2025 11:14 AM > To: Windl, Ulrich <[email protected]> > Cc: [email protected] > Subject: [EXT] Re: Q: "monitor_back_register_entry("cn=Consumer > 112,cn=Database 1,cn=Databases,cn=Monitor"): entry exists" > > Sicherheits-Hinweis: Diese E-Mail wurde von einer Person außerhalb des > UKR gesendet. Seien Sie vorsichtig vor gefälschten Absendern, wenn Sie auf > Links klicken, Anhänge öffnen oder weitere Aktionen ausführen, bevor Sie > die Echtheit überprüft haben. > > On Thu, Jul 03, 2025 at 06:51:21AM +0000, Windl, Ulrich wrote: > > Hi! > > > > For openldap-2.5 and an MMR configuration I see the message > > monitor_back_register_entry("cn=Consumer 112,cn=Database > > 1,cn=Databases,cn=Monitor"): entry exists during startup. I'm > > wondering what the messages actually says, and what causes it. Could > > it be some bug in OpenLDAP? The machine in question is real hardware > > (no VM) and it has a *lot* of RAM (500G) and CPUs (64). > > Hi Ulrich, > are you sure you're not using duplicate rid= values in your > configuration? > > Regards, > > -- > Ondřej Kuzník > Senior Software Engineer > Symas Corporation http://www.symas.com > Packaged, certified, and supported LDAP solutions powered by OpenLDAP
