>>> Geert Hendrickx <[email protected]> schrieb am 22.08.2019 um 13:19 in Nachricht <[email protected]>: > On Mon, Aug 19, 2019 at 08:54:43 ‑0700, Quanah Gibson‑Mount wrote: >> ‑‑On Monday, August 19, 2019 1:21 PM +0200 Ulrich Windl wrote: >> > I have a question preparing a transition of syncrepl to delta‑syncrepl: >> > Our database already has an accesslog overlay (olcAccessLogOps: writes) >> > and a corresponding database configured for monitoring purposes. >> >> You haven't noted the value for olcAccessLogSuccess. Generally for >> delta‑syncrepl *only* databases, this is set to TRUE. However, that's not >> mandatory (see the end for why). > > > Incidentally, we just toggled olcAccessLogSuccess to FALSE on a database > last week, to debug a provisioning issue where the client did not log > enough details. But our failed writes were still not logged. > > Turns out that writes failed by an overlay (slapo‑unique in our case) are > only logged to the accesslog, if this overlay is defined in the config > BEFORE the accesslog overlay (as overlays are loaded on a stack, see topic > 12.18 in the admin guide). So we now put the accesslog overlay as last > instead of first.
Makes sense as the error has to "go through" the overlay, I guess. Anyway a reminder in the manual page would be a nice thing to have. > > > Geert > > > ‑‑ > geert.hendrickx.be :: [email protected] :: PGP: 0xC4BB9E9F > This e‑mail was composed using 100% recycled spam messages!
