Grouper Users - Open Discussion List

[Shilen Patel <>]

I'd probably try a couple of things:

1.  Enable debug logging.  Add
"log4j.logger.edu.internet2.middleware.grouper = DEBUG" to your
log4j.properties file, start gsh again, and run the command.  See if that
helps.  Feel free to send the logs to me.

2.  Run jstack or kill -3 on the java process to get a thread dump.
Again, feel free to send.

Thanks!

- Shilen

On 9/2/16, 3:05 PM, "Michael McManaman" 
<>
 wrote:

>Thanks Shilen.
>
>The grouper_change_log_entry_temp table had in excess of 900 rows in it.
>
>We've been testing different bulk load methods and I'm guessing that's
>where those records came from.
>
>They're not needed so I truncated the table and the command still hangs.
>
>Is there another table that could be the problem, or is there a was to
>trace what the gsh is doing & where it's stopping processing that command?
>
>Thanks again!
>
>Mike
>
>
>
>On 09/02/2016 02:13 PM, Shilen Patel wrote:
>> Hi Mike,
>>
>> That could mean that you have a lot of rows in the
>> grouper_change_log_entry_temp table that haven't been processed.  And
>>that
>> could happen if you haven't been running the Grouper Daemon. Typically
>>the
>> daemon runs the changeLogTempToChangeLog job every minute to prevent a
>> backlog.  In any case, while running that job from GSH, do a few counts
>>on
>> the table and see if the number of rows is decreasing.  If so, you just
>> have a backlog and you can estimate how long it will take to finish.
>> Otherwise, it may be stuck on a change.
>>
>> Thanks!
>>
>> - Shilen
>>
>> On 9/2/16, 1:35 PM, "Michael McManaman" 
>> <>
>>  wrote:
>>
>>> Hello -
>>>
>>> I'm trying to follow the online videos in setting for Grouper Training
>>>-
>>> Admin - PSP, and in part 3, I hit a problem with the first couple
>>> commands entered into gsh.  I cannot get this command to run:
>>>
>>>      loaderRunOneJob("CHANGE_LOG_changeLogTempToChangeLog")
>>>
>>> It stalls and never returns.  I set debug (GSH_DEBUG = true) and still
>>> see nothing & nothing in the logs.
>>>
>>> Other commands like:
>>>
>>>      loaderRunOneJob("CHANGE_LOG_consumer_psp")
>>>
>>>      findBadMemberships()
>>>
>>>      loaderRunOneJob("CHANGE_LOG_consumer_grouperRules")
>>>
>>> Return with "loader ran successfully: null"
>>>
>>> I have change log records - when i ran
>>>
>>>      loaderRunOneJob("MAINTENANCE_cleanLogs")
>>>
>>> I got back:
>>>
>>> loader ran successfully: Deleted 10 records from grouper_loader_log
>>> older than 7 days old.  Deleted 283206 records from
>>> grouper_change_log_entry older than 14 days old.
>>>
>>>
>>> Anyone have any ideas?
>>>
>>> Thanks in advance.
>>>
>>> Mike
>>>
>>>
>