Grouper Users - Open Discussion List

["Hyzer, Chris" <>]

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

-----Original Message-----
From: 

 
[mailto:]
 On Behalf Of Scott Koranda
Sent: Saturday, November 05, 2016 12:33 PM
To: grouper-users 
<>
Subject: [grouper-users] understanding diagnostic servlet output for loader 
jobs

Hi,

I am using Grouper 2.3 with all the latest patches as of 11/5/2016.

The diagnostic servlet with diagnosticType=all was reporting

Grouper status error!

There was an error in the diagnostic task
DiagnosticLoaderJobTest, Loader job
LDAP_SIMPLE__community:facstaffother:members_systemOfRecord__381b6af6779f4f03a866669339ad5afa

So I then used GSH to run the loader job "by hand":

gsh 0% grouperSession = GrouperSession.startRootSession();
edu.internet2.middleware.grouper.GrouperSession: 
b0928e7b3e7d4e498db56d7fb9713e56,'GrouperSystem','application'
gsh 1% group = GroupFinder.findByName(grouperSession, 
"community:facstaffother:members_systemOfRecord")
group: name='community:facstaffother:members_systemOfRecord' 
displayName='community:facstaffother:members_systemOfRecord' 
uuid='381b6af6779f4f03a866669339ad5afa' 
gsh 2% loaderRunOneJob(group)
loader ran successfully, inserted 0 memberships, deleted 0 memberships, total 
membership count: 7066, unresolvable subjects: 0
gsh 3% quit

I then restarted Tomcat to make sure that the diagnostic servlet cleared
its state.

When I again query the diagnostic servlet (after Tomcat restart) I see (still)

Grouper status error!

There was an error in the diagnostic task DiagnosticLoaderJobTest, Loader job 
LDAP_SIMPLE__community:facstaffother:members_systemOfRecord__381b6af6779f4f03a866669339ad5afa

Why do I still see that error even though the loader job ran successfully?

Thanks,

Scott K