Skip to Content.
Sympa Menu

grouper-users - [grouper-users] RE: Composite with complement did not update?

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] RE: Composite with complement did not update?


Chronological Thread 
  • From: "Hyzer, Chris" <>
  • To: "Waldbieser, Carl" <>, Kumi Hagimoto <>
  • Cc: "" <>
  • Subject: [grouper-users] RE: Composite with complement did not update?
  • Date: Tue, 18 Oct 2016 16:37:17 +0000
  • Accept-language: en-US
  • Authentication-results: spf=none (sender IP is ) ;
  • Ironport-phdr: 9a23:dGufDBVjBAyomt1QY/h5o3EMTU/V8LGtZVwlr6E/grcLSJyIuqrYZhGAt8tkgFKBZ4jH8fUM07OQ6P+wHzFbqs/c+Fk5M7VyFDY9wf0MmAIhBMPXQWbaF9XNKxIAIcJZSVV+9Gu6O0UGUOz3ZlnVv2HgpWVKQka3HUNPK+/0Ao/fidisn6D3osWLIlYAuD3oK4x7KBm8rAjKu9NSyaBrMKJ7gk/Wq39EceVbzktsLFyajhvg+sr28ZJ+pWAYmO8k9oZgWKr7eqMkSvQMDykjMiY17cLqsB7fSiOI/HYTVWMNjhNUDk7I4AysDbnrtS6v/MpsyiSAeYXdTao1Qn7qu6JgSA76hT0vNiUytnzPh8p2yq9XvUTy9FRE34fIbdTNZ7JFdaTHcIZfHDIZUw==
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99

There is no bad-badmembershipfinder-finder... that is the correct script.
And note, you should run it again afterwards until it says things are good.

Note, 2.3 api patch 23: find bad memberships daemon

https://spaces.internet2.edu/display/Grouper/v2.3+Release+Notes
https://bugs.internet2.edu/jira/browse/GRP-1367

This will run automatically so you don’t need to worry about it.

Thanks
Chris

-----Original Message-----
From:


[mailto:]
On Behalf Of Waldbieser, Carl
Sent: Tuesday, October 18, 2016 12:28 PM
To: Kumi Hagimoto
<>
Cc:

Subject: Re: [grouper-users] Composite with complement did not update?

Kumi,

That does look to be what happened.
When I run the bad membership finder, I get an output script with a number of
statements that I'm not sure what they are doing:

GrouperSession.startRootSession();

GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_createNewCompositeMembershipObject("63f2036200ff48d48aa463e33ca43622",
"5ec8735b43f546d08061ca33a73a4964", "612e954d58c44e37985e4e6fbb0f3b9a"));

GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_createNewCompositeMembershipObject("63f2036200ff48d48aa463e33ca43622",
"892bc28297f94372a5179eeec548c63e", "612e954d58c44e37985e4e6fbb0f3b9a"));

GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_createNewCompositeMembershipObject("71f7aba21f3948399727c4ec33fd3c1e",
"9aa9723ce7df4025a68c91d9450c6371", "0c354eb1eef74201a383b515d8b456bb"));

GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_createNewCompositeMembershipObject("71f7aba21f3948399727c4ec33fd3c1e",
"faf83a9bac5e4832adc38ab64f4e6427", "0c354eb1eef74201a383b515d8b456bb"));

GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_createNewCompositeMembershipObject("63f2036200ff48d48aa463e33ca43622",
"faf83a9bac5e4832adc38ab64f4e6427", "612e954d58c44e37985e4e6fbb0f3b9a"));

GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_createNewCompositeMembershipObject("71f7aba21f3948399727c4ec33fd3c1e",
"fdaf8e85ee264f3eb83be6ced20276f1", "0c354eb1eef74201a383b515d8b456bb"));

GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_createNewCompositeMembershipObject("63f2036200ff48d48aa463e33ca43622",
"fdaf8e85ee264f3eb83be6ced20276f1", "612e954d58c44e37985e4e6fbb0f3b9a"));
sqlRun("delete from grouper_memberships where
id='7a2e3a0e7365426a9b2c73602b3f99c2'");
sqlRun("delete from grouper_memberships where
id='d3f6b104d5ab4a959e62dbec06d46a46'");

The last 2 seem to be removing some obsolete groups.
Are the `Composite.internal_createNewCompositeMembershipObject` creating
missing memberships? Is there some way to (easily) check these before
updating?

Thanks,
Carl

----- Original Message -----
From: "Kumi Hagimoto"
<>
To:
,
"waldbiec"
<>
Sent: Tuesday, October 18, 2016 11:58:47 AM
Subject: Re: [grouper-users] Composite with complement did not update?

Hi Carl,

Looks like maybe you're seeing the same issue we have with v2.2.1?

https://lists.internet2.edu/sympa/arc/grouper-users/2016-09/msg00033.html

We just run the BadMembership gsh generated by nightly report until we
upgrade.

Thanks,
Kumi



Archive powered by MHonArc 2.6.19.

Top of Page