Re: [jetty-users] No logs when jetty runs as a daemon

[Ram Vemuri <ramvem@xxxxxxxxx>]

Yes, I added logging-log4j2 and added a custom log4j2.xml that writes to /logs under jettybase. App writes to its own log file in the same dir. This works when jetty is started from command line but not when it runs as a service. As a s device syslog shows the startup command but logs go nowhere. 

Sent from my iPhone

On Oct 19, 2022, at 9:56 AM, Joakim Erdfelt <joakim@xxxxxxxxxxx> wrote:



Did you setup log4j2 on your Jetty instance (the `${jetty.base}` directory)?

Jetty 10 ships with slf4j-2.x support.

The default sfl4j-2.x implementation (not log4j2) will write to STDERR (aka System.err).

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Wed, Oct 19, 2022 at 11:53 AM Ram Vemuri <ramvem@xxxxxxxxx> wrote:

Hi
I’ve set up Jetty 10 to run as a daemon on Ubuntu 22. Logs aren’t working though.  I see the start commands logged in syslog but no jetty logs. my war deploys and works but I dont see it’s log4j2 logs. Any ideas on what I might be missing? Thank you.
-Ram Vemuri


Sent from my iPhone
_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users

_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jetty-users