Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Bad Memberships in Composite group

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Bad Memberships in Composite group

Chronological Thread 
  • From: Blair Christensen <>
  • To: Kumi Hagimoto <>
  • Cc:
  • Subject: Re: [grouper-users] Bad Memberships in Composite group
  • Date: Wed, 14 Sep 2016 08:44:44 -0500
  • Ironport-phdr: 9a23:8SjZHhChTh3Dm8H9wS2KUyQJP3N1i/DPJgcQr6AfoPdwSP76pcbcNUDSrc9gkEXOFd2Crakb26yL6Ou5BCQp2tWojjMrSNR0TRgLiMEbzUQLIfWuLgnFFsPsdDEwB89YVVVorDmROElRH9viNRWJ+iXhpRZbIBj0NBJ0K+LpAcaSyp3vj6Hhs6HUNiZVgTv1Qbp9LRCxsQKZ4soLhIokKq8+yx7OvnxgfP5bymRuPk6agxu668utqs1N6SNV7tgl/s9aGY76ZaUjUbFeFzkgezQ/4MTqrzHeRguO7XITVSMbngceUFuN1w3zQpqk6niyjeF6wiTPeJSuFb0=

I've seen this in our environment with a similar group setup, first in 1.6.x and now on 2.2.2.

For now we just regularly run the Bad Membership Finder Utility to fix them but at some point I'd like to dig deeper and identify/resolve the actual problem.

blair @ uchicago

On Tue, Sep 13, 2016 at 5:21 PM, Kumi Hagimoto <> wrote:

We've been getting bad memberships reported in the nightly reports since we've
created a composite group and would like to figure out the cause.

One of the groups that constitutes the composite group is a result of multiple
layers of group memberships rolled up.    At the very bottom layer are groups
that define different types of users, and it seems that the membership change
from one group to another in this layer may be the cause of this bad
membership.  Here's a simplified structure:

Composite Group
    |        \
 Base      Excludes
    |           \
  userGrp1   userGrp2  ...

A user was deleted from userGrp1 and added to userGrp2 - timestamp less than a
second apart.  We got the Bad Memberships reported that night, and the user
was no longer in the Composite Group but still in the "Base" group.  This
happened for a few users, and all of them had a group change like this
example.  We checked the logs and there has been no error reported.   Has
anyone seen this sort of behavior?  If so, was there a fix for it?  We're
running grouper v 2.2.1.


Archive powered by MHonArc 2.6.19.

Top of Page