--On Thursday, July 9, 2026 4:38 PM -0700 Ben Poliakoff benp@reed.edu wrote:
The syncrepl process seems to get hung up "every so often" (might run for several days without issue). Today I found that it had gotten "stuck" again (newer change to an entry on slapd-a that wasn't being propagated to slap-b and slapd-c). Sometimes in these cases, simply restarting slapd on the non-primary instances gets things moving again. Today, though, that didn't work, and I was only able to get replication moving again, by deleting the entry (on the primary slapd instance) that was being referenced in the logs, and then recreating it (also on the primary slapd instance).
Hi Ben,
I'm curious if rather than deleting/adding the entry, if you modify an attribute on the entry back to its same value if that fixes it. That's worked for me in the past.
like:
dn: uid=blah,dc... changetype: modify replace: description description: account for blah
Regards, Quanah