Grouper Users - Open Discussion List

[Scott Koranda <>]

On Fri, May 9, 2014 at 9:15 AM, Chris Hyzer 
<>
 wrote:
> https://spaces.internet2.edu/display/Grouper/GrouperShell+(gsh)#GrouperShell%28gsh%29-Loader
>
> loaderRunOneJob("MAINTENANCE_cleanLogs");

Ah. Thanks.

>
> but after a certain period of time you will get the error again if you 
> arent running the loader...

I am definitely running the loader.

How soon after the loader starts should a cleanLogs job be run?

Put another way, after a successful deployment and starting the
loader, how long do I have to wait before the status servlet returns
200?

>
> I think you have an extra underscore there:
>
> FROM:
>
> ws.diagnostic.ignore.loader_MAINTENANCE__cleanLogs = true
>
> TO:
>
> ws.diagnostic.ignore.loader_MAINTENANCE_cleanLogs = true

Yes. I changed it to test and it worked, but I think I will set that
back to false and instead just force
a run of the cleanLogs job.

Thanks,

Scott

>
> (sorry, the ignore group loader jobs have two underscores, the MAINTENANCE 
> type isn’t consistent)
>
> Thanks,
> chris
>
> -----Original Message-----
> From: 
> 
>  
> [mailto:]
>  On Behalf Of Scott Koranda
> Sent: Friday, May 09, 2014 9:56 AM
> To: grouper-users
> Subject: [grouper-users] status servlet error due to MAINTENANCE_cleanLogs
>
> Hi,
>
> After standing up a new production deployment I want to use the status
> servlet to monitor Grouper health but the deployment throws this error
> for type = all:
>
> java.lang.RuntimeException:
> There was an error in the diagnostic task DiagnosticLoaderJobTest,
> Loader job MAINTENANCE_cleanLogs
>
> :Cant find a success, expecting one in the last 3120 minutes
> edu.internet2.middleware.grouper.ws.status.GrouperStatusServlet.doGet(GrouperStatusServlet.java:211)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
>
> I have added
>
> ws.diagnostic.ignore.loader_MAINTENANCE__cleanLogs = true
>
> to grouper-ws.properties and restarted but the error persists.
>
> How can force a cleanLogs job so that this error goes away and we can
> turn on production monitoring?
>
> Thanks,
>
> Scott