https://bugs.openldap.org/show_bug.cgi?id=9345
Issue ID: 9345 Summary: Restarted consumer with syncprov may have empty cookie Product: OpenLDAP Version: 2.4.52 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: --- Component: slapd Assignee: bugs@openldap.org Reporter: hyc@openldap.org Target Milestone: ---
On a relatively fresh node with both syncrepl and syncprov, after some writes have occurred, if the consumer config is deleted and re-added, it's possible the consumer won't see the current cookie. On startup it checks the local database for contextCSN, but if syncprov has been caching cookie updates it may not have been written to the DB yet. (And on an older server, the contextCSN may be present in the DB, but stale relative to the state syncprov has cached.)
The consumer calls check_syncprov on subsequent iterations, but it ought to also call it on startup, just in case.