nlog Issue Tracker Rss Feed

Created Issue: Data loss when applying concurrentWrites and keepFileOpen [7425]

powertoy — Wed, 24 Apr 2013 13:22:32 GMT

Hi,

Consider following scenario.

1. I am starting 5 applications logging 30,000 messages each.
2. I am expecting 1,50,000 messages at the end in the log files. Applications are sharing the same log file destination.
3. I am leveraging concurrentWrites = true and keepFileOpen = true. Now the problem is, we are not getting 1,50,000 messages logged at the end.

We have around 1,30,000 messages and other messages are lost. I am closing all applications once all logs are written to the file and I am also calling LogManager.Flush(); at the end.

Are we missing any configuration here? Attached is my configuration.
Any help in this direction would be great!

Thanks

Commented Issue: Async Wrapper is not working [7422]

powertoy — Wed, 24 Apr 2013 12:44:55 GMT

Hi All,

We are getting different behaviors when enabling Aync logging by using AsyncWrapper. As I know there are 2 ways to enable this.

1. by using <targets async =" true">
2. by providing a new target by using <target name="asyncWrapper" xsi:type="AsyncWrapper" queueLimit="5000" overflowAction="Grow">

The option 1 is fast and i can see that my logs are written on a different thread. I can see that 50000 log messages are being written when program control comes back. The only problem here is, log messages are lost.

The option 2 is not at all working. It seems that NLog writes messages synchronously and doesn't return control.

Are we missing any NLog specific configuration for option number 2?

Attached is the configuration file I am using.

Thanks,
Comments: ** Comment from web user: powertoy **

Thanks a lot Jaroslaw. It worked!

Now I am facing another issue. Consider following scenario.

1. I am starting 5 applications logging 30,000 messages each.
2. I am expecting 1,50,000 messages at the end in the final log file. Applications are sharing the same log file.
3. I am leveraging concurrentWrites = true and keepFileOpen = true.

Now the problem is, we are not getting 1,50,000 messages logged at the end. We have around 1,30,000 messages and other messages are lost.

I am closing all applications once all logs are written to the file and I am also calling LogManager.Flush(); at the end.

__Are we again missing any configuration here?__

Following is my configuration.

</nlog>

Commented Issue: Async Wrapper is not working [7422]

jkowalski — Tue, 23 Apr 2013 16:14:27 GMT

You need to fix your rules. Instead of writeTo="file" you need to say writeTo="asyncWrapper". Right now you're not really using the wrapper.

Commented Issue: Async Wrapper is not working [7422]

jagrutpatel — Tue, 23 Apr 2013 12:42:54 GMT

Ditto issue!

Is AsyncWrapper async at all? I don't see any difference with or without this target. It takes almost same time to log, say 50K messages. What is the correct way to achieve async logging using AsyncWrapper? For me OverFlowAction = Grow is important parameter.

I then tried "async=true". It is truly async. But alas! There is data loss. Not all log messages got logged even if the application is running. Is this because by default OverFlowAction is Discard so log messages that exceed the default queueLimit will be dropped?

Commented Issue: Async Wrapper is not working [7422]

Harshil13 — Tue, 23 Apr 2013 12:30:23 GMT

We have also observed the same behaviour. However, the actual behaviour is asyncWrapper doesn't work asynchronously and to make the code async, we have to have <targets async =" true"> set, which in turns overwrites all underlying setting at <target xsi:type="File" .... /> level. In such cases it mandates the default settings.

Is this bug?

Thanks.

Created Issue: Async Wrapper is not working [7422]

powertoy — Tue, 23 Apr 2013 12:15:26 GMT

Commented Issue: AspNetBufferingWrapper not working for IIS7 [7356]

pedrofilipebin — Tue, 19 Mar 2013 16:15:47 GMT

Hi, I have an MVC3 project with NLog.2.0.0.2000 and NLog.Extended.2.0.0.2000
I can't seem to use NLog.Extended 'AspNetBufferingWrapper'. I have added the NLog.Extended module to 'httpModules'.
I believe that because I'm using IIS7, the httpModules does not work in integrated mode.
I've tried adding to the system.webServer module, but to no avail.
Can you help me? If this is the source of the issue, the documentation should also be updated, right?
Comments: ** Comment from web user: pedrofilipebin **

Details at http://stackoverflow.com/questions/15504727/nlog-extended-aspnetbufferingwrapper-not-working

Created Issue: AspNetBufferingWrapper not working for IIS7 [7356]

pedrofilipebin — Tue, 19 Mar 2013 15:32:01 GMT

Commented Issue: Create layout renderer assembly-version [6932]

consept — Thu, 22 Nov 2012 13:39:06 GMT

It would be useful to have a ${assembly-version} layout renderer for use with headers, so you could log, for example:
 
header="Application Startup. Version ${assembly-version}, PID ${processid}"

Comments: ** Comment from web user: consept **

Is this what you were looking for: http://lowleveldesign.wordpress.com/2012/11/22/nlog-layoutrenderer-for-assembly-version/?

Commented Issue: LogManager.Flush throws exceptions [6227]

MichelZ — Wed, 14 Nov 2012 14:00:13 GMT

Despite having throwsExceptions="false" in the configuration when I called LogManager.Flush(), it rethrew a timeout exception that I think was thrown by the first target in a failback group. I need to Flush because I unload the AppDomain and I don't want to lose a log which gets sent to a remote database using an asynchronous database target.
 
Expected behavior would be for it to simply log the error, it should never throw an unhandled exception that brings down my whole process.
 
This is the error I got when calling flush:
 
 Exception: NLog.NLogRuntimeException: Asynchronous exception has occurred. ---> System.TimeoutException: Timeout.
 
 --- End of inner exception stack trace ---
 at NLog.Common.AsyncHelpers.RunSynchronously(AsynchronousAction action) in c:\NLogBuild\src\NLog\Common\AsyncHelpers.cs:line 226
 at NLog.LogFactory.Flush(TimeSpan timeout) in c:\NLogBuild\src\NLog\LogFactory.cs:line 370
 at Tps.PowerTools.CoreEngine.V5.Processor.Milestone.BatchRunner.Run() in C:\SourceCode\Tps.PowerToolsV1\Trunk\Libraries\CoreEngine\CoreEngine.V5\Processor\Milestone\BatchRunner.cs:line 195
 at Tps.PowerTools.CoreEngine.V5.Processor.Milestone.BatchRunner.Run()
 at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
 at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
 at System.Threading.ThreadHelper.ThreadStart()

Comments: ** Comment from web user: MichelZ **

Any plans on when a new version will be released?

Commented Issue: TraceTarget blocks application when logging error events - Trace.Fail [2599]

thnk2wn — Tue, 13 Nov 2012 22:04:03 GMT

My application - a windows service - stops working when logging errors to TraceTarget. 
The Write method in TraceTarget calls Trace.Fail which causes the application to stop an and popup a retry/abort/ignore dialog.
 
Trace.cs
if (logEvent.Level >= LogLevel.Error)
{
 Trace.Fail(CompiledLayout.GetFormattedMessage(logEvent));
}
else
{
 Trace.WriteLine(CompiledLayout.GetFormattedMessage(logEvent));
}

Comments: ** Comment from web user: thnk2wn **

Any word on when this might be fixed in the NuGet package?

Closed Issue: Client Profile Support [5012]

Xharze — Sun, 07 Oct 2012 18:03:06 GMT

The client profile has been around since .NET 3.5. With .NET 4 and VS2010, it has become far more important. Microsoft has decided that only the client profile will be distributed automatically through Windows Update. So if developers wish to provide applications that run out of the box on up to date systems, they need to use the client profile. As well, VS2010 uses the client profile as the default for a number of project types now. While VS2008 used to compile things with warnings, VS2010 now produces errors when linking against assemblies that aren't client profile-enabled. As such, NLog should support the client profile.
 
I've been involved in moving many projects to the client profile and the most straightforward way has been to remove the reference to System.Web and add a bit of reflection/delegates to move the compile time dependency to runtime. Although I haven't fully analyzed the NLog code base, in the other systems I've dealt with, the actual number of types/properties/methods that aren't in the client profile has been small and they have been easy to eliminate with reflective techniques such as Delegate.CreateDelegate() on methods.
 
I'd be happy to help out in this area. I was originally trying to get something to happen with log4net, but it seems like all the maintainers are gone. I'm definitely hoping we can make some progress on having a client profile-enabled logging framework with NLog.

Comments:

Fixed

Closed Issue: NLog throws exception [4071]

Xharze — Sun, 07 Oct 2012 18:02:54 GMT

When two or more instances of an application is executed in parallel, and they reach the logger at the same time, NLog throws an exception, which causes application to crash.

Comments:

Need more information

Closed Issue: Autoreload not working on *nix systems [3653]

Xharze — Sun, 07 Oct 2012 18:02:35 GMT

Autoreload functionality doesn't work on *nix systems. After a small investigation I've found that in:
XmlLoggingConfiguration.cs:132 (NLog-1.0 Refresh sources)
there's a line: 
string key = Path.GetFullPath(fileName).ToLower(CultureInfo.InvariantCulture);
later that key is written to _visitedFiles which is used to define files that file watcher is supposed to observer. What's the point of invoking "ToLower" function on file path?

Comments:

Moved to https://github.com/NLog/NLog/issues/148

Closed Issue: I'm using longdate, but sometimes dates are in local time instead of UTC [2709]

Xharze — Sun, 07 Oct 2012 18:01:57 GMT

Reported in the forum at post: http://nlog-project.org/forum.html#nabble-tc1685765|a1685765
 
Is this a known bug? Although the LayoutRenderer specifies longdate, sometimes the dates written to the log file are in local time. This happens intermittently and apparently, only when the level is Error and there is a stack trace. NLog version: 1.0.0.505. Here's the target spec:
 
<target name="RollingFileTarget"
 type="File"
 filename="${environment:variable=MYAPP_HOME_FOLDER}\log\MyLog.log"
 layout="${level} ${longdate} ${threadid} ${logger} - ${message} ${exception:format=message,stacktrace:separator=*}"
 archiveAboveSize="4000000"
 archiveFileName="${environment:variable=MYAPP_HOME_FOLDER}\log\Archives\MyLog.{########}.log"
 maxArchiveFiles="250"
 concurrentWrites="true"
 openFileCacheSize="5"
 />

Comments:

Duplicate

Closed Issue: Problem with Target FormControl [2708]

Xharze — Sun, 07 Oct 2012 18:01:42 GMT

Reported in the forum at post: http://nlog-project.org/forum.html#nabble-tc1685764|a1685764
 
Hi,
 
i have a little problem with the target FormControl. I wrote a NLog.config with 3 targets ( File, Debugger, FormControl ). The logger writes successfull all messages to the targets File and Debugger, the FormControl target is ignored by the logger. I attached my config, and the internal Nlog log.
The FormControl is a ToolStripStatusLabel Control.
 
I hope somebody have an idea, thx.
 
NLog.config
nlog.log

Comments:

Moved to https://github.com/NLog/NLog/issues/147

Closed Issue: Problem using the log4jxmlevent layout [2705]

Xharze — Sun, 07 Oct 2012 17:59:58 GMT

Reported in the forum at post: http://nlog-project.org/forum.html#nabble-tc1685658|a1685658
 
Hi All,
 
I'm using the log4jxmlevent layout on a file target. And I've set the includeSourceInfo=true.
 
The output that I'm getting in the log file is missing some data. NLog does not close the log4j:event xml tag.
 
I've set the nlog throwExceptions and the internalLogFile and I get an exception:
Warn Exception in NLog.LayoutRenderers.Log4JXmlEventLayoutRenderer.Append(): System.NullReferenceException: Object reference not set to an iinstance of an object.
at NLog.LayoutRenderers.Log4JXmlEventLayoutRenderer.Append(StringBuilder builder, LogEventInfo logEvent) in E:\My Programs\NLog\NLog\src\LayoutRenderers\Log4JXmlEvent.cs:line 194
at NLog.Layout.GetFormattedMessage(LogEventInfo logEvent) in E:\My Programs\NLog\NLog\src\NLog\Layout.cs:line 142
 
I managed to set a breakpoint in Append() method at line 194 and it seems that it's looking for UserStackTrace in logEvent which returns null.
 
Hope this helps to solve the problem.
 
Dan

Comments:

Moved to https://github.com/NLog/NLog/issues/146

Closed Issue: Custom csv layout doesn't work in nlog 2.0 release [6476]

Xharze — Sun, 07 Oct 2012 17:59:19 GMT

use of config
 
<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 
 
 <targets>
 <target name="logfile" xsi:type="File" fileName="file.txt">
 <layout xsi:type="CsvLayout">
 
 <quoting>All</quoting>
 <quoteChar>"</quoteChar>
 <withHeader>true</withHeader>
 <delimiter>Comma</delimiter>
 <column layout="${event-context:item=col1}" name="column1"/>
 <column layout="${event-context:item=col2}" name="column2"/>
 <column layout="${processtime}" name="column3"/>
 </layout>
 </target>
 </targets>
 <rules>
 <logger name="*" minlevel="Info" writeTo="logfile" />
 </rules>
</nlog>
 
and code
 
 Logger logger = LogManager.GetCurrentClassLogger();
 LogEventInfo myEvent = new LogEventInfo(LogLevel.Info, "", "My debug message");
 myEvent.Properties["col1"]="column1 info"; 
 myEvent.Properties["col2"] = "column2 info";
 logger.Info(myEvent);
 
results in 
 
"column1","column2","column3"
"","","00:00:00.0000"
 
I suspect it's a bug in passing LogEventInfo to a target (when wrapping it in another LogEventInfo)

Comments:

See comment

Closed Issue: Error while using NLog under mono [6462]

Xharze — Sun, 07 Oct 2012 17:58:58 GMT

Hi,
I hope that I did not created twice.
 
I want to use mono and NLog under OpenSuse.
 
First I have created a litle consol application to test NLog.
 
 class Program
 {
 private static Logger logger = LogManager.GetCurrentClassLogger();
 
 static void Main(string[] args)
 {
 logger.Debug("Test");
 }
 }
 
NLog_config file:
 
<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 internalLogFile="/media/log/Nlog_error.log"
 internalLogLevel="Trace"
 autoReload="true">
 <targets>
 <target name="OtherLog" xsi:type="File" fileName="/media/log/Other.log" />
 </targets>
 <rules>
 <logger name="*" minlevel="Trace" writeTo="OtherLog" />
 </rules>
</nlog>
 
RESULT:
 
Missing method .ctor in assembly /media/Debug/NLog.dll, type System.ServiceModel.ServiceContractAttribute
Can't find custom attr constructor image: /media/Debug/NLog.dll mtoken: 0x0a000428
Missing method .ctor in assembly /media/Debug/NLog.dll, type System.ServiceModel.ServiceContractAttribute
Can't find custom attr constructor image: /media/Debug/NLog.dll mtoken: 0x0a000428
Missing method .ctor in assembly /media/Debug/NLog.dll, type System.ServiceModel.ServiceContractAttribute
Can't find custom attr constructor image: /media/Debug/NLog.dll mtoken: 0x0a000428
Missing method .ctor in assembly /media/Debug/NLog.dll, type System.ServiceModel.ServiceContractAttribute
Can't find custom attr constructor image: /media/Debug/NLog.dll mtoken: 0x0a000428
Missing method .ctor in assembly /media/Debug/NLog.dll, type System.ServiceModel.ServiceContractAttribute
Can't find custom attr constructor image: /media/Debug/NLog.dll mtoken: 0x0a000428
Missing method .ctor in assembly /media/Debug/NLog.dll, type System.ServiceModel.ServiceContractAttribute
Can't find custom attr constructor image: /media/Debug/NLog.dll mtoken: 0x0a000428
Missing method .ctor in assembly /media/Debug/NLog.dll, type System.Runtime.Serialization.DataContractAttribute
Can't find custom attr constructor image: /media/Debug/NLog.dll mtoken: 0x0a00042a
Missing method .ctor in assembly /media/Debug/NLog.dll, type System.Runtime.Serialization.DataContractAttribute
Can't find custom attr constructor image: /media/Debug/NLog.dll mtoken: 0x0a00042a
Missing method .ctor in assembly /media/Debug/NLog.dll, type System.Runtime.Serialization.CollectionDataContractAttribute
Can't find custom attr constructor image: /media/Debug/NLog.dll mtoken: 0x0a000434
Missing method .ctor in assembly /media/Debug/NLog.dll, type System.ServiceModel.ServiceContractAttribute
Can't find custom attr constructor image: /media/Debug/NLog.dll mtoken: 0x0a000428
 
Unhandled Exception: System.TypeInitializationException: An exception was thrown by the type initializer for TestNlog.Program ---> NLog.NLogConfigurationException: Exception occurred when loading configuration from /media/Debug/NLog.config ---> System.ArgumentException: Target cannot be found: 'File'
 at NLog.Config.Factory`2[NLog.Targets.Target,NLog.Targets.TargetAttribute].CreateInstance (System.String name) [0x00000] in <filename unknown>:0
 at NLog.Config.XmlLoggingConfiguration.ParseTargetsElement (NLog.Config.NLogXmlElement targetsElement) [0x00000] in <filename unknown>:0
 at NLog.Config.XmlLoggingConfiguration.ParseNLogElement (NLog.Config.NLogXmlElement nlogElement, System.String baseDirectory) [0x00000] in <filename unknown>:0
 at NLog.Config.XmlLoggingConfiguration.ParseTopLevel (NLog.Config.NLogXmlElement content, System.String baseDirectory) [0x00000] in <filename unknown>:0
 at NLog.Config.XmlLoggingConfiguration.Initialize (System.Xml.XmlReader reader, System.String fileName, Boolean ignoreErrors) [0x00000] in <filename unknown>:0
 --- End of inner exception stack trace ---
 at NLog.Config.XmlLoggingConfiguration.Initialize (System.Xml.XmlReader reader, System.String fileName, Boolean ignoreErrors) [0x00000] in <filename unknown>:0
 at NLog.Config.XmlLoggingConfiguration..ctor (System.String fileName) [0x00000] in <filename unknown>:0
 at NLog.LogFactory.get_Configuration () [0x00000] in <filename unknown>:0
 at NLog.LogFactory.GetLogger (NLog.LoggerCacheKey cacheKey) [0x00000] in <filename unknown>:0
 at NLog.LogFactory.GetLogger (System.String name) [0x00000] in <filename unknown>:0
 at NLog.LogManager.GetCurrentClassLogger () [0x00000] in <filename unknown>:0
 at TestNlog.Program..cctor () [0x00000] in <filename unknown>:0
 --- End of inner exception stack trace ---
 
The same application works under mono 2.8 event if it never finish.
 
Could you help me please.

Comments:

See comment

Closed Issue: Tweak for Full Trust : variant of No Log File, SecurityException, Partial Trust [6400]

Xharze — Sun, 07 Oct 2012 17:58:23 GMT

The issue of SecurityException, while using in partial trust environment - web application, is raised at two points.
 
To resolve the Partial Trust error, modify the AssemblyCofig.cs file of NLog project and add following
[Code]
//System.Security.SecurityException: That assembly does not allow partially trusted callers.
[assembly: System.Security.AllowPartiallyTrustedCallers()]
[/Code]
Also make sure the project properties has the Signature assigned.
 
After doing the above workaround, you will face following issues, that causes no file issue, securityexception etc. [The issue of not supporting Partial Trust is known issue and noted in release note.]
 
1] while accessing the nlog.config : XmlLoggingConfiguration.AppConfig : access to System.Configuration.ConfigurationManager
Work around : use web.config
 
2] while loading configuration from web.config and creating a FileSystemWatcher internally.
Work around following code change
File: LogFactory.cs
Line 164 
[Code]
if (this.config != null)
{
 Dump(this.config);
 if (AppDomain.CurrentDomain.IsFullyTrusted)
 {
 this.watcher.Watch(this.config.FileNamesToWatch);
 }
}
[/Code]
 
Hope this helps team and community.

Comments:

Moved to https://github.com/NLog/NLog/issues/144