grouper-users - RE: [grouper-users] Pesky Error v2.4.0
Subject: Grouper Users - Open Discussion List
List archive
- From: "Redman, Chad" <>
- To: "O'Dowd, Josh" <>, "" <>
- Subject: RE: [grouper-users] Pesky Error v2.4.0
- Date: Tue, 5 Mar 2019 20:17:46 +0000
Are there any rules on the folder? That might cause an error like that,
because it can hardcode a group ID (e.g. an inherited privilege to a group)
into the rule. Easiest is to look at the attributes on the folder (and its
parent folders up to root?) and see if any attribute has this group ID.
What group does the group ID correspond to? Maybe it's in the old system but
not the new.
-Chad
-----Original Message-----
From:
[] On Behalf Of O'Dowd, Josh
Sent: Tuesday, March 05, 2019 2:13 PM
To:
Subject: [grouper-users] Pesky Error v2.4.0
Greetings.
I am pulling hair after a couple hours now, and thought I’d reach out and see
if anyone has seen this error…
To provide a little context, we recently migrated our 2.3.0 oracle database
over to a 2.4.0 postgres database, then deployed a fresh grouper 2.4.0
UI/WS/API with the postgres backend. To migrate the data, I ran gsh export
on the 2.3.0, then gsh-executed the resulting script on 2.4.0. The only
errors the script output listed were for creating a single group in a folder
with many groups that were already successfully moved. I figured I would
just manually rebuild that group and that is where I ran into this error:
"Error creating group: Subject not found: 'g:gsa':
'3f70e9c855e244808dda2f7ee3cebef0', Problem in HibernateSession:
HibernateSession (6e3f203a): notNew, notReadonly, READ_WRITE_NEW,
activeTransaction, session (6cb2ab3e), Problem in HibernateSession:
HibernateSession (5bc5ea81): new, notReadonly, READ_WRITE_NEW,
notActiveTransaction, session (6cb2ab3e),….”
It doesn’t matter what I try to name the group (in this case, “testing”), the
folder gives this same error every time. Furthermore, I CAN add/remove
members in other groups in this folder, and I can add/remove groups in other
folders that are in the same stem as the problem folder.
Very puzzling! Any thoughts?
Thanks for the time.
Josh O’Dowd
University of Montana
- [grouper-users] Pesky Error v2.4.0, O'Dowd, Josh, 03/05/2019
- RE: [grouper-users] Pesky Error v2.4.0, Redman, Chad, 03/05/2019
- RE: [grouper-users] Pesky Error v2.4.0, O'Dowd, Josh, 03/05/2019
- RE: [grouper-users] Pesky Error v2.4.0, Hyzer, Chris, 03/05/2019
- RE: [grouper-users] Pesky Error v2.4.0, O'Dowd, Josh, 03/05/2019
- RE: [grouper-users] Pesky Error v2.4.0, Hyzer, Chris, 03/05/2019
- RE: [grouper-users] Pesky Error v2.4.0, O'Dowd, Josh, 03/05/2019
- RE: [grouper-users] Pesky Error v2.4.0, O'Dowd, Josh, 03/05/2019
- RE: [grouper-users] Pesky Error v2.4.0, O'Dowd, Josh, 03/05/2019
- RE: [grouper-users] Pesky Error v2.4.0, Redman, Chad, 03/05/2019
- RE: [grouper-users] Pesky Error v2.4.0, Hyzer, Chris, 03/05/2019
- RE: [grouper-users] Pesky Error v2.4.0, O'Dowd, Josh, 03/05/2019
- RE: [grouper-users] Pesky Error v2.4.0, Hyzer, Chris, 03/05/2019
- RE: [grouper-users] Pesky Error v2.4.0, O'Dowd, Josh, 03/05/2019
- RE: [grouper-users] Pesky Error v2.4.0, Redman, Chad, 03/05/2019
Archive powered by MHonArc 2.6.19.