As for the log file, by launching the war file directly from the command line with java, i.e., using systemd, the logging information sent to the console is captured by systemd where it can be viewed with journalctl (i.e., systemd logging), but not to ~<cas_user>/.gradle/daemon/<gradle_version>/daemon-<pid>.out.log . Once through with debugging, I modified log4j2.xml to limit what is sent to the console. Specifically, I removed the <AppenderRef ref="casConsole"/> line at the bottom, then changed most of the*.level properties to "warn" rather than "info" or "debug" (exception: cas.log.level is set to "info"). Log entries appended to the "casFile" and "casAudit" appenders are written only to the files associated with those appenders (by default, cas.log and cas_audit.log), not to systemd logs.
I believe my questions have been answered, but also welcome additional recommendations. On Thursday, January 16, 2020 at 10:30:54 AM UTC-5, crdaudt wrote: > > Thanks Jérôme. Indeed, I am finding that launching the cas.war file with > java directly seems to be the best approach dealing with logs. I am not > using the dockerfile cas overlay, although perhaps I should be. > -- - 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/bb259496-53af-4ff2-a494-83145d2ba238%40apereo.org.
