--On Wednesday, July 8, 2026 12:33 PM -0700 Ben Poliakoff benp@reed.edu wrote:
Jul 8 10:39:28 slapd-c daemon.info slapd[129831]: 6a3f4436.0d06e5be 0x7f6d411fc6c0 conn=-1 op=0 syncprov_matchops: recording uuid for dn=uid=example-user,ou=People,dc=foo,dc=bar on opc=0x7f6d2800c550 Jul 8 10:39:28 slapd-c daemon.info slapd[129831]: 6a3f4436.0d06f638 0x7f6d411fc6c0 conn=1869 op=4 syncprov_matchops: skipping original sid 001 Jul 8 10:39:28 slapd-c daemon.info slapd[129831]: 6a3f4436.0d082b1f 0x7f6d411fc6c0 syncrepl_null_callback : error code 0x7a Jul 8 10:39:28 slapd-c daemon.info slapd[129831]: 6a3f4436.0d08671e 0x7f6d411fc6c0 syncrepl_entry: rid=011 be_modify uid=example-user,ou=People,dc=foo,dc=bar (122)
From: https://ldap.com/ldap-result-code-reference-other-server-side-result-codes/
------------------------------------------------------------------------------------- assertionFailed (122)
Defined in Specification: RFC 4528
Applicable operation types: add, compare, delete, extended, modify, modify DN, search
The assertionFailed result code is used to indicate that the associated request included an LDAP assertion request control with a filter that did not match the target entry. The assertion request control may be used to indicate that the associated operation should only be processed if the target entry matches a specified filter. This is particularly useful for write operations, as it allows for a kind of atomic "check and set" operation, but you can also use it for compare and search operations (and for a search operation, the target entry is the one indicated by the search base DN). Some directory servers may also support it for certain extended operations.
If the filter included in the assertion request control does not match the target entry, then the operation will fail, and the response will include the assertionFailed result code. If the filter does match the target entry, then the operation will be processed as normal, and may succeed, or may fail for some reason unrelated to the inclusion of the assertion request control.
-------------------------------------------------------------------------------------
so looks like a non-fatal issue. I am curious what control is being asserted, and if that indicates a missing overlay in your stack.
Regards, Quanah