Paul B. Henson wrote:
> From: Quanah Gibson-Mount
> Sent: Friday, July 22, 2016 10:40 AM
> Also see ITS 8448.
Ah, thanks much for the heads up on these additional issues. Perhaps it
would be safest for me to stick with 2.4.41 until a 2.4.45 is officially
released with fixes for both the replication loop and possible fallout from
its fix :). We've been pretty lucky with 2.4.41, knock on bits, it's been
very stable with no issues or problems that I've seen while we've been
The bug noted in ITS#8460 is not present in 2.4 at all. Quanah is also running
experimental backports of features from 2.5 and forgets to mention that
sometimes. This particular issue is from 2.5 (and is now fixed in git).
Most likely it's the same issue as #8448. You can disregard both of these.
> --On Thursday, July 21, 2016 5:47 PM -0700 Quanah Gibson-Mount
> <quanah(a)zimbra.com> wrote:
>> I would note that I've opened up two new ITSes for problems that only
>> occur on systems that have the ITS8432 fix. Still waiting on fixes for
>> those, which is why I haven't pushed the fix into RE24 yet.
>> ITSes 8460 and 8462.
>> --On Thursday, July 21, 2016 2:59 PM -0700 "Paul B. Henson"
>> <henson(a)acm.org> wrote:
>>>> From: Howard Chu
>>>> Sent: Thursday, July 21, 2016 3:36 AM
>>>> The fix for #8432 only prevents the redundant mod from being
>>>> on a particular node. If other nodes are still accepting the redundant
>>> then yes,
>>>> it will continue to propagate. So yes, you need the patched code on
>>> Okay, thanks for the clarification. I usually stage updates to avoid a
>>> complete outage at any given time. It's interesting though that I had
>>> never seen this problem running 2.4.41 until I introduced a 2.4.44
>>> into the mix, and then it went away once I reverted that system back to
>>> 2.4.41. I wonder why that combination caused it to pop up suddenly.
>>> have to schedule a downtime window and update them all at once and
>>> what happens.
>>> By any chance have you had the time to look at ITS 8444? The reporter
>>> says he sees a similar circular replication issue when the memberOf
>>> overlay is enabled, which we also use.
>>> Thanks much.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/