On Mar 3, 2014, at 11:24 AM, Rich Megginson <rmeggins(a)redhat.com> wrote:
On 03/03/2014 08:56 AM, Morgan Jones wrote:
> We're pulling our hair out over this issue and wondering if it rings a bell for
anyone or perhaps there's a bug fix in a later version of 389 that might resolve it.
I've looked and not found anything but it's also not the easiest issue to search
for. We are on CentOS DS now but can move to 389 of course but hesitate to put forth the
effort if we aren't reasonably sure it will resolve our issue.
...
>
> We are considering many options, primarily just moving to 389 on CentOS 6.
That's a fairly big task for a site of our size so we'd like some confidence that
we won't see a repeat of this issue. There's talk of considering other products
which no one wants to do but we're all edgy as this has caused a fair amount of
downtime and about all I can do at the moment is monitor for it and re-initialize when it
happens which doesn't inspire confidence.
I've never seen this problem, so I can't be sure that upgrading will solve it.
However, it is almost impossible for us to support centos-ds 8.2, so we are unlikely to be
able to debug 8.2 and provide a patch for 8.2.
This is understandable. Now that I have a better idea of how the community works I would
not implement on CentOS-DS again.
If you can reproduce the problem with 389-ds-base 1.2.11.x, it will
be much easier for us to debug and fix.
We are still unable to repeat it reliably but are working to do so in our dev environment.
I'll be in touch when/if we are able to do so in 389 1.2.11.x.
thanks,
-morgan