[
https://issues.apache.org/jira/browse/LOG4NET-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667678#comment-13667678
]
Horst Beham edited comment on LOG4NET-378 at 5/27/13 10:20 AM:
---------------------------------------------------------------
Data is definitively lost.
File "flotto.20130527.1.log" had 4MB of log data in it (which was then rolled
over to flotto.20140527.2.log) and when the process was restarted file 1.log
got truncated and is currently being written to.
I can see original log statements and timestamps in 0.log, 2.log, 3.log. The
original information from 1.log is missing and the file only contains log
statements since the process restarted.
When I restart the process again, file 1.log is being truncated again even
though it's currently only 100KB in size.
The intention of my composite rolling appender is to roll the file when the
date changes or when the current file is already larger than 4MB.
I'll download the sources now and try to find the problematic code
was (Author: hbeham):
Data is definitively lost.
File "flotto.20130527.1.log" had 4MB of log data in it (which was then rolled
over to flotto.20140527.2.log) and when the process was restarted file 1.log
got truncated and is currently being written to.
I can see original log statements and timestamps in 0.log, 2.log, 3.log. The
original information from 1.log is missing and the file only contains log
statements since the process restarted.
When I restart the process again, file 1.log is being truncated again even
though it's currently only 100KB in size.
> Rolling log file is overwritten when application is restarted
> -------------------------------------------------------------
>
> Key: LOG4NET-378
> URL: https://issues.apache.org/jira/browse/LOG4NET-378
> Project: Log4net
> Issue Type: Bug
> Affects Versions: 1.2.11
> Reporter: Horst Beham
> Priority: Minor
>
> My server process uses log files which roll on date and file size (4MB).
> When I restart the server and there are already more than 1 log files for the
> current date, the 2nd segment gets overwritten and the 3rd, 4th, ... may get
> overwritten later, when #2 is filled up again.
> I'm using version 1.2.11, which I can't select in the "Affects Version" combo
> box.
> e.g.
> flotto.20130527.0.log = 4MB
> flotto.20130527.1.log = 0MB (just got overwritten when the server was
> restarted)
> flotto.20130527.2.log = 4MB (still contains original data but will be
> overwritten too as soon as #1 fills up)
> flotto.20130527.3.log = 4MB (same as above)
> The configuration in MyServer.exe.config looks like this:
> <log4net>
> <appender name="LogFileAppender"
> type="log4net.Appender.RollingFileAppender">
> <file value="flotto.log" />
> <appendToFile value="true" />
> <encoding>utf-8</encoding>
> <preserveLogFileNameExtension value="true"/>
> <rollingStyle value="Composite" />
> <staticLogFileName value="false" />
> <datePattern value=".yyyyMMdd"/>
> <countDirection value="1"/>
> <maximumFileSize value="4MB" />
> <layout type="log4net.Layout.PatternLayout">
> <conversionPattern value="%date [%-7thread] %-5level %-35logger -
> %message%newline" />
> </layout>
> </appender>
> <root>
> <level value="INFO" />
> <appender-ref ref="LogFileAppender"/>
> </root>
> <logger name="Flotto.FlottoService">
> <!--<level value="DEBUG"/>-->
> </logger>
> <logger name="Flotto.TcpServer">
> <!--<level value="DEBUG"/>-->
> </logger>
> <logger name="Flotto.UdpBroadcastReceiver">
> <!--<level value="DEBUG"/>-->
> </logger>
> <logger name="Flotto.GpsTrackerGprsServer">
> <level value="DEBUG"/>
> </logger>
> <logger name="Flotto.SmsAtHttpReceiver">
> <level value="DEBUG"/>
> </logger>
> <logger name="Flotto.SmsAtHttpSender">
> <level value="DEBUG"/>
> </logger>
> <logger name="Flotto.BulksmsComHttpReceiver">
> <level value="DEBUG"/>
> </logger>
> <logger name="Flotto.BulksmsComHttpSender">
> <level value="DEBUG"/>
> </logger>
> <logger name="Flotto.TrackerManager">
> <!--<level value="INFO"/>-->
> </logger>
> </log4net>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
