It’s not you. I have the same issue. I think those other log files are just there for backwards compatibility to make users feel good, since they never seem to be written to. “No news is good news” as the saying goes.
Sent from my iPhone > On Sep 17, 2019, at 4:34 PM, Jerry Malcolm <techst...@malcolms.com> wrote: > > For the problem du jour.... when I start JAMES, all of the expected log files > get created. The main log output goes to the console and to the > james-server.log file as expected. No problem there. But the remainder of > the log files never get touched. No matter what happens, every file in the > log folder other than james-server.log is empty. I've tried changing > log4j.properties and setting everything to DEBUG level. The console log > dumps a bunch more info while in DEBUG mode (which confirms I'm changing the > correct log4j file). But every other log file is still empty. I used to see > my mailet output in the main console and james-server.log in b5. I'm not > seeing any of that anywhere. Again, I've played around with log4j.properties > (I made sure I was using the latest 3.3.0 log4j.properties file). Nothing. > What am I doing wrong? How can I get log data to start going into those > other files? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
