0003834: Resin Logover sometimes create empty archive file.

3834

major

sometimes

01-04-10 03:43

01-07-10 11:24

Reporter:

mfsaleem

Platform:

Assigned To:

ferg

OS:

Priority:

normal

OS Version:

Status:

closed

Product Version:

3.0.15

Product Build:

Resolution:

fixed

Projection:

none

ETA:

none

Fixed in Version:

4.0.2

Summary:

0003834: Resin Logover sometimes create empty archive file.

Description:

Our application runs on resin 3.0.15 and we have noticed a behaviour that it creates an empty archive file because sometimes the stdout.log file is not created again after a correct log rollover. See below, during a failed rollover it creates an archive file of 20 Bytes which contains an unknown file type of 0 bytes. This issue can be seen more frequently when the application logging is set to finest.

-rw-rw-r-- 1 emea emea 75718 Jan 3 19:00 stdout.log.20100103-18:59:59.gz
-rw-rw-r-- 1 emea emea 20 Jan 3 20:00 stdout.log.20100103-19:59:59.gz
-rw-rw-r-- 1 emea emea 75897 Jan 3 21:00 stdout.log.20100103-20:59:59.gz
-rw-rw-r-- 1 emea emea 20 Jan 3 22:00 stdout.log.20100103-21:59:59.gz
-rw-rw-r-- 1 emea emea 75976 Jan 3 23:00 stdout.log.20100103-22:59:59.gz
-rw-rw-r-- 1 emea emea 20 Jan 4 00:00 stdout.log.20100103-23:59:59.gz
-rw-rw-r-- 1 emea emea 75924 Jan 4 01:00 stdout.log.20100104-00:59:59.gz
-rw-rw-r-- 1 emea emea 20 Jan 4 02:00 stdout.log.20100104-01:59:59.gz
-rw-rw-r-- 1 emea emea 76102 Jan 4 03:00 stdout.log.20100104-02:59:59.gz
-rw-rw-r-- 1 emea emea 75959 Jan 4 04:00 stdout.log.20100104-03:59:59.gz
-rw-rw-r-- 1 emea emea 20 Jan 4 05:00 stdout.log.20100104-04:59:59.gz
-rw-rw-r-- 1 emea emea 76208 Jan 4 06:00 stdout.log.20100104-05:59:59.gz
-rw-rw-r-- 1 emea emea 75775 Jan 4 07:00 stdout.log.20100104-06:59:59.gz
-rw-rw-r-- 1 emea emea 76110 Jan 4 08:00 stdout.log.20100104-07:59:59.gz
-rw-rw-r-- 1 emea emea 20 Jan 4 09:00 stdout.log.20100104-08:59:59.gz
-rw-rw-r-- 1 emea emea 76360 Jan 4 10:00 stdout.log.20100104-09:59:59.gz
-rw-rw-r-- 1 emea emea 20 Jan 4 11:00 stdout.log.20100104-10:59:59.gz

My Rollover config:
<stdout-log path='$ds.resinBaseDir/log/stdout.log' rollover-size="-1" rollover-period='1h'archive-format='stdout.log.%Y%m%d-%H:%M:%S.gz' />

When we noticed the issue, our rollover was set to once a day, then i changed it to generate archive every hour just to see if see the issue related with a large stdout.log file size but we can see the issue with this setting aswell.

Steps To Reproduce:

Additional Information:

Relationships

Attached Files:

Mantis - Resin
Viewing Issue Advanced Details

ID:	Category:	Severity:	Reproducibility:	Date Submitted:	Last Update:
3834		major	sometimes	01-04-10 03:43	01-07-10 11:24

Reporter:	mfsaleem	Platform:
Assigned To:	ferg	OS:
Priority:	normal	OS Version:
Status:	closed	Product Version:	3.0.15
Product Build:		Resolution:	fixed
Projection:	none
ETA:	none	Fixed in Version:	4.0.2

Summary:	0003834: Resin Logover sometimes create empty archive file.
Description:	Our application runs on resin 3.0.15 and we have noticed a behaviour that it creates an empty archive file because sometimes the stdout.log file is not created again after a correct log rollover. See below, during a failed rollover it creates an archive file of 20 Bytes which contains an unknown file type of 0 bytes. This issue can be seen more frequently when the application logging is set to finest. -rw-rw-r-- 1 emea emea 75718 Jan 3 19:00 stdout.log.20100103-18:59:59.gz -rw-rw-r-- 1 emea emea 20 Jan 3 20:00 stdout.log.20100103-19:59:59.gz -rw-rw-r-- 1 emea emea 75897 Jan 3 21:00 stdout.log.20100103-20:59:59.gz -rw-rw-r-- 1 emea emea 20 Jan 3 22:00 stdout.log.20100103-21:59:59.gz -rw-rw-r-- 1 emea emea 75976 Jan 3 23:00 stdout.log.20100103-22:59:59.gz -rw-rw-r-- 1 emea emea 20 Jan 4 00:00 stdout.log.20100103-23:59:59.gz -rw-rw-r-- 1 emea emea 75924 Jan 4 01:00 stdout.log.20100104-00:59:59.gz -rw-rw-r-- 1 emea emea 20 Jan 4 02:00 stdout.log.20100104-01:59:59.gz -rw-rw-r-- 1 emea emea 76102 Jan 4 03:00 stdout.log.20100104-02:59:59.gz -rw-rw-r-- 1 emea emea 75959 Jan 4 04:00 stdout.log.20100104-03:59:59.gz -rw-rw-r-- 1 emea emea 20 Jan 4 05:00 stdout.log.20100104-04:59:59.gz -rw-rw-r-- 1 emea emea 76208 Jan 4 06:00 stdout.log.20100104-05:59:59.gz -rw-rw-r-- 1 emea emea 75775 Jan 4 07:00 stdout.log.20100104-06:59:59.gz -rw-rw-r-- 1 emea emea 76110 Jan 4 08:00 stdout.log.20100104-07:59:59.gz -rw-rw-r-- 1 emea emea 20 Jan 4 09:00 stdout.log.20100104-08:59:59.gz -rw-rw-r-- 1 emea emea 76360 Jan 4 10:00 stdout.log.20100104-09:59:59.gz -rw-rw-r-- 1 emea emea 20 Jan 4 11:00 stdout.log.20100104-10:59:59.gz My Rollover config: <stdout-log path='$ds.resinBaseDir/log/stdout.log' rollover-size="-1" rollover-period='1h'archive-format='stdout.log.%Y%m%d-%H:%M:%S.gz' /> When we noticed the issue, our rollover was set to once a day, then i changed it to generate archive every hour just to see if see the issue related with a large stdout.log file size but we can see the issue with this setting aswell.
Steps To Reproduce:
Additional Information:
Relationships
Attached Files: