Grouper Users - Open Discussion List

[Shilen Patel <>]

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
>
>