Grouper Developers Forum

["Gettes, Michael" <>]

Ok, basis:byDept:ALL:PRESIDNT:AG_NATRS:60030000:60036000:Not Two-Factor has 
no members in it and the loader job has "Groups like sql part” set to 
"basis:byDept:%”.  So there is an attempt to delete this group with 
id=09740d74e17646378755f0589955b1d9.  I see there are several other entries 
in group_set with member_group_id = 09740d74e17646378755f0589955b1d9.  I see 
there’s about 9 other instances of member_group_id = owner_group_id with 
values of 09740d74e17646378755f0589955b1d9.  Should I delete all instances of 
where the owner_group_id = 09740d74e17646378755f0589955b1d9?

/mrg

> On May 31, 2019, at 1:55 PM, Todd Haddaway <> wrote:
> 
> I could be wrong, but I read this to mean you cannot delete a row from the 
> parent (grouper_groups) because it contains a value in a field 
> (grouper_groups.id) that is being used as a foreign key in the child table 
> (grouper_group_set) field (member_group_id).  If the parent row was 
> deleted, it would violate that constraint.
> 
> Todd
> 
> On Fri, May 31, 2019 at 1:43 PM Gettes, Michael <> wrote:
> I’m trying to decipher the error presented…
> 
> Caused by: java.sql.BatchUpdateException: Cannot delete or update a parent 
> row: a foreign key constraint fails (`grouper`.`grouper_group_set`, 
> CONSTRAINT `fk_group_set_member_group_id` FOREIGN KEY (`member_group_id`) 
> REFERENCES `grouper_groups` (`id`))
> 
> I read this to imply there is a value in grouper_group_set.member_group_id 
> that is not in grouper_groups.id.
> To prove, I ran a right outer join to find what’s in group_set that is not 
> in groups
> select * from grouper.grouper_group_set gs 
> right join grouper.grouper_groups g 
> on gs.member_group_id = g.id
> where gs.member_group_id = null
> 
> and got 0 records returned.
> 
> i am not sure where the problem is - any guidance?
> 
> > On May 31, 2019, at 11:16 AM, Gettes, Michael <> wrote:
> > 
> > Hi all,
> > 
> > I have a condition of about a dozen groups which cannot be modified or 
> > deleted and the log snippet attached shows the error log for one of these 
> > groups.  First, I’d like to know how I fix these groups.  Second, the 
> > condition of how this occurred I am still trying to prove but it seems to 
> > be related to whether or not memory is configured with ms=mx.  I haven’t 
> > been able to recreate what caused the condition in the log snippet but 
> > the log snippet with ms=mx devolves into Garbarge collection failures and 
> > the loader becoming unusable over time.  With ms<mx (8g<9g) the errors i 
> > see in the log snippet do not cause the loader to become unusable over 
> > time.  Anyway, I’d really appreciate help fixing the bad groups based on 
> > the log.
> > 
> > I decided not to post this to the grouper-users list because I don’t want 
> > people thinking grouper is unstable and this could happen to them.  As 
> > you guys know, i have been doing some extreme things with grouper to see 
> > what’s possible and find issues and i think these “broken groups” are 
> > related to that work and the various memory problems I was having.
> > 
> > Thank you!
> > 
> > /mrg
> > 
> > <20190531-grouper-error.log>
> 
> 
> 
> -- 
> Todd Haddaway
> Senior Director - Middleware & Application Infrastructure
> UMBC, Division of Information Technology (DoIT) 
> 410.455.2854 |