OMG!!! Finally. I feel like I can go back to the bosses with some progress. This is all good news. Also, thanks for the correction on the "lo and behold", I never knew that. I have to laugh at myself.
I can change the catalina file name to the name catalina.log, I think you are right and it be less confusing. Yes, nothing is going to catalina.out anymore. In the production environment there is almost always activity so then the new catalina.log file will be rollover pretty close to midnight every day. Now I'm really excited about implementing these changes in our big test environment that has a lot of activity. My little system at home is not used as much so I didn't get to experience the rollover. But I learned a lot from this experience. I will want to build from this setup to attempting to control what data is written where as right now there is a lot of duplicate information going to both the catalina and localhost file but I think it would be a separate email stream. Thank you so much for the help Christpher. -Joleen On Mon, Nov 30, 2015 at 10:26 AM, Christopher Schultz < ch...@christopherschultz.net> wrote: > Joleen, > > On 11/30/15 7:32 AM, Joleen Barker wrote: > > I will send the log4 details but I wanted to send this information first. > > The above details for the files remained the same all this time until I > > decided to login to the software and try to do some work. I had expected > > the files to roll at midnight each night which I did not see. But, long > > behold > > N.B. This is usually said "lo and behold". [1] > > > I run an ls -la command and the logs after I logged in and tried a > > couple things on the software and it appears the logs roll over and a new > > catalina log and localhost log started. Does some activity need to take > > place for the logs to roll over? > > Yes. The documentation suggests otherwise, but the appender won't > actually re-name the file and open a new one until it gets a write > operation after midnight had occurred. So it's possible to entirely skip > a day if there are no logging events that are sent to the appender. I'm > not sure if it will re-name and re-open when an event comes /and is > filtered/ (e.g. by a LEVEL that is too high for the logging-event) or > only when a log message will actually be written to the file. > > > I thought it was supposed to be each night at midnight. Also the > > dates of the files are a little misleading because they rolled today > > and not on 11-25 when they started up. > > Right, the creation-timestamp of the new file will be the time that the > file was created, not 00:00 at the beginning of the day when you thought > it should be created. > > > Here is what I see now: > > > > -rw-r--r--. root root 24372 Nov 30 06:33 catalina > > -rw-r--r--. root root 30694 Nov 25 22:49 catalina.2015-11-25.log > > -rw-r--r--. root root 0 Nov 25 22:49 catalina.out > > So it looks like catalina.out has nothing in it anymore. That's good, > right? Nothing is going to stderr/stdout. > > > -rw-r--r--. root root 0 Nov 25 22:49 host-manager > > -rw-r--r--. root root 24372 Nov 30 06:33 localhost > > -rw-r--r--. root root 31909 Nov 25 22:49 localhost.2015-11-25.log > > -rw-r--r--. root root 0 Nov 25 22:49 > > localhost_access_log.2015-11-25.txt > > -rw-r--r--. root root 25988 Nov 30 06:34 > localhost_access_log.2015-11-30 > > .txt > > -rw-r--r--. root root 0 Nov 25 22:49 manager > > [root@centos7sys1 logs]# date > > Thu Nov 30 07:27:39 EST 2015 > > The file "catalina" (which you might want to name catalina.log or > something, so it's less confusing) will always have the date of the > most-recent log message written to it. > > Hope that helps, > -chris > > [1] http://idioms.thefreedictionary.com/lo+and+behold > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
