Repository navigation
Issues with logging in WorkerService project after upgrading to v6.0.1 #5928
Description
Hi! Thanks for reporting this bug!
NLog version: 6.0.1
Platform: .NET9 (Worker Service)
Current NLog config (xml or C#, if relevant)
<?xml version="1.0" encoding="utf-8" ?>
<!-- XSD manual extracted from package NLog.Schema: https://www.nuget.org/packages/NLog.Schema-->
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
autoReload="true"
internalLogFile=".\logs\internal.log"
internalLogToConsole="true"
throwConfigExceptions="true"
internalLogLevel="Info">
<!-- the targets to write to -->
<targets>
<!-- write logs to file -->
<target xsi:type="File" name="fileLog" fileName=".\logs\nlog-all-${shortdate}.log"
layout="${date}|${level:uppercase=true}|${message} ${exception}|${logger}|${all-event-properties}" />
</targets>
<!-- rules to map from logger name to target -->
<rules>
<logger name="*" minlevel="Info" writeTo="fileLog" />
<logger name="*" minlevel="Error" writeTo="fileLog" />
<!--<logger name="*" minlevel="Error" writeTo="fileLog, mailLog" />-->
</rules>
</nlog>
<!--link https://github.com/nlog/NLog/wiki/Mail-target-->-
What is the current result?
There is no output for both the internal log and the application log. -
What is the expected result?
There should be at least 1 log file. -
Did you check the Internal log?
Yes, I did. Added some configuration, but nothing yet -
Please post full exception details (message, stacktrace, inner exceptions)
Attached is the screenshot showing what the logger looks like when inspected. -
Are there any workarounds? yes/no
No workaround that I know of. -
Is there a version in which it did work?
Downgrading to version 5.4.0 solves the issue -
Can you help us by writing a unit test?
Yes, I can.
I have also developed a minimal reproducible version here: https://github.com/elfico/nlog-test
Activity
welcome commentedon Jul 14, 2025
Hi! Thanks for opening your first issue here! Please make sure to follow the issue template - so we could help you better!
[-]Issues with logging in WorkerService project after upgrading to v6.0.0[/-][+]Issues with logging in WorkerService project after upgrading to v6.0.1[/+]snakefoot commentedon Jul 15, 2025
Yes the new NLog XmlParser introduced with NLog v6, needs some more tender-loving-and-care. I have now created the following improvements:
</nlog>As a work-around until NLog v6.0.2. then I recommend removing this from your
NLog.config-file after the</nlog>-end-tag:<!--link https://github.com/nlog/NLog/wiki/Mail-target-->Thank you again for this feedback, and helping with improving the NLog-logging-library.
elfico commentedon Jul 15, 2025
Thanks!
It's working now!
snakefoot commentedon Jul 15, 2025
Happy to hear, soon NLog v6.0.2 will be out, so others will not be blocked by the same issue.
snakefoot commentedon Jul 20, 2025
NLog v6.0.2 has been released:
Thank you again for the feedback
elfico commentedon Oct 21, 2025
Hi @snakefoot
I am experiencing similar issue when I updated to the latest NLog v6.0.5
Here is my configuration:
And content of my internal.log
snakefoot commentedon Oct 21, 2025
Please don't awaken/reopen old closed issues for reporting new issues, instead open a new issue.
P.S. From you looking at the NLog InternalLogger-output then there are no errors, so I'm guessing the issue is
<logger name="*" minlevel="Error" writeTo="fileLog" />and your application is not logging any errors (minlevel="Error"). Remember to check NLog Troubleshooting Guide before reporting issues.This is the output from NLog InternalLogger when using your NLog.config in an example app that generates Error-output (File is successfully created and has the expected output):
elfico commentedon Oct 21, 2025
Thanks for the quick response.
Sorry about that. Will create a new issue going forward.
I followed the troubleshooting guide, but could not resolve the issue. The application is logging errors. Plus, it is working with v6.0.2 and only stopped when I updated the NuGet.
So, same code and config, but different updated NuGet packages.