Hi Ondřej,
Which parts of the config would be good to see (sending over the contents of all the ldif files in slapd.d seems like overkill to send to the list)?
Replication appears to have been stable for the past several days, but I do continue to see repeated instances of logs (on the consumer) like this, even when replication seems to be working (verified both by watching contextCSN values on producer and consumer, as well as by making changes to entries on the primary provider and seeing those changes replicated in the consumer):
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) Jul 8 10:39:28 slapd-c daemon.info slapd[129831]: 6a3f4436.0d0896d0 0x7f6d411fc6c0 syncrepl_entry: rid=011 be_search (0) Jul 8 10:39:28 slapd-c daemon.info slapd[129831]: 6a3f4436.0d08a8b7 0x7f6d411fc6c0 syncrepl_entry: rid=011 uid=example-user,ou=People,dc=foo,dc=bar Jul 8 10:39:28 slapd-c daemon.info slapd[129831]: 6a3f4436.0d08c461 0x7f6d411fc6c0 conn=-1 op=0 syncprov_matchops: recording uuid for dn=uid=example-user,ou=People,dc=foo,dc=bar on opc=0x7f6d2800c550
Ben
On Tue, Jul 7, 2026 at 3:33 AM Ondřej Kuzník ondra@mistotebe.net wrote:
On Wed, Jul 01, 2026 at 02:39:50PM -0700, Ben Poliakoff wrote:
We've started experiencing syncrepl replication issues recently that look like this in the logs:
syncrepl_entry: rid=011 be_search (0) syncrepl_entry: rid=011 uid=example,ou=People,dc=foo,dc=bar syncrepl_null_callback : error code 0x7a syncrepl_entry: rid=011 be_modify uid=example,ou=People,dc=foo,dc=bar
(122)
Hi Ben, is there anything more from that session? This can happen if a local change happens between the time syncrepl reads the local copy and tries to update it[0] and as such, it should only need to try once more and succeed, not loop forever.
If it keeps happening for the same change, something might be interfering, so please post your sanitised config and logs from both sides (provider+consumer) of the affected session.
[0]. ITS#10358 https://bugs.openldap.org/show_bug.cgi?id=10358
Regards,
-- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP