On Mon, Feb 09, 2026 at 04:13:28PM +0100, Bastian Tweddell wrote:
On 09Feb26 11:22+0100, Ondřej Kuzník wrote:
They should get scheduled straight away. If you enable 'sync' level logging, what do the logs say about what's happening?
Adding 'sync' to the loglevel does not cause more log lines.
Hi Bastian, this is contrary to what I've seen every time I've done this before.
Just to check: how are you changing the configuration? Are you sure you're changing the config DB online (ldapmodify etc.) and not changing it via **offline** tools like slapmodify or worse editing the files directly (which the files themselves tell you **not** to do)?
But, when sending sigusr1 to slapd, sync-logs begin immediately:
Doesn't SIGUSR1 just kill the process, so your service manager starts a new one that you see do this?
do_syncrep1: rid=002 starting refresh (sending cookie=rid=002) syncrepl_message_to_entry: rid=002 DN: BASEDN, UUID: 813cd5d4-88d1-1038-96ad-bf796e276721 syncrepl_entry: rid=002 LDAP_RES_SEARCH_ENTRY(LDAP_SYNC_ADD) csn=(none) tid 0x7f07ab7f8640 syncrepl_entry: rid=002 inserted UUID 813cd5d4-88d1-1038-96ad-bf796e276721 syncrepl_entry: rid=002 be_search (32) ...The provisioning process adds the database section in two steps, first the main databse config (suffix, rootdn etc), and in a second step the syncrepl config. Would it make sense to add a delay before adding the syncrepl configuration to the database section?
Shouldn't make a difference, in fact, both scenarios (DB+syncrepl in one go or separately) are being actively tested in our test suite.
Regards,