Hello,
Due to lack of response, this ITS will be closed. If you continue to
encounter the issue with the current OpenLDAP release, please follow up
with the information that was requested.
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Hi Andrew,
Sorry for the delay in response to this issue report. I believe I actually
encountered this same problem at a later point, and it is fixed in current
OpenLDAP. Would you be able to confirm?
Thanks,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--On Thursday, April 06, 2017 3:22 PM +0000
clement.oudot(a)savoirfairelinux.com wrote:
> Hello,
>
> I would like to know if some of you have an idea on how to fix this bug?
>
> I am able to test a patch if you can provide one.
Hi Clement,
Ondrej will be looking at this on Monday.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
--On Friday, April 07, 2017 7:59 PM +0000 Frank.Swasey(a)uvm.edu wrote:
> Today at 1:36pm, Frank.Swasey(a)uvm.edu wrote:
>
>> Today at 7:59am, ondra(a)mistotebe.net wrote:
>>
>>> Would you be able to confirm the patch in my previous email does the
>>> right thing for you?
>>
>> I am building it now, I'll test and report back.
>
> Yes, it has worked with every nasty test I have been able to dream up to
> throw at it.
Thanks for the confirmation. This fix will be included in OpenLDAP 2.4.45.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Today at 1:36pm, Frank.Swasey(a)uvm.edu wrote:
> Today at 7:59am, ondra(a)mistotebe.net wrote:
>
>> Would you be able to confirm the patch in my previous email does the
>> right thing for you?
>
> I am building it now, I'll test and report back.
Yes, it has worked with every nasty test I have been able to dream up to
throw at it.
--
Frank Swasey | http://www.uvm.edu/~fcs
Sr Systems Administrator | Always remember: You are UNIQUE,
University of Vermont | just like everyone else.
"I am not young enough to know everything." - Oscar Wilde (1854-1900)
Hello,
This ITS is being closed due to a lack of feedback. If you continue to
encounter this issue with a current release of OpenLDAP, please file a new
issue report, providing the additional details that were requested in this
ITS.
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Hello,
Thanks for the report, and I apologize for the delay in responding. I
would note that 2.4.21 (at this point) is ancient, and there have been
numerous fixes to Multimaster replication since that time. I would note in
the future, if you choose to file a report, your exact configurations would
also need to be supplied for a report such as this one. There was nothing
particularly actionable based on this report.
This ITS will be closed. If you can reproduce this issue with a current
build of OpenLDAP, please file a new issue.
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
Today at 7:59am, ondra(a)mistotebe.net wrote:
> Would you be able to confirm the patch in my previous email does the
> right thing for you?
I am building it now, I'll test and report back.
--
Frank Swasey | http://www.uvm.edu/~fcs
Sr Systems Administrator | Always remember: You are UNIQUE,
University of Vermont | just like everyone else.
"I am not young enough to know everything." - Oscar Wilde (1854-1900)
Hello,
Due to lack of response, this ITS will be closed. If you continue to
encounter the issue with a current build of OpenLDAP, please file a new ITS.
Regards,
Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
On Thu, Apr 06, 2017 at 02:48:45PM +0000, Frank.Swasey(a)uvm.edu wrote:
> On Wed, 5 Apr 2017 at 8:18am, ondra(a)mistotebe.net wrote:
>
>> AFAIK, LDAP doesn't forbid it so I don't see that going away.
>
> Well, then that means that the current behavior is a bug in either the
> syncrepl implementation or the accesslog recording. Since the MASTER
> gets updated correctly and the REPLICAs (and other MMR members) all fall
> down when attempting to process the accesslog entry.
Yes, they might reject the log entry and fall back to regular syncrepl
in the way they would in case of a conflict (which is mostly fine), or
the interpretation might seem to fit and a chance is that it's different
that the actual modification, causing the servers to silently get out of
sync.
>> It does need a fair bit of attention, the problem is it's something that
>> would require a format change and there are already existing consumers
>> that would be affected.
>>
>> I'm going to try with a patch to record something like this:
>> regMod: sn:= George
>> regMod: :
>> regMod: sn:= George
>>
>> Together with the relevant syncrepl updates.
>>
>> While consumers would still be affected, this should be quite rare and
>> the current handling of that case would have been incorrect anyway. The
>> change would then only make the silent failure a noisy one.
>
> Noisy in that the replica/mmr falls over dead or just logs more stuff?
In case of delta-syncrepl, it should reject it and fall back to regular
syncrepl. I can't vouch for anything else that consumes accesslog data
obviously.
> To be honest, my goal is consistency. I want the replicas (and
> MMR mates) to all wind up with the same values the master has.
Would you be able to confirm the patch in my previous email does the
right thing for you?
--
OndÅ™ej KuznÃk
Senior Software Engineer
Symas Corporation http://www.symas.com
Packaged, certified, and supported LDAP solutions powered by OpenLDAP