On Sat, Jan 23, 2021 at 12:57:37AM +0200, Nick Milas wrote: > On 18/1/2021 6:27 μ.μ., Quanah Gibson-Mount wrote: > > > Nothing in the log snippet provided shows an issue. What leads you to > > believe an issue has been encountered? > > Hi Quanah, > > Thanks for the reply, > > I can't tell whether it was an issue or not (for example, I could call it a > phenomenon), but I found it strange to have this repeating for weeks every > three minutes and always on that single entry (among thousands). > > I am trying to figure out what does the log snippet mean. I would guess it > means that the particular entry at the master DIT is found to be older than > the one at the slave?
Something writes to your consumer, if you have a MMR environment, you want to assign different serverids. Otherwise you want to figure out how the change happened and either fix the offending service or set up chaining on consumers. > If so, I wonder how this may have happened! Maybe due to a DIT change that > took place at some point in time when the master clock was a bit slower than > the slave? (Although both are running ntp service.) > > And - in any case - what would be the recommended way to stop this from > occurring constantly? Regards, -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP
