Log4Net and Windows 7

[KazMax]

I have a software project which I was previously developing under Windows XP. I recently upgraded to Windows 7 (64bit release candidate) and transferred the project across. Everything works perfectly, except Log4Net. And I can't get it working.

I had previously defined my Log4Net setup to record messages in both a log file and also sent via UDP to Log4View. The logging to file works fine, but no messages ever make it to Log4View.

I immediately thought "firewall issue". I couldn't find a set of firewall rules which would allow the UDP (or TCP) traffic from Log4Net, so I switched the firewall off - it made no difference, I still didn't get any messages from Log4Net.

I've had broadly similar problems with SMTP/POP3/IMAP for a Mail Server I was trying to install on Windows 7 (and also Windows Server 2008 which is based upon the same code base), in that I couldn't get that mail server to connect to the outside world.

Is there something I'm missing with Windows 7?

[steven higgan-3]

There is this _very_ old bug in the udp appender code that crops up if
you have the IPV6 protocol installed on the listening machine.

Your options wait for a blessed release, find the patch and apply it
yourself, try your luck with head.

Mabye a forth option is to make a UdpAppenderThatWorks based off the
UdpAppender class and use that.

On Tue, Jul 21, 2009 at 5:12 PM, KazMax<andrew@...> wrote:

>
> I have a software project which I was previously developing under Windows XP.
> I recently upgraded to Windows 7 (64bit release candidate) and transferred
> the project across. Everything works perfectly, except Log4Net. And I can't
> get it working.
>
> I had previously defined my Log4Net setup to record messages in both a log
> file and also sent via UDP to Log4View. The logging to file works fine, but
> no messages ever make it to Log4View.
>
> I immediately thought "firewall issue". I couldn't find a set of firewall
> rules which would allow the UDP (or TCP) traffic from Log4Net, so I switched
> the firewall off - it made no difference, I still didn't get any messages
> from Log4Net.
>
> I've had broadly similar problems with SMTP/POP3/IMAP for a Mail Server I
> was trying to install on Windows 7 (and also Windows Server 2008 which is
> based upon the same code base), in that I couldn't get that mail server to
> connect to the outside world.
>
> Is there something I'm missing with Windows 7?
> --
> View this message in context: http://www.nabble.com/Log4Net-and-Windows-7-tp24581800p24581800.html
> Sent from the Log4net - Dev mailing list archive at Nabble.com.
>
>

[KazMax]

That stands to reason. Whilst I am aware of IPV6 (it has been around a few years but hasn't been widely implemented) I haven't actually had to deal with it in earnest before now. I guess now seems like a good time to learn!

When you say "find the patch", is there such a thing? If there is I'm not sure whether the patch would be for the operating system, Log4Net, or something else?

Thanks for your comments - very helpful to point me in the right direction (to begin with).

Andrew

steven higgan-3 wrote:

There is this _very_ old bug in the udp appender code that crops up if
you have the IPV6 protocol installed on the listening machine.

Your options wait for a blessed release, find the patch and apply it
yourself, try your luck with head.

Mabye a forth option is to make a UdpAppenderThatWorks based off the
UdpAppender class and use that.

On Tue, Jul 21, 2009 at 5:12 PM, KazMax<[e-mail]> wrote:
>
> I have a software project which I was previously developing under Windows XP.
> I recently upgraded to Windows 7 (64bit release candidate) and transferred
> the project across. Everything works perfectly, except Log4Net. And I can't
> get it working.
>
> I had previously defined my Log4Net setup to record messages in both a log
> file and also sent via UDP to Log4View. The logging to file works fine, but
> no messages ever make it to Log4View.
>
> I immediately thought "firewall issue". I couldn't find a set of firewall
> rules which would allow the UDP (or TCP) traffic from Log4Net, so I switched
> the firewall off - it made no difference, I still didn't get any messages
> from Log4Net.
>
> I've had broadly similar problems with SMTP/POP3/IMAP for a Mail Server I
> was trying to install on Windows 7 (and also Windows Server 2008 which is
> based upon the same code base), in that I couldn't get that mail server to
> connect to the outside world.
>
> Is there something I'm missing with Windows 7?
> --
> View this message in context: http://www.nabble.com/Log4Net-and-Windows-7-tp24581800p24581800.html
> Sent from the Log4net - Dev mailing list archive at Nabble.com.
>
>

[KazMax]

For anyone who may be interested, doing a quick Google using the following words provides a rich set of interesting articles on this topic:

log4net ipv6 udp appender

Definitely looks like IPV6 needing the eye of Mordor focussed on it.....

Andrew


That stands to reason. Whilst I am aware of IPV6 (it has been around a few years but hasn't been widely implemented) I haven't actually had to deal with it in earnest before now. I guess now seems like a good time to learn!

When you say "find the patch", is there such a thing? If there is I'm not sure whether the patch would be for the operating system, Log4Net, or something else?

Thanks for your comments - very helpful to point me in the right direction (to begin with).

Andrew

steven higgan-3 wrote:

There is this _very_ old bug in the udp appender code that crops up if
you have the IPV6 protocol installed on the listening machine.

Your options wait for a blessed release, find the patch and apply it
yourself, try your luck with head.

Mabye a forth option is to make a UdpAppenderThatWorks based off the
UdpAppender class and use that.

On Tue, Jul 21, 2009 at 5:12 PM, KazMax<[e-mail]> wrote:
>
> I have a software project which I was previously developing under Windows XP.
> I recently upgraded to Windows 7 (64bit release candidate) and transferred
> the project across. Everything works perfectly, except Log4Net. And I can't
> get it working.
>
> I had previously defined my Log4Net setup to record messages in both a log
> file and also sent via UDP to Log4View. The logging to file works fine, but
> no messages ever make it to Log4View.
>
> I immediately thought "firewall issue". I couldn't find a set of firewall
> rules which would allow the UDP (or TCP) traffic from Log4Net, so I switched
> the firewall off - it made no difference, I still didn't get any messages
> from Log4Net.
>
> I've had broadly similar problems with SMTP/POP3/IMAP for a Mail Server I
> was trying to install on Windows 7 (and also Windows Server 2008 which is
> based upon the same code base), in that I couldn't get that mail server to
> connect to the outside world.
>
> Is there something I'm missing with Windows 7?
> --
> View this message in context: http://www.nabble.com/Log4Net-and-Windows-7-tp24581800p24581800.html
> Sent from the Log4net - Dev mailing list archive at Nabble.com.
>
>

[KazMax]

Via Google I found the following article. As soon as I had entered that UdpAppender for my Log4Net installation it started working:

http://markmail.org/message/2nlxkf5i6v3xvda7#query:+page:1+mid:2nlxkf5i6v3xvda7+state:results

IPV6 is the cause of this problem. Thanks for the help to get my onto this solution!

Andrew


For anyone who may be interested, doing a quick Google using the following words provides a rich set of interesting articles on this topic:

log4net ipv6 udp appender

Definitely looks like IPV6 needing the eye of Mordor focussed on it.....

Andrew

KazMax wrote:

That stands to reason. Whilst I am aware of IPV6 (it has been around a few years but hasn't been widely implemented) I haven't actually had to deal with it in earnest before now. I guess now seems like a good time to learn!

When you say "find the patch", is there such a thing? If there is I'm not sure whether the patch would be for the operating system, Log4Net, or something else?

Thanks for your comments - very helpful to point me in the right direction (to begin with).

Andrew

steven higgan-3 wrote:

There is this _very_ old bug in the udp appender code that crops up if
you have the IPV6 protocol installed on the listening machine.

Your options wait for a blessed release, find the patch and apply it
yourself, try your luck with head.

Mabye a forth option is to make a UdpAppenderThatWorks based off the
UdpAppender class and use that.

On Tue, Jul 21, 2009 at 5:12 PM, KazMax<[e-mail]> wrote:
>
> I have a software project which I was previously developing under Windows XP.
> I recently upgraded to Windows 7 (64bit release candidate) and transferred
> the project across. Everything works perfectly, except Log4Net. And I can't
> get it working.
>
> I had previously defined my Log4Net setup to record messages in both a log
> file and also sent via UDP to Log4View. The logging to file works fine, but
> no messages ever make it to Log4View.
>
> I immediately thought "firewall issue". I couldn't find a set of firewall
> rules which would allow the UDP (or TCP) traffic from Log4Net, so I switched
> the firewall off - it made no difference, I still didn't get any messages
> from Log4Net.
>
> I've had broadly similar problems with SMTP/POP3/IMAP for a Mail Server I
> was trying to install on Windows 7 (and also Windows Server 2008 which is
> based upon the same code base), in that I couldn't get that mail server to
> connect to the outside world.
>
> Is there something I'm missing with Windows 7?
> --
> View this message in context: http://www.nabble.com/Log4Net-and-Windows-7-tp24581800p24581800.html
> Sent from the Log4net - Dev mailing list archive at Nabble.com.
>
>