Anonymous | Login | Signup for a new account | 09-07-2024 17:59 PDT |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0003834 | [Resin] | major | sometimes | 01-04-10 03:43 | 01-07-10 11:24 | ||||
Reporter | mfsaleem | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 4.0.2 | Product Version | 3.0.15 | ||||
Product Build | |||||||||
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 | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
32 total queries executed. 27 unique queries executed. |