Paul,
On 8/11/22 12:09, Paul Chauvet wrote:
Hello all,
I haven't been able to figure this out - but a catalina.out file is not being generated
for me. Sadly - I'm trying to troubleshoot an issue (with a vendor's saml
implementation) which wants to write to that file (and doesn't seem to be writing what I
need to catalina.YYYY-DD-MM.logs, /var/log/messages, or into the journal as seen by
"journalctl --unit=tomcat.service").
My environment:
* RHEL 7.9 (though the same happens on my RHEL 8 hosts)
* Tomcat 9.0.63 (installed from the .tar.gz download from
https://tomcat.apache.org/download-90.cgi - not from the OS repository)
* Using jsvc via a systemd startup script to start Tomcat (that script is
at the bottom of this message).
Typically, systemd captures stdout/stderr and sends it to journald or
whatever. Writing to log files is apparently too quaint.
I've tried specifying CATALINA_OUT in setenv.sh, and in my systemd startup
script. I've temporarily disabled SELinux to see if that makes a difference.
Neither of those work. What does work, though I would like to avoid it, is if
I start Tomcat via ./startup.sh. If I do that - catalina.out is generated but
I'm not getting other settings I set in my systemd script (or having it tied to
startup/shutdown of the OS).
I don't know what I'm missing or doing wrong here, or if there's something
about jsvc that is an issue here that I can't figure out. I've been unable to
find anything related to this (lots of posts about catalina.out related to
operating system distributed versions of Tomcat that don't appear to apply).
It seems that you are just resisting doing things the Systemd Way.
Have you tried poking-around with journalctl to see if you can get the logs?
If "catalina.sh start/run" works for you, then the issue lies with your
systemd configuration/environment.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
