Grouper Users - Open Discussion List

[Yoann Delattre <>]

Hi,

Great :)
just a thing, this url : 
http://software.internet2.edu/grouper/release/2.2.2/patches/grouper_v2_2_2_api_patch_6.tar.gz 
link to a 404 not found

Thanks,
Yoann

Le 31/01/2016 21:52, Hyzer, Chris a écrit :
> This is fixed.
>
> e.g. 
> https://grouperdemo.internet2.edu/grouper_v2_2/status?diagnosticType=daemonJobsOnly
>
> https://grouperdemo.internet2.edu/grouper_v2_2/status?diagnosticType=daemonJobsOnly&includeOnly=loader_MAINTENANCE_cleanLogs,loader_SQL_SIMPLE__community:students__4e01fd58743840df8bd63ae6b4fc12e5
>
> https://grouperdemo.internet2.edu/grouper_v2_2/status?diagnosticType=daemonJobsOnly&exclude=loader_MAINTENANCE_cleanLogs,loader_SQL_SIMPLE__community:students__4e01fd58743840df8bd63ae6b4fc12e5
>
> Note: grouper 2.2.3+ and 2.2.2.api.patch.6 has a diagnostic type of 
> daemonJobsOnly where only daemon (and loader) jobs will be run.
>
> https://url.to.grouper.edu/grouperWs/status?diagnosticType=daemonJobsOnly
>
> Server: mchyzer-pc, grouperVersion: 2.2.2, up since: 2016/01/31 15:14, 0 
> requests
> SUCCESS loader_CHANGE_LOG_changeLogTempToChangeLog: Not checking, there was a 
> success from before: 2016/01/31 15:14:50.000, expecting one in the last 30 
> minutes (65ms elapsed)
> SUCCESS loader_MAINTENANCE_cleanLogs: Not checking, there was a success from 
> before: 2016/01/31 11:45:13.000, expecting one in the last 3120 minutes (65ms 
> elapsed)
> SUCCESS loader_CHANGE_LOG_consumer_syncGroups: Not checking, there was a 
> success from before: 2016/01/31 15:14:00.000, expecting one in the last 30 
> minutes (66ms elapsed)
> SUCCESS loader_CHANGE_LOG_consumer_grouperRules: Not checking, there was a 
> success from before: 2016/01/31 15:14:02.000, expecting one in the last 30 
> minutes (66ms elapsed)
> SUCCESS loader_SQL_SIMPLE_loader:owner_9178d7d636de49d6b271d12ca351dc19: Not 
> checking, there was a success from before: 2016/01/31 13:40:04.000, expecting 
> one in the last 3120 minutes (66ms elapsed)
> Diagnostics errors since start: 0 (66ms elapsed)
>
>
> Exclude/include jobs by URL param
>
> You can includeOnly jobs in the URL by comma separated param (2.2.3+ and 
> 2.2.2.api.patch.6)
>
> https://url.to.grouper.edu/grouper/status?diagnosticType=daemonJobsOnly&includeOnly=loader_MAINTENANCE_cleanLogs,loader_CHANGE_LOG_consumer_syncGroups,loader_SQL_SIMPLE__loader:owner__9178d7d636de49d6b271d12ca351dc19
>
>
> SUCCESS loader_CHANGE_LOG_changeLogTempToChangeLog: Loader job 
> CHANGE_LOG_changeLogTempToChangeLog ignored in config since URL param 
> contains includeOnly which doesn't have 
> 'loader_CHANGE_LOG_changeLogTempToChangeLog' (46ms elapsed)
> SUCCESS loader_MAINTENANCE_cleanLogs: Not checking, there was a success from 
> before: 2016/01/31 11:45:13.000, expecting one in the last 3120 minutes (46ms 
> elapsed)
> SUCCESS loader_CHANGE_LOG_consumer_syncGroups: Not checking, there was a 
> success from before: 2016/01/31 15:14:00.000, expecting one in the last 30 
> minutes (46ms elapsed)
> SUCCESS loader_CHANGE_LOG_consumer_grouperRules: Loader job 
> CHANGE_LOG_consumer_grouperRules ignored in config since URL param contains 
> includeOnly which doesn't have 'loader_CHANGE_LOG_consumer_grouperRules' 
> (46ms elapsed)
> SUCCESS loader_SQL_SIMPLE_loader:owner_9178d7d636de49d6b271d12ca351dc19: Not 
> checking, there was a success from before: 2016/01/31 13:40:04.000, expecting 
> one in the last 3120 minutes (46ms elapsed)
>
>
> You can exclude jobs in the URL by comma separated param (2.2.3+ and 
> 2.2.2.api.patch.6)
>
>
> https://url.to.grouper.edu/grouper/status?diagnosticType=daemonJobsOnly&exclude=loader_MAINTENANCE_cleanLogs,loader_CHANGE_LOG_consumer_syncGroups,loader_SQL_SIMPLE__loader:owner__9178d7d636de49d6b271d12ca351dc19
>
>
> SUCCESS loader_CHANGE_LOG_changeLogTempToChangeLog: Not checking, there was a 
> success from before: 2016/01/31 15:14:50.000, expecting one in the last 30 
> minutes (31ms elapsed)
> SUCCESS loader_MAINTENANCE_cleanLogs: Loader job MAINTENANCE_cleanLogs 
> ignored in config since URL param contains exclude which has 
> 'loader_MAINTENANCE_cleanLogs' (31ms elapsed)
> SUCCESS loader_CHANGE_LOG_consumer_syncGroups: Loader job 
> CHANGE_LOG_consumer_syncGroups ignored in config since URL param contains 
> exclude which has 'loader_CHANGE_LOG_consumer_syncGroups' (31ms elapsed)
> SUCCESS loader_CHANGE_LOG_consumer_grouperRules: Not checking, there was a 
> success from before: 2016/01/31 15:14:02.000, expecting one in the last 30 
> minutes (31ms elapsed)
> SUCCESS loader_SQL_SIMPLE_loader:owner9178d7d636de49d6b271d12ca351dc19: 
> Loader job SQL_SIMPLEloader:owner9178d7d636de49d6b271d12ca351dc19 ignored in 
> config since URL param contains exclude which has 
> 'loader_SQL_SIMPLEloader:owner_9178d7d636de49d6b271d12ca351dc19' (31ms 
> elapsed)
>
>
>                   URL: https://bugs.internet2.edu/jira/browse/GRP-1242
>               Project: Grouper
>            Issue Type: New Feature
>        Security Level: Standard (Standard bug, may impact functionality but 
> does not represent a security vulnerability)
>            Components: WS
>      Affects Versions: 2.2.2
>              Reporter: Scott Koranda
>              Assignee: Chris Hyzer
>
>
> The Grouper diagnostic web-services servlet takes the query parameter 
> 'diagnosticType'. Right now there are four supported values:
>
> - trivial
> - db
> - all
> - sources
>
> The 'all' value includes diagnostics for loader jobs, but then also includes 
> all of the other diagnostics.
>
> It would be helpful if a value for 'diagnosticType' allowed only the loader 
> job testing. It would be even more helpful if there was some syntax to 
> specify a particular loader job or jobs to examine.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.4.11#64026)