Re: [cas-user] How to disable CasMetricsConfiguration in CAS 5.2.3?

2018-12-12 Thread Ray Bon
By 'application log files', do you mean catalina.out?

First make sure you are editing the correct file. You can force a particular 
file with a setting like this in cas.properties:

logging.config: file:/home/uvtomcat/config/log4j2.xml

Perhaps there is a more general logger that picks up the perStatsLogger. In the 
logger definition 'additivity="false"' prevents other loggers from also 
processing the messages. _BUT_ you must have an AppenderRef defined; if not the 
root logger (typically console => catalina.out) will take over.
In other words, you have to comment out the logger, as below, not just the 
appender ref.

Ray

On Wed, 2018-12-12 at 14:03 -0800, Mr Rao wrote:
Thanks for your response.   I tried commenting out and it started routing the 
logs to application log files which didn't solve the issue.



On Wednesday, December 12, 2018 at 9:28:43 AM UTC-8, Jon Anderson wrote:
I fought with the same issue a few months ago, and I did not figure out how to 
suppress that log. I'm pretty sure that I tried commenting out the log4j entry 
as well as other tweaks, but nothing worked for me. If it works I'll have to 
try again...

Jon

From: cas-...@apereo.org [cas-...@apereo.org] on 
behalf of Ray Bon [rb...@uvic.ca]
Sent: Wednesday, December 12, 2018 11:10 AM
To: cas-...@apereo.org
Subject: Re: [cas-user] How to disable CasMetricsConfiguration in CAS 5.2.3?

Rao,

You can comment it out in log4j2.xml:




Ray

On Tue, 2018-12-11 at 18:32 -0800, Mr Rao wrote:
Hi,
We have decided to  disable  CasMetricsConfiguration  I couldn't find property 
in cas.properties file to disable this?

I do not want any perfStatsLogger at all. Any help is greatly appreciated. This 
is filling up log files/disk space.


Thanks
Rao


018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.non-heap.used, value=105554216
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Code-Cache.committed, value=11108352
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Code-Cache.init, value=163840
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Code-Cache.max, value=33554432
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Code-Cache.usage, value=0.1809825897216797
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Code-Cache.used, value=6072768
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.committed, value=143130624
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.init, value=4521984
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.max, value=143130624
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.usage, value=0.34437706356956843
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.used, value=49290904
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.used-after-gc, value=0
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Metaspace.committed, value=100773888
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Metaspace.init, value=0
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Metaspace.max, value=-1
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Metaspace.usage, value=0.9871748522791935
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Metaspace.used, value=99481448
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.committed, value=17891328
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.init, value=524288
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.max, value=17891328
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.usage, value=0.20750611692994506
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.used, value=3712560
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.used-after-gc, value=3712560
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Tenured-Gen.committed, value=357957632
2018-12-11 18:22:13,666 severity=INFO, 

Re: [cas-user] How to disable CasMetricsConfiguration in CAS 5.2.3?

2018-12-12 Thread Mr Rao
Thanks for your response.   I tried commenting out and it started routing 
the logs to application log files which didn't solve the issue.



On Wednesday, December 12, 2018 at 9:28:43 AM UTC-8, Jon Anderson wrote:
>
> I fought with the same issue a few months ago, and I did not figure out 
> how to suppress that log. I'm pretty sure that I tried commenting out the 
> log4j entry as well as other tweaks, but nothing worked for me. If it works 
> I'll have to try again...
>
> Jon
> --
> *From:* cas-...@apereo.org  [cas-...@apereo.org ] 
> on behalf of Ray Bon [rb...@uvic.ca ]
> *Sent:* Wednesday, December 12, 2018 11:10 AM
> *To:* cas-...@apereo.org 
> *Subject:* Re: [cas-user] How to disable CasMetricsConfiguration in CAS 
> 5.2.3?
>
> Rao,
>
> You can comment it out in log4j2.xml:
>
> 
> 
>
> Ray
>
> On Tue, 2018-12-11 at 18:32 -0800, Mr Rao wrote:
>
> Hi, 
> We have decided to  disable  CasMetricsConfiguration  I couldn't find 
> property in cas.properties file to disable this?
>
> I do not want any perfStatsLogger at all. Any help is greatly 
> appreciated. This is filling up log files/disk space.
>
>
> Thanks
> Rao
>
>
> 018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.non-heap.used, value=105554216
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Code-Cache.committed, value=11108352
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Code-Cache.init, value=163840
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Code-Cache.max, value=33554432
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Code-Cache.usage, value=0.1809825897216797
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Code-Cache.used, value=6072768
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Eden-Space.committed, value=143130624
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Eden-Space.init, value=4521984
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Eden-Space.max, value=143130624
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Eden-Space.usage, value=0.34437706356956843
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Eden-Space.used, value=49290904
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Eden-Space.used-after-gc, value=0
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Metaspace.committed, value=100773888
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Metaspace.init, value=0
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Metaspace.max, value=-1
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Metaspace.usage, value=0.9871748522791935
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Metaspace.used, value=99481448
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Survivor-Space.committed, value=17891328
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Survivor-Space.init, value=524288
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Survivor-Space.max, value=17891328
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Survivor-Space.usage, value=0.20750611692994506
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Survivor-Space.used, value=3712560
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Survivor-Space.used-after-gc, value=3712560
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Tenured-Gen.committed, value=357957632
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Tenured-Gen.init, value=11206656
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Tenured-Gen.max, value=357957632
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Tenured-Gen.usage, value=0.9090788710994714
> 2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
> name=jvm.memory.pools.Tenured-Gen.used, value=325411720
> 

[cas-user] Re: Issues getting GoogleApps working on 5.3.6

2018-12-12 Thread JF Poulin
After a lot of debugging, I have discovered that the XML is not being 
properly inflated in AbstractSaml20ObjectBuilder at line 442: 
CompressionUtils.inflate(decodedBytes);

java is complaining about the zip header

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/6d052ef5-d24c-4e17-9906-e7f1933b9480%40apereo.org.


[cas-user] What does cas.authn.policy.requiredHandlerAuthenticationPolicyEnabled=false do?

2018-12-12 Thread Jac Fitzgerald

I haven't found a description of what this setting really controls - is it 
saying whether or not any authentication is required at all? Or can I use 
it to say that a specific handler is required to pass? Does someone have a 
more detailed guide to setting up authentication policies?

(My particular situation is that for a test deployment, I don't want 
requests to ever be rejected, I just want to log whether they pass or not 
before letting them continue, but I would also like to know how to set up 
more complex scenarios in the future).  

cheers,
Jac


This is the documentation I could find:

https://apereo.github.io/cas/5.3.x/installation/Configuring-Authentication-Components.html#authentication-policy
Authentication
 
Policy

CAS presents a number of strategies for handling authentication security 
policies. Policies in general control the following:

   1. Should the authentication chain be stopped after a certain kind of 
   authentication failure?
   2. Given multiple authentication handlers in a chain, what constitutes a 
   successful authentication event?

Policies are typically activated after:

   1. An authentication failure has occurred.
   2. The authentication chain has finished execution.

Typical use cases of authentication policies may include:

   1. Enforce a specific authentication’s successful execution, for the 
   entire authentication event to be considered successful.
   2. Ensure a specific class of failure is not evident in the 
   authentication chain’s execution log.
   3. Ensure that all authentication schemes in the chain are executed 
   successfully, for the entire authentication event to be considered 
   successful.

To see the relevant list of CAS properties, please review this guide 

.

*which links to*
 
https://apereo.github.io/cas/5.3.x/installation/Configuration-Properties.html#authentication-polic
*y*
Authentication Policy

To learn more about this topic, please review this guide 

.* (which links back to the above section)*

Global authentication policy that is applied when CAS attempts to vend and 
validate tickets.

1

# cas.authn.policy.requiredHandlerAuthenticationPolicyEnabled=false

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/5a5873e4-9fd4-458a-81a3-a42a5f9213f8%40apereo.org.


RE: [cas-user] How to disable CasMetricsConfiguration in CAS 5.2.3?

2018-12-12 Thread Jon Anderson
I fought with the same issue a few months ago, and I did not figure out how to 
suppress that log. I'm pretty sure that I tried commenting out the log4j entry 
as well as other tweaks, but nothing worked for me. If it works I'll have to 
try again...

Jon

From: cas-user@apereo.org [cas-user@apereo.org] on behalf of Ray Bon 
[r...@uvic.ca]
Sent: Wednesday, December 12, 2018 11:10 AM
To: cas-user@apereo.org
Subject: Re: [cas-user] How to disable CasMetricsConfiguration in CAS 5.2.3?

Rao,

You can comment it out in log4j2.xml:




Ray

On Tue, 2018-12-11 at 18:32 -0800, Mr Rao wrote:
Hi,
We have decided to  disable  CasMetricsConfiguration  I couldn't find property 
in cas.properties file to disable this?

I do not want any perfStatsLogger at all. Any help is greatly appreciated. This 
is filling up log files/disk space.


Thanks
Rao


018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.non-heap.used, value=105554216
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Code-Cache.committed, value=11108352
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Code-Cache.init, value=163840
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Code-Cache.max, value=33554432
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Code-Cache.usage, value=0.1809825897216797
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Code-Cache.used, value=6072768
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.committed, value=143130624
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.init, value=4521984
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.max, value=143130624
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.usage, value=0.34437706356956843
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.used, value=49290904
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.used-after-gc, value=0
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Metaspace.committed, value=100773888
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Metaspace.init, value=0
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Metaspace.max, value=-1
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Metaspace.usage, value=0.9871748522791935
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Metaspace.used, value=99481448
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.committed, value=17891328
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.init, value=524288
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.max, value=17891328
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.usage, value=0.20750611692994506
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.used, value=3712560
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.used-after-gc, value=3712560
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Tenured-Gen.committed, value=357957632
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Tenured-Gen.init, value=11206656
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Tenured-Gen.max, value=357957632
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Tenured-Gen.usage, value=0.9090788710994714
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Tenured-Gen.used, value=325411720
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Tenured-Gen.used-after-gc, value=301383952
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.total.committed, value=630861824
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.total.init, value=16941056
2018-12-11 18:22:13,666 

Re: [cas-user] How to disable CasMetricsConfiguration in CAS 5.2.3?

2018-12-12 Thread Ray Bon
Rao,

You can comment it out in log4j2.xml:




Ray

On Tue, 2018-12-11 at 18:32 -0800, Mr Rao wrote:
Hi,
We have decided to  disable  CasMetricsConfiguration  I couldn't find property 
in cas.properties file to disable this?

I do not want any perfStatsLogger at all. Any help is greatly appreciated. This 
is filling up log files/disk space.


Thanks
Rao


018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.non-heap.used, value=105554216
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Code-Cache.committed, value=11108352
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Code-Cache.init, value=163840
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Code-Cache.max, value=33554432
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Code-Cache.usage, value=0.1809825897216797
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Code-Cache.used, value=6072768
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.committed, value=143130624
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.init, value=4521984
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.max, value=143130624
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.usage, value=0.34437706356956843
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.used, value=49290904
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Eden-Space.used-after-gc, value=0
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Metaspace.committed, value=100773888
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Metaspace.init, value=0
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Metaspace.max, value=-1
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Metaspace.usage, value=0.9871748522791935
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Metaspace.used, value=99481448
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.committed, value=17891328
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.init, value=524288
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.max, value=17891328
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.usage, value=0.20750611692994506
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.used, value=3712560
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Survivor-Space.used-after-gc, value=3712560
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Tenured-Gen.committed, value=357957632
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Tenured-Gen.init, value=11206656
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Tenured-Gen.max, value=357957632
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Tenured-Gen.usage, value=0.9090788710994714
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Tenured-Gen.used, value=325411720
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.pools.Tenured-Gen.used-after-gc, value=301383952
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.total.committed, value=630861824
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.total.init, value=16941056
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.total.max, value=518979583
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=jvm.memory.total.used, value=483969400
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=thread-states.blocked.count, value=0
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 
name=thread-states.count, value=81
2018-12-11 18:22:13,666 severity=INFO, class=perfStatsLogger, type=GAUGE, 

[cas-user] Re: Issues getting GoogleApps working on 5.3.6

2018-12-12 Thread JF Poulin
I've traced the problem to the SamlServiceFactory class. It seems as though 
service and requestBody are always null. Trying to debug the issue.

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/b76d96d3-f4c5-41e2-82c8-e963983a9e43%40apereo.org.


Re: [cas-user] HA Redis Crash

2018-12-12 Thread Ramakrishna G
Mac,

You really saved my!! Thanks you so much.



On Wed, Dec 12, 2018 at 6:38 PM Mac Reid  wrote:

> Hi,
>
> Our repo is based on the overlay. You can find the version of spring boot
> here: https://github.com/apereo/cas-overlay-template/tree/5.3
>
> Another thing I noticed is the node option does not end with an `s`,
> meaning it should look like:
>
> cas.ticket.registry.redis.sentinel.master=mymaster
> cas.ticket.registry.redis.sentinel.node[0]=192.168.111.201:26379
> cas.ticket.registry.redis.sentinel.node[1]=192.168.111.205:26379
> cas.ticket.registry.redis.sentinel.node[2]=192.168.111.206:26379
>
> - Mac
>
> --
> - Website: https://apereo.github.io/cas
> - Gitter Chatroom: https://gitter.im/apereo/cas
> - List Guidelines: https://goo.gl/1VRrw7
> - Contributions: https://goo.gl/mh7qDG
> ---
> You received this message because you are subscribed to the Google Groups
> "CAS Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to cas-user+unsubscr...@apereo.org.
> To view this discussion on the web visit
> https://groups.google.com/a/apereo.org/d/msgid/cas-user/CALX_e4miT6Aw%3DERe9WnGYj8qoWm0%3DW7TPZW82A2DROTrqfXWjA%40mail.gmail.com
> 
> .
>

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/CAGST5P_iR8MBhn6pjfR7iBVJ4pb6zAE%3DMaSKhQoP45DCGugYgw%40mail.gmail.com.


Re: [cas-user] HA Redis Crash

2018-12-12 Thread Mac Reid
Hi,

Our repo is based on the overlay. You can find the version of spring boot
here: https://github.com/apereo/cas-overlay-template/tree/5.3

Another thing I noticed is the node option does not end with an `s`,
meaning it should look like:

cas.ticket.registry.redis.sentinel.master=mymaster
cas.ticket.registry.redis.sentinel.node[0]=192.168.111.201:26379
cas.ticket.registry.redis.sentinel.node[1]=192.168.111.205:26379
cas.ticket.registry.redis.sentinel.node[2]=192.168.111.206:26379

- Mac

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/CALX_e4miT6Aw%3DERe9WnGYj8qoWm0%3DW7TPZW82A2DROTrqfXWjA%40mail.gmail.com.


Re: [cas-user] HA Redis Crash

2018-12-12 Thread Ramakrishna G
Hi Mac,

I tried your solution but didn't work!!.

Do you any dependency added in your pom file apart from
"cas-server-support-redis-ticket-registry"? Also what is the version of
springboot used?

Thanks
Ramakrishna G


On Wed, Dec 12, 2018 at 1:23 AM Mac Reid  wrote:

> Hi,
>
> You cannot configure a single redis server with sentinel configured as
> well. Your config should only have:
>
> cas.ticket.registry.redis.sentinel.master=mymaster
> cas.ticket.registry.redis.sentinel.nodes[0]=192.168.111.201:26379
> cas.ticket.registry.redis.sentinel.nodes[1]=192.168.111.205:26379
> cas.ticket.registry.redis.sentinel.nodes[2]=192.168.111.206:26379
>
> We are using CAS 5.3.4 with redis sentinel using a config similar to the
> above lines.
>
> - Mac
>
> --
> - Website: https://apereo.github.io/cas
> - Gitter Chatroom: https://gitter.im/apereo/cas
> - List Guidelines: https://goo.gl/1VRrw7
> - Contributions: https://goo.gl/mh7qDG
> ---
> You received this message because you are subscribed to the Google Groups
> "CAS Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to cas-user+unsubscr...@apereo.org.
> To view this discussion on the web visit
> https://groups.google.com/a/apereo.org/d/msgid/cas-user/CALX_e4%3DT3BoRqXCX3UMybkFqf8Tn_%2BdAxBMGXvXhN%3DD0H%2BtCWQ%40mail.gmail.com
> 
> .
>

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/CAGST5P96XfaxUXbVuAPKYbbam%3Dkr_tU%2BMbFqzfnQ4Qm7fKBybQ%40mail.gmail.com.