Hi Richard, I've filed a bug for this here:
http://bugs.caucho.com/view.php?id=3024 If you discover more information, please add it to this bug report. In the meantime, try changing the archive-format to have a filename with a .gz extension to have Resin automatically gzip the rotated logs. This should help with the disk filling up. Take care, Emil On Tue, Oct 21, 2008 at 04:10:12PM +0100, Richard Grantham wrote: > Sorry, you're right. All that is missing. > > I'm running Resin 3.1.7a. My log configuration is as follows: > <log name="" path="logs/resin.log" timestamp="[%Y-%m-%d %H:%M:%S.%s] " > rollover-period="1D" /> > <stdout-log path="logs/stdout.log" timestamp="[%Y-%m-%d %H:%M:%S.%s] " > rollover-period="1D" /> > <stderr-log path="logs/stderr.log" timestamp="[%Y-%m-%d %H:%M:%S.%s] " > rollover-period="1D" /> > <access-log path="logs/access.log" format='%h %l %u %t "%r" %s %b > "%{Referer}i" "%{User-Agent}i"' rollover-period="1D" /> > > We don't run Resin with Apache as we use a hardware load balancer. > > What I see happening is the log being rotated but a file handle is > maintained on access.log (it's all the logs mentioned above this is > happening with, not just access.log) and not recycled after the log is > rotated. The result is that the log is copied to another file but then > not cleared. It continues to be written to. Hope that makes sense. > > rgds, > > Richard > > > > > Richard Grantham > Development > > ------------------------------- > [EMAIL PROTECTED] > Limehouse Software Ltd > > DDI: (020) 7566 3336 > Main: (020) 7566 3320 > Fax: (020) 7566 3321 > > Limehouse Software Ltd > Bridewell Gate > 9 Bridewell Place > London > EC4V 6AW > > Manchester Office: > 3rd Floor, The Triangle, Exchange Square, Manchester M4 3TR > Tel: (0161) 240 2440, Fax: (0161) 240 2441, ISDN: 08700 119 400 > > Check out Limehouse Software's innovative solutions > www.limehousesoftware.co.uk - Transforming the way you publish and consult on > information > > The information contained in this e-mail or in any attachments is > confidential and is intended solely for the named addressee only. Access to > this e-mail by anyone else is unauthorised. If you are not the intended > recipient, please notify Limehouse Software Ltd immediately by returning this > e-mail to sender or calling 020 7566 3320 and do not read, use or disseminate > the information. Opinions expressed in this e-mail are those of the sender > and not necessarily the company. Although an active anti-virus policy is > operated, the company accepts no liability for any damage caused by any virus > transmitted by this e-mail, including any attachments.-----Original > Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Rob Lockstone > Sent: 15 October 2008 15:52 > To: General Discussion for the Resin application server > Subject: Re: [Resin-interest] Logs not rotating correctly > > My first question would be why would you want to maintain (on an ongoing > basis) access logs for what appears to be a pretty busy server? > > An important piece of information that's missing is the version of resin > that you're running. I know from personal experience that older > versions, in the 2.x world, did not properly rotate log files. > > Also, what settings for the logs do you have configured in your resin > configuration? If you're running resin with apache, then (usually) > apache is in control of the access logs, not resin. It's hard to tell > from what you've said how you have resin configured, standalone or with > apache. > > Rob > > On Oct 15, 2008, at 04:33, Richard Grantham wrote: > > > Hi list, > > I've got a major issue with our live servers. The logs don't > appear to > be rotating correctly. This is filling the disk and causing > performance > issues. > > Resin is running as the resin user - therefore will have reduced > permissions but, even so, this shouldn't be happening as that > user is > the owner of the folder that is being written to. > > Any ideas on how to sort this or is it a bug? > > [EMAIL PROTECTED] logs]# ls -l > total 3431672 > -rw-r--r-- 1 resin apache 1073979392 Oct 15 11:30 access.log > -rw-r--r-- 1 resin apache 1073745275 Oct 15 00:50 > access.log.20081015 > -rw-r--r-- 1 resin apache 1073892465 Oct 15 00:52 > access.log.20081015.0052 > -rw-r--r-- 1 resin apache 49848320 Oct 15 00:54 > access.log.20081015.0054 > -rw-r--r-- 1 resin apache 0 Oct 15 00:56 > access.log.20081015.0056 > -rw-r--r-- 1 resin apache 0 Oct 15 00:58 > access.log.20081015.0058 > -rw-r--r-- 1 resin apache 0 Oct 15 01:00 > access.log.20081015.0100 > -rw-r--r-- 1 resin apache 0 Oct 15 01:02 > access.log.20081015.0102 > -rw-r--r-- 1 resin apache 0 Oct 15 01:04 > access.log.20081015.0104 > > > [rest deleted for brevity] > > > > _______________________________________________ > resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest ============================================================ Emil Ong Chief Evangelist Caucho Technology, Inc. Tel. (858) 456-0300 mailto:[EMAIL PROTECTED] http://blog.caucho.com/ Caucho: Reliable Open Source --> Resin: application server --> Quercus: PHP in Java --> Hessian Web Services _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
