Grouper Users - Open Discussion List

[Scott Koranda <>]

> Give me a full screen copy of the status servlet, and look in logs and get 
> full error message there.  Sometimes it fails on a job but its really 
> another job (but threaded so it say both, if you know what I mean).  IF 
> that doesn't help find the problem job...
> 
> Maybe run this in the database:  (is it oracle?  If not you need to change 
> the SYSDATEs to whatever else for your DB...
> 
>    SELECT DISTINCT 'loaderRunOneJob("' || job_name || '");' AS script
>      FROM grouper_loader_log gll
>     WHERE     started_time > SYSDATE - 1
>           AND status != 'SUCCESS'
>           AND gll.job_name NOT LIKE 'subjobFor%'
>           AND NOT EXISTS
>                      (SELECT 1
>                         FROM grouper_loader_log gll2
>                        WHERE     gll2.started_time > SYSDATE - 1
>                              AND gll2.status = 'SUCCESS'
>                              AND gll2.job_name = gll.job_name);

For the archives:

The issue was that the copy of grouper-loader.properties in
the WS and UI deployment directories was out of sync with the
one in the "API" deployment directory (the one from which the
loader process actually runs).

So although there was no issue with the loader, the diagnostic servlet
was not working from a "proper" configuration.

After synchronizing that file across the API, UI, and WS and
restarting Tomcat the diagnostic servlet is reporting 200 OK,
the expected value based on the state of the loader jobs.

Thanks,

Scott K