search for: ldap_unavailable_critical_extension

>Then I am at a loss, if nothing really changed, why are you getting the >error ? Well, I ask myself the same question. The fact is that it went bad at the precise second we tried to add a new remote DC to the domain. This never happened before has we had many other remote DCs and use to join them whitout any problem. I was hopping that deleting and recreating the ldb cache would be

...ut it wasn't. Launching the daemonized script failed at the end of the first sync with the error i gave you. Is anyone on the dev side able to explain what happens here? Reminder of the error during a password sync: Thu Aug 13 15:19:12 2020: pid[31990]: ldb.LdbError(12) => (LDAP error 12 LDAP_UNAVAILABLE_CRITICAL_EXTENSION - <0000202C: Unable to unmarshall cookie as a ldapControlDirSyncCookie structure at ../source4/dsdb/samdb/ldb_modules/dirsync.c:1269> <>) -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscri...

...ted One day, after promoting a new remote DC, the sync began to fail on every DC. We tried to recover the first main DC from a backup, the sync worked, until we added a new DC and it failed again with the following error: Thu Aug 13 15:19:12 2020: pid[31990]: ldb.LdbError(12) => (LDAP error 12 LDAP_UNAVAILABLE_CRITICAL_EXTENSION - <0000202C: Unable to unmarshall cookie as a ldapControlDirSyncCookie structure at ../source4/dsdb/samdb/ldb_modules/dirsync.c:1269> <>) Thu Aug 13 15:19:12 2020: pid[31990]: Wait before connect - sleep(1) Thu Aug 13 15:19:13 2020: pid[31990]: Connecting to 'ldapi:///var/lib/samba...