blocks|key|98242|text|如果出现问题，并且无法写入其附加器，则Log4Net将执行fail+silently。这实际上是一件好事，因为它意味着一些失败的日志记录不会使原本健康的系统崩溃，但当某些东西没有像您预期的那样进行日志记录时，这可能会令人恼火。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|98243|最好的办法是打开log4net自己的internal+logging来进行一些诊断，并(希望)找出它失败的原因。|98244|因此，在应用程序的配置文件中添加：|98245|<?xml+version="1.0"+encoding="utf-8"+?>
<configuration>
++++<appSettings>
++++++++<add+key="log4net.Internal.Debug"+value="true"/>
++++</appSettings>
</configuration>|code-block|syntax|javascript|98246|这将打开发送到System.Diagnostics.Trace的内部日志记录，因此您可以添加：|style|CODE|98247|<configuration>
++++...
++++<system.diagnostics>
++++++++<trace+autoflush="true">
++++++++++++<listeners>
++++++++++++++++<add+
++++++++++++++++++++name="textWriterTraceListener"+
++++++++++++++++++++type="System.Diagnostics.TextWriterTraceListener"+
++++++++++++++++++++initializeData="C:\tmp\log4net.txt"+/>
++++++++++++</listeners>
++++++++</trace>
++++</system.diagnostics>
++++...
</configuration>|98248|将其捕获到一个文件中。|98249|entityMap|0|LINK|mutability|MUTABLE|url|http://logging.apache.org/log4net/release/faq.html#reliability|1|http://logging.apache.org/log4net/release/faq.html#internalDebug^0|T|D|0|0|I|G|1|0|0|0|7|O|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@$A|15|B|16|1|17]]|C|$]]|$1|D|3|E|5|6|7|18|8|@]|9|@$A|19|B|1A|1|1B]]|C|$]]|$1|F|3|G|5|6|7|1C|8|@]|9|@]|C|$]]|$1|H|3|I|5|J|7|1D|8|@]|9|@]|C|$K|L]]|$1|M|3|N|5|6|7|1E|8|@$A|1F|B|1G|O|P]]|9|@]|C|$]]|$1|Q|3|R|5|J|7|1H|8|@]|9|@]|C|$K|L]]|$1|S|3|T|5|6|7|1I|8|@]|9|@]|C|$]]|$1|U|3|-4|5|6|7|1J|8|@]|9|@]|C|$]]]|V|$W|$5|X|Y|Z|C|$10|11]]|12|$5|X|Y|Z|C|$10|13]]]]

Log4Net will <a href="http://logging.apache.org/log4net/release/faq.html#reliability" rel="noreferrer">fail silently</a> if something goes wrong and it is unable to write to its appenders. This is actually a good thing, since it means a bit of failed logging won't bring down an otherwise healthy system, but it can be annoying when something isn't logging as you expect.

Your best bet is to turn on log4net's own <a href="http://logging.apache.org/log4net/release/faq.html#internalDebug" rel="noreferrer">internal logging</a> to do some diagnostics and (hopefully) work out why it's failing.

So in your app's config file add:

<pre class="lang-xml prettyprint-override"><code>&lt;?xml version="1.0" encoding="utf-8" ?&gt;
&lt;configuration&gt;
 &lt;appSettings&gt;
 &lt;add key="log4net.Internal.Debug" value="true"/&gt;
 &lt;/appSettings&gt;
&lt;/configuration&gt;
</code></pre>

which will turn on the internal logging, which gets sent to <code>System.Diagnostics.Trace</code>, so you can add:

<pre class="lang-xml prettyprint-override"><code>&lt;configuration&gt;
 ...
 &lt;system.diagnostics&gt;
 &lt;trace autoflush="true"&gt;
 &lt;listeners&gt;
 &lt;add 
 name="textWriterTraceListener" 
 type="System.Diagnostics.TextWriterTraceListener" 
 initializeData="C:\tmp\log4net.txt" /&gt;
 &lt;/listeners&gt;
 &lt;/trace&gt;
 &lt;/system.diagnostics&gt;
 ...
&lt;/configuration&gt;
</code></pre>

to capture this to a file.

blocks|key|98272|text|在应用程序生命周期中尽可能早地发送一条测试日志消息，只需一个简单的LogManager.GetLogger("Init").Info("Starting+logging")即可。如果某些其他引用的代码首先启动日志记录，则初始化过程的一部分可能会失败(因为它从另一个程序集加载设置，而它只执行一次)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|98273|点击此处阅读：https://logging.apache.org/log4net/release/faq.html#first-log|98274|entityMap|0|LINK|mutability|MUTABLE|url|https://logging.apache.org/log4net/release/faq.html#first-log^0|X|1H|0|7|1P|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@]|D|@$9|T|A|U|1|V]]|E|$]]|$1|H|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

Send out a test log message as early as you can in your application lifecycle, just a simple <code>LogManager.GetLogger("Init").Info("Starting logging")</code> will do. If some other referenced code gets first to starting logging, a part of your initialization process may fail (as it loads settings from another assembly, which it only does once).

Read here: <a href="https://logging.apache.org/log4net/release/faq.html#first-log" rel="nofollow">https://logging.apache.org/log4net/release/faq.html#first-log</a>

blocks|key|98281|text|还要检查AssemblyInfo.cs文件中是否仍配置了log4net。在我的示例中，签入导致此文件中的以下行被删除：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|98282|程序集:+log4net.Config.XmlConfigurator(Watch+=+true)|98283|这反过来导致log4net停止记录...|98284|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Also check if log4net is still configured in the AssemblyInfo.cs file. In my case a check-in caused the following line to be removed in this file: 

[assembly: log4net.Config.XmlConfigurator(Watch = true)]

Which in turn caused log4net to stop logging...

blocks|key|98294|text|在与Log4Net斗争了一段时间后，我发现它将完全停止日志记录。不管我怎么试，我都不能让它恢复工作。当您没有在前几行代码中初始化日志时，似乎存在问题，但是模糊的指示不足以让我可靠地使日志在由另一个程序加载的dll中工作，等等。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|98295|我也从来没有激活过内部日志。|98296|我最终决定创建一个专用的dll，我的程序可以调用它来使用Log4Net可靠地创建日志。dll仅执行此操作，并且创建日志的代码是独立的，并且永远不会更改。我假设通过这种方式，我将能够可靠地创建日志文件并将其写入。到目前为止，这种方法已经解决了我花费了无数令人沮丧的小时的日志问题。|98297|我在这个SO线程上发布了代码：|98298|stackoverflow.com/questions/308436/log4net-programmatically-specify-multiple-loggers-with-multiple-file-appenders|offset|length|98299|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/308436/log4net-programmatically-specify-multiple-loggers-with-multiple-file-appenders/52162977#52162977^0|0|0|0|0|0|35|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@$J|Y|K|Z|1|10]]|A|$]]|$1|L|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|M|$N|$5|O|P|Q|A|$R|S]]]]

After struggling with Log4Net for a while, I found out that it would stop logging altogether. Not matter what I tried I couldn't get it back to work. It seems that there are issues when you do not initialize the log in the first few lines of code but that fuzzy indication was not enough for me to reliably get the log to work within a dll loaded by another program and so on.

I never managed to activate the internal log either.

I finally resolved to create a dedicated dll that my programs can call to reliably create a log using Log4Net. The dll does only that and the code creating the log is isolated and never changes. I assume that this way I will be able to reliably create logs files and write to them. So far this approach has fixed the issues with logging on which I had spend countless frustrating hours.

I posted the code on this SO thread: 

<a href="https://stackoverflow.com/questions/308436/log4net-programmatically-specify-multiple-loggers-with-multiple-file-appenders/52162977#52162977">stackoverflow.com/questions/308436/log4net-programmatically-specify-multiple-loggers-with-multiple-file-appenders</a>

I am currently building an ASP.Net-MVC Application using log4net for logging, but the logger seems to just stop at random. It will happily log for awhile, and then stop, and then will start again after a period of time. I am not even sure what it is that makes it resume logging. I'm not talking about just a few messages being lost- sometimes it dissappears for a long period of time, such as an hour or so. 

Why would it stop and start like this? How should I properly configure this so that it will not randomly stop as it does? 

Here is my configuration:

<pre class="lang-xml prettyprint-override"><code>&lt;log4net debug="true"&gt;
&lt;appender name="RollingLogFileAppender"
 type="log4net.Appender.RollingFileAppender"&gt;

 &lt;file value="..\Logs\\CurrentLog.txt" /&gt;
 &lt;appendToFile value="true" /&gt;
 &lt;datePattern value="yyyyMMdd" /&gt;

 &lt;rollingStyle value="Date" /&gt;
 &lt;filter type="log4net.Filter.LevelRangeFilter"&gt;
 &lt;acceptOnMatch value="true" /&gt;

 &lt;levelMin value="INFO" /&gt;
 &lt;levelMax value="FATAL" /&gt;
 &lt;/filter&gt;

 &lt;layout type="log4net.Layout.PatternLayout"&gt;
 &lt;conversionPattern
 value="%-5p %d %5rms %-22.22c{1} %-18.18M - %m%n" /&gt;
 &lt;/layout&gt;

&lt;/appender&gt;

&lt;root&gt;
 &lt;level value="INFO" /&gt;
 &lt;appender-ref ref="RollingLogFileAppender" /&gt;
&lt;/root&gt;
</code></pre>

Log4net randomly stops logging.

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我目前正在构建一个使用log4net进行日志记录的ASP.NETMVC应用程序，但是日志记录器似乎就这样随机停止了。它将愉快地记录一段时间，然后停止，然后在一段时间后重新启动。我甚至不确定是什么让它恢复日志记录。我说的不只是几条丢失的消息--有时它会消失很长一段时间，比如一个小时左右。为什么它会像这样停下来又开始呢？我...

问Log4net会随机停止日志记录。
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Log4net会随机停止日志记录。EN