1

Resolved

Latest version (0.12.2.0) doesn't work with NLog 4

description

I tried with NLog 4.2.3 and 4.1.2.

comments

yarseyah wrote Feb 6, 2016 at 11:23 AM

Hi,

It did work with 4.0.1 (there is a tester in the repository), but that's not a great answer.

Since nLog has so many variables, can you upload your nlog.config (or appropriate section of app.config)?

Some other variables to consider, ipv6 causes some problems. When you define the destination for the log output (where Sentinel is placed), one trick is to force nLog into using ipv4, this can be done by changing the following:
address="udp://127.0.0.1:9999"
to
address="udp4://127.0.0.1:9999"
R

yarseyah wrote Feb 6, 2016 at 2:42 PM

Hmmm. You're right, it is broken.

Fixed and released 0.12.3.0, please give this a go. Works for me now.

https://sentinel.codeplex.com/releases/view/619737

MrKhoa wrote Feb 15, 2016 at 3:01 AM

Hi,

Version 0.12.4.0 doesn't work for me, I didn't get a chance to try with 0.12.3.0, but the latest version of Sentinel doesn't work with latest version of NLog, I tried to force it using ipv4 also.

csdelan wrote Jul 22, 2016 at 11:31 PM

Version 0.12.4.0 also doesn't work for me with nLog. Is this going to be fixed?

yarseyah wrote Jul 23, 2016 at 2:57 PM

I have downloaded both 0.12.3.0 and 0.12.4.0 and used against the test application (uses nLog 4.2.3) and everything works fine.

What configuration are you using?

csdelan wrote Jul 23, 2016 at 7:45 PM

I can't post it now because it is at work, but I tried many different configurations in nLogViewer target and Network target. I tried UDP, TCP UDP4, 127.0.0.1, real local IP address, none of it worked. When I backtracked to 0.12.0.0 though (after I posted the above message), it started working.

csdelan wrote Jul 23, 2016 at 7:46 PM

and using the latest version of nlog