0001354: log rollover issue in 3.0.21

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0001354

[Resin]

minor

always

09-18-06 09:30

11-06-06 07:09

Reporter

ferg

View Status

public

Assigned To

ferg

Priority

normal

Resolution

fixed

Status

closed

Product Version

Summary

0001354: log rollover issue in 3.0.21

Description

(rep by Shane Cruz)

Has anybody seen any problems with the log rollovers in Resin Pro 3.0.19 or above? It seems that most of the issues have been fixed, but the log rollover naming is not working properly for us for the stdout and stderr logs right now. It was working for a while, but over the past several days it hasn't been correct.

Here is how we define the logs in resin.conf:

   <stdout-log
        path="logs/stdout-${serverId}.log"
        rollover-period="1D"
        timestamp="[%H:%M:%S.%s] "/>

    <stderr-log
        path="logs/stderr-${serverId}.log"
        rollover-period="1D"
        timestamp="[%H:%M:%S.%s] "/>
    <log name="org.apache.geronimo"
         level="finest"
         path="logs/geronimo-${serverId}.log"
         rollover-period="1D"
         timestamp="[%H:%M:%S.%s] "
         format="${log.sourceClassName}.${log.sourceMethodName} ${log.message}" />

    <log name="org.jencks"
         level="finest"
         path="logs/jencks-${serverId}.log"
         rollover-period="1D"
         timestamp="[%H:%M:%S.%s] "
         format="${log.sourceClassName}.${log.sourceMethodName} ${log.message}" />

And here is what I see in the JVM logs:

[2006-09-18 00:00:00] Archiving access log to jencks-app1.log.20060917.
[2006-09-18 00:00:00] Archiving access log to geronimo-app1.log.20060917.
[2006-09-18 00:00:00] Archiving access log to stderr-app1.log.20060917.2359.
[2006-09-18 00:00:00] Archiving access log to stdout-app1.log.20060917.2359.
[2006-09-18 00:00:00] Archiving access log to stdout-app1.log.20060917.23
[2006-09-18 00:00:00] Archiving access log to stdout-app1.log.20060917.2359.0917.
And the files end up being named with a .20060917.2358 extension. Since the rollover period is 1D, shouldn't the naming convention default to just the date? As you can see, our other defined logs (for Jencks and Geronimo) are working fine.

Do we need to be specifying an archive-format in order to guarantee the naming is accurate? It seems that the documentation (http://www.caucho.com/resin-3.0/config/log.xtp#rollover) [^] indicates it should default to using %Y%m%d, so I don't think that will make a difference.

Any ideas? I don't see any open issues in BugTrack, what wanted to see if Scott had any suggestions before I opened a new bug.

Additional Information

Attached Files

Relationships

Notes
(0001544) scruz 10-16-06 07:10	This seems to only be happening with the stdout and stderr logs. It so happens that those are the only logs that are also configured in the httpd.sh script (so wrapper.pl can write to it). Is it possible that Resin cannot rotate those logs because wrapper.pl is writing to them? I am going to change the httpd.sh arguments to write to different files than what is configured in resin.conf to see if it fixes the rollover problem.

(0001575) ferg 11-06-06 07:09	synchronization/timing issue with rollover

Issue History
Date Modified	Username	Field	Change
09-18-06 09:30	ferg	New Issue
10-16-06 06:51	scruz	Issue Monitored: scruz
10-16-06 07:10	scruz	Note Added: 0001544
11-06-06 07:09	ferg	Note Added: 0001575
11-06-06 07:09	ferg	Assigned To	=> ferg
11-06-06 07:09	ferg	Status	new => closed
11-06-06 07:09	ferg	Resolution	open => fixed
11-06-06 07:09	ferg	Fixed in Version	=> 3.1.0

Mantis 1.0.0rc3[^]

32 total queries executed.
27 unique queries executed.