[jira] [Closed] (LOG4NET-534) rollingfileappender: INTERNAL ERROR. Append is False but OutputFile already exists

["Dominik Psenner (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/LOG4NET-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dominik Psenner closed LOG4NET-534.
-----------------------------------
    Resolution: Invalid
      Assignee: Dominik Psenner

Closing as invalid. The logging framework cant work around permission issues. Feel free to reopen the issue if there is something in the logging framework that could be improved. That can be code changes, documentation, faq additions or others.

With respect to your issue, I am unable to help you. You could raise this question on the mailing lists to reach out to a larger audience, hoping that there is somebody who can help you.

> rollingfileappender: INTERNAL ERROR. Append is False but OutputFile already exists
> ----------------------------------------------------------------------------------
>
>                 Key: LOG4NET-534
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-534
>             Project: Log4net
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 1.2.15
>         Environment: Windows 10
>            Reporter: Jay McCormick
>            Assignee: Dominik Psenner
>              Labels: newbie
>
> Have read about [LOG4NET-118] and [LOG4NET-485] but it looks like neither has a resolution.  Existing log file is not being rolled, it is being overwritten instead.
> Same code and config running on Windows 7, produces the error message in the summary.  Not sure if UAC is a cause.  Log file is written into users %LOCALAPPDATA%\TEMP directory.  I have read about some "internal" log4net logging, but do not know how to activate that.
> The config:
> <?xml version="1.0" encoding="utf-8" ?>
> <configuration>
>     <!-- configSections MUST be first! -->
>     <configSections>
>         <section name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler, log4net"/>
>     </configSections>
>     
>     <log4net>
>         <appender name="MAINLogFile" type="log4net.Appender.RollingFileAppender">
>             <file type="log4net.Util.PatternString" value="%property{LogFileName}"/>
>             <appendToFile value="false"/>
>             <maximumFileSize value="20MB"/>
>             <maxSizeRollBackups value="3"/>
>             <param name="Encoding" value="unicodeFFFE"/>
>             <layout type="log4net.Layout.PatternLayout">
>                 <conversionPattern value="%date{ISO8601}&#09;%property{messageId}&#09;%-5level&#09;%message%newline"/>
>             </layout>
>             <filter type="log4net.Filter.LevelRangeFilter">
>                 <param name="LevelMin" value="ALL"/>
>                 <param name="LevelMax" value="OFF"/>
>             </filter>
>         </appender>
>         <appender name="AsyncBufferingAppender-HotSwap" type="AsyncForwardingAppenderHotSwap">
>             <GrowType value="Grow"/>
>             <GrowLimit value="3000000"/>
>             <Fix value="4"/>
>             <appender-ref ref="MAINLogFile"/>
>         </appender>
>         <logger name="MAIN">
>             <level value="INFO"/>
>             <appender-ref ref="AsyncBufferingAppender-HotSwap"/>
>         </logger>
>     </log4net>
>     <startup>
>         <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5.1"/>
>     </startup>
>     <system.windows.forms jitDebugging="true"/>
>     <system.diagnostics>
>         <trace useGlobalLock="false"/>
>     </system.diagnostics>
> </configuration>
> The AsyncBufferingAppender-HotSwap is borrowed from here:
> *       Copied from .NET low latency logging. Part 5 - Asynchronous log4net solutions
> *       http://deep-depth.blogspot.com/2014/02/net-low-latency-logging-part-5.html
> (I also tried without the Asynchronous Appender as well)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)