New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logging stops using archiving and async target #1826
Comments
Please fill in the template, thanks! |
Type
NLog version: 4.3.11 Platform: .Net 4.5 Current NLog config see attached file In case of a BUG:
|
thx! |
has updated your internallog and removed your email adresses and smtp address |
Can you please remove the smtp entry from the internal log also? Thx. |
yes done :) |
@ChristianHoe Could you try and add OpenFileCacheTimeout=10 to the file-target configuration? And see if the problem is "fixed". |
@ChristianHoe I'm adding more internal logging. Could you test it with a trace internal log soon? |
Sorry, I am on vacation till begin of january. What is the best way to get the new tracing? Nuget? |
@ChristianHoe have a good vacation!
I mean the internal log as described here: https://github.com/NLog/NLog/wiki/Internal-logging |
Maybe the question was how to get the build that includes this PR: #1872 ? |
Ah, short-link for this case: https://ci.appveyor.com/api/buildjobs/6f8felbsc9agdfe5/artifacts/build%2Fbin%2Frelease%2FNuGetPackages%2FNLog.4.4.nupkg |
Hi,
I tried to use archiving (DateAndSequence) in combination with async target and keepFileOpen.
Testing this feature locally with our database log worked fine and the archive files where created like expected (Database 20161205.1.log, Database 20161205.2.log ....).
Putting same configuration under stress running multiple WCF-Requests causing the logging to stop. Leaving a valid log file like Database ${522or5ae}.0.log and no further activity.
First I thought it could be something like #1029 but updating from 3.2.0 to 4.3.11 did not help. It looks like the logger dies silently the very moment the current file is archived (see internal log).
The WCF Service is running on Windows Server 2008 and .Net-Framework 4.5.1.
My current work around is using the archiving on daily base only. but files with size of 1.5 GB and more are not easy to handle.
nlog.config.txt
nlog-internal.log.txtThe text was updated successfully, but these errors were encountered: