I've been fighting this same battle today, also on Centos 7 with tomcat installed via yum.
My issue is that I can't find cas.log anywhere. I can "journalctl -u tomcat" to see the output, but I can't find the file. Where is it putting your cas.log? Bryce On Thursday, April 28, 2016 at 7:12:40 AM UTC-6, Matt S. wrote: > > Hi, > > On Cas server 4.2.1, it doesn't seem to be using the property in > cas.properties for externalizing the log4j2.xml file. > > This was working in 4.1.x, for example setting > log4j.config.location=file:///etc/cas/log4j2.xml in an externalized > cas.properties file, but it doesn't seem to be picking it up in 4.2 as none > of the log files are being created. > > If I just copy the log4j2.xml into my overlay in WEB-INF/classes/, it does > seem to work, but at least that is expected since it's the default location. > > I also noticed that in the sample Overlay linked in documentation, the > cas.properties file does not contain any property related to the log4j2 > file. > Is there a different way this is supposed to be setup to externalize? > > The logging section of the documentation only mentions a Java virtual > machine argument to define log4j.configurationFile for externalization. > I also tried using a property name of "log4j.configurationFile" in > cas.properties but that didn't seem to work. > > Any suggestions? > > > Thanks, > Matt > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/929aa643-fbaf-43bb-b3c4-aa20ed0cf2a3%40apereo.org. For more options, visit https://groups.google.com/a/apereo.org/d/optout.
