Return-Path: X-Original-To: apmail-logging-log4net-dev-archive@www.apache.org Delivered-To: apmail-logging-log4net-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 45FD317F99 for ; Thu, 19 Feb 2015 08:11:12 +0000 (UTC) Received: (qmail 87797 invoked by uid 500); 19 Feb 2015 08:11:12 -0000 Delivered-To: apmail-logging-log4net-dev-archive@logging.apache.org Received: (qmail 87749 invoked by uid 500); 19 Feb 2015 08:11:12 -0000 Mailing-List: contact log4net-dev-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Log4NET Dev" List-Id: Delivered-To: mailing list log4net-dev@logging.apache.org Received: (qmail 87737 invoked by uid 99); 19 Feb 2015 08:11:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Feb 2015 08:11:12 +0000 Date: Thu, 19 Feb 2015 08:11:11 +0000 (UTC) From: "Ilpo Juvander (JIRA)" To: log4net-dev@logging.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (LOG4NET-82) RollingFileAppender: Cannot RollFile ... Source does not exist MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/LOG4NET-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14327100#comment-14327100 ] Ilpo Juvander commented on LOG4NET-82: -------------------------------------- Yes, source does not exist is there as well when this error comes. Funny thing is that even if I have appendtofile enabled, it overwrites log file so this move operation succeeds to some extend but .1 or .2 files are not there after roll operation. I'm using rollingStyle as Size. > RollingFileAppender: Cannot RollFile ... Source does not exist > --------------------------------------------------------------- > > Key: LOG4NET-82 > URL: https://issues.apache.org/jira/browse/LOG4NET-82 > Project: Log4net > Issue Type: Bug > Components: Appenders > Affects Versions: 1.2.9, 1.2.10 > Environment: Windows 2003 Server > Reporter: Kenneth Oberleitner > Fix For: 1.2 Maintenance Release > > > The following logging configuration will produce an endless loop of warnings under the following circumstances: > > > > > > > > > > > > > > 1.) set your system clock back at least three days > 2.) run an application to create the static log file dated 3 days prior > 3.) set your system clock forward a day (i.e. from Monday to Tuesday) > 4.) run the application again, the log file will roll and a new static log file is written > 5.) set your system clock forward a day (i.e. from Monday to Tuesday) > 6.) run the application > repeated warnings will be issued until the application is killed > log4net:WARN RollingFileAppender: Cannot RollFile [E:\tmp\LoggingFileLockBug\LoggingFileLockBug\bin\Debug\Log\Audit\audit.txt.XXX] -> [E:\tmp\LoggingFileLockBug\LoggingFileLockBug\bin\Debug\Log\Audit\audit.txt.20060719.XXX]. Source does not exist > where XXX is infinitely incremented until the process is halted > Two workarounds found so far both involve changing the date pattern. Both "yyyyMMdd" and ".yyyy-MM-dd" seem to work without issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)