[Date Prev][Date Next]
Re: (ITS#8490) changes not written to accesslog, causing replicas to loop syncing
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#8490) changes not written to accesslog, causing replicas to loop syncing
- From: email@example.com
- Date: Thu, 01 Sep 2016 08:50:50 +0000
- Auto-submitted: auto-generated (OpenLDAP-ITS)
--On Thursday, September 01, 2016 8:58 AM +0000 firstname.lastname@example.org wrote:
> In looking at the LDAP accesslog, what I see is that what should have
> been a modRDN op was stored in the accesslog as a MOD op (the one I
> noted before). This seems particularly bizarre, because ldap01 should
> have rejected this change as well. It appears we may have a problem
> where the accesslog DB is updated, but then the change got rejected by
> the unique overlay.
Ok, actually the server (ldap01) accepted the change (renamed the entry).
Looking at the database, it was correctly done as a MODRDN to ldap01, but
/written/ as a MOD to accesslog?!