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. But, when sending sigusr1 to slapd, sync-logs begin immediately: ``` 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? Many thanks, -- Bastian Tweddell Juelich Supercomputing Centre phone: +49 (2461) 61-6586 --------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------- Forschungszentrum Jülich GmbH 52425 Jülich Sitz der Gesellschaft: Jülich Eingetragen im Handelsregister des Amtsgerichts Düren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Stefan Müller Geschäftsführung: Prof. Dr. Astrid Lambrecht (Vorsitzende), Dr. Stephanie Bauer (stellvertretende Vorsitzende), Prof. Dr. Ir. Pieter Jansens, Prof. Dr. Laurens Kuipers --------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------
smime.p7s
Description: S/MIME cryptographic signature
