[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: memberOf overlay issues with 2.4.44 + ITS 8432 patch
- To: "Paul B. Henson" <henson@acm.org>
- Subject: Re: memberOf overlay issues with 2.4.44 + ITS 8432 patch
- From: Quanah Gibson-Mount <quanah@symas.com>
- Date: Sat, 31 Dec 2016 17:39:15 -0600 (CST)
- Cc: openldap-technical@openldap.org
- In-reply-to: <WM!083b52013dd35fecb4c478751546c40b5c53e98b7509b5e91b1604d27057a42502e7b95bd28715368881fd7434e70db0!@mailstronghold-2.zmailcloud.com>
- References: <1682499429.55651701.1482424555189.JavaMail.zimbra@symas.com> <20161223021215.GK4221@bender.unx.cpp.edu> <WM!0e3da6695a26caceac5cb00165656c8bb09a08ad6c0179088bbd53f08f5a18e87a8f977b40fe6645574703f29a67cfe8!@mailstronghold-1.zmailcloud.com> <CCED81A021700EC515B75C91@[192.168.1.30]> <20161229004456.GB3709@bender.unx.cpp.edu> <WM!10a1dc7a17e4469407de824383f02214066398f10d4648de48a24708a73b972cd54038d4596e6f6c51782e1ba282ce24!@mailstronghold-3.zmailcloud.com> <10E301763CFA4E43239E3661@[192.168.1.30]> <20161230035540.GC3709@bender.unx.cpp.edu> <WM!392ea7bbbbde5a29541c7a78e3f748f3ec0b7f0510217816f33732c5cd5203ba969808e179cf05d3eec30c9b6122ae5f!@mailstronghold-2.zmailcloud.com> <5BE8DDC5CFAD6290CA241E8A@[192.168.1.30]> <20161231053136.GD3709@bender.unx.cpp.edu> <WM!083b52013dd35fecb4c478751546c40b5c53e98b7509b5e91b1604d27057a42502e7b95bd28715368881fd7434e70db0!@mailstronghold-2.zmailcloud.com>
- Thread-index: LELop561B5CILK7iXUCJWjpFdy0IVg==
- Thread-topic: memberOf overlay issues with 2.4.44 + ITS 8432 patch
Ok good to know! The issue I created occurred when deleting the group, which I believe is the original complaint in the ITS as well. So I will add individual membership deletes as a part of that test too.
--Quanah
> On Dec 30, 2016, at 9:31 PM, Paul B. Henson <henson@acm.org> wrote:
>
>> On Fri, Dec 30, 2016 at 02:41:06PM -0800, Quanah Gibson-Mount wrote:
>>
>> Well, it seems to be some sort of race condition.
>
> Yes, I'd agree; probably also load dependent as I never triggered it on
> my dev systems which are mostly idle other than my test load. It only
> showed up on my prod systems which tend to have continuous load from
> various other things.
>
>> I did want to confirm that you see this on servers that are long running
>> (I.e., they've been running for a long time, and had other group deletes
>> that went through w/o issue during that time). If so, then I can modify
>> the test to randomly add and delete groups as a part of the test,
>> increasing the likelyhood of triggering the issue within the test.
>
> I don't have too many deletions of group objects themselves in
> production, mostly just deletions of the members of groups. I didn't see
> any issues with group deletions in dev, or during some basic initial
> testing in prod. I'll go ahead and make a new test group, add some
> members to it, and then delete it and see what happens now that I've
> been running this code for about 3 weeks...
>
> I didn't see any errors deleting a group, although there were these
> syncrepl messages that I don't believe used to show up:
>
> Dec 30 21:23:29 themis slapd[2607]: syncrepl_message_to_op: rid=001 be_delete uid=ldaptest5,ou=group,dc=cpp,dc=edu (32)
> Dec 30 21:23:29 themis slapd[2607]: syncrepl_message_to_op: rid=003 be_delete uid=ldaptest5,ou=group,dc=cpp,dc=edu (32)
> Dec 30 21:23:29 themis slapd[2607]: syncrepl_message_to_op: rid=002 be_delete uid=ldaptest5,ou=group,dc=cpp,dc=edu (32)
>
> The group and memberOf attributes are gone on all four servers, so other
> than noise in the logs I'm not sure what these messages meant.
>
>