I would vote for ditching the CONSOLE log completely. It's useful to see the startup messages from catalina (tomcat), but we should put all cloudstack logs in the management log (or agent/usage). I see not much use in duplicating the logs in both the management.log and the catalina.out.
Cheers, Hugo > -----Original Message----- > From: Musayev, Ilya [mailto:[email protected]] > Sent: Tuesday, April 23, 2013 6:00 AM > To: [email protected]; Kelven Yang > Subject: RE: [ACS41] Catalana.out needs log rotate > > This should work, and we can make it part of RPM/DEB builds. > > 1. Create this file > /etc/logrotate.d/tomcat > > 2. Copy the following contents into the above file > /var/log/cloudstack/management/catalina.out { copytruncate daily rotate 7 > compress missingok size 5M } > > -----Original Message----- > From: Musayev, Ilya [mailto:[email protected]] > Sent: Monday, April 22, 2013 11:53 PM > To: Kelven Yang; [email protected] > Subject: RE: [ACS41] Catalana.out needs log rotate > > In that case, we can use native system log rotate daemon. > > If no objections, I can take this on. > > > -----Original Message----- > From: Kelven Yang [mailto:[email protected]] > Sent: Monday, April 22, 2013 9:08 PM > To: [email protected]; Musayev, Ilya > Subject: Re: [ACS41] Catalana.out needs log rotate > > For log4j log files, we are using the rotation facility offered by log4j. > catalina.out may be a problem here, I think it is created in using shell > redirection > > Kelven > > On 4/22/13 5:34 PM, "Musayev, Ilya" <[email protected]> wrote: > > >Catalana.out on a lightly used demo ACS41 is 166mb in size in less than > >2 weeks old implementation running on centos6.3 > > > >How does log rotate work? Would anyone know if we are using Linux > >based log rotate or some other engine? > > > >Thanks > >Ilya > > > >
