--On Monday, September 24, 2018 2:51 PM +0000 Ole Nomann Thomsen ole.nomann@stil.dk wrote:
2018-09-12T16:25:41.526574+02:00 nonpresent_callback: rid=001 present UUID 9b99ec5a-4cfe-1029-9a2e-80309636f032, dn ou=Authentication,o=UNI-C,c=DK
This is the presence phase.
I'm guessing that that the Consumer is looking up every entry to decide if it has changed.
It is confirming each entry is still present (not deleted).
But why is it not persistent? Am a missing some obvious explanation as to why this is not possible, or have I just misconfigured something? Any hints where I should look?
Is there a better way to set up replication to avoid this?
a) Use delta-syncrepl b) Ensure you have a large sessionlog setting (See ITS#8125, ITS#8486)
Warm regards, Quanah
Thanks - You too.
In my case, the present-phase is not really useful, since this particulat ldap-instance only ever adds and modifies entries, never deletes. Would it then be possible to skip it ?
- Ole.