You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by Stromský Josef <jo...@elvac.eu> on 2010/02/03 17:57:30 UTC
Log4net UDP Appender and Chainsaw on Windows 7
Dear Sirs.
We were using the log4net with chainsaw (over UDP) on the WinXP for a few years with absolutely no complications. However, once we upgraded to Windows 7, messages sent over UDP did not reach the chainsaw. We tried almost everything. Is this a known issue or do you have any clue for us.
Thank you for any advice.
Regards,
Josef Stromsky
RE: Log4net UDP Appender and Chainsaw on Windows 7
Posted by Stromský Josef <jo...@elvac.eu>.
Thank you for your swift reply. Sorry I did not mention, however the log4net library and chainsaw is running on the same computer and firewall is down.
From: Scott Deboy [mailto:scott.deboy@gmail.com]
Sent: Wednesday, February 03, 2010 7:16 PM
To: Log4NET Dev
Subject: Re: Log4net UDP Appender and Chainsaw on Windows 7
I'd use something like wireshark on the destination machine to ensure the machine can see the udp packets on the network. I'd suggest you're seeing a Windows-specific network firewall issue (Windows is probably blocking UDP traffic to your machine unless you explicitly allow the box to receive the UDP traffic).
Scott
2010/2/3 Stromský Josef <jo...@elvac.eu>
Dear Sirs.
We were using the log4net with chainsaw (over UDP) on the WinXP for a few years with absolutely no complications. However, once we upgraded to Windows 7, messages sent over UDP did not reach the chainsaw. We tried almost everything. Is this a known issue or do you have any clue for us.
Thank you for any advice.
Regards,
Josef Stromsky
Re: Log4net UDP Appender and Chainsaw on Windows 7
Posted by Scott Deboy <sc...@gmail.com>.
I'd use something like wireshark on the destination machine to ensure the
machine can see the udp packets on the network. I'd suggest you're seeing a
Windows-specific network firewall issue (Windows is probably blocking UDP
traffic to your machine unless you explicitly allow the box to receive the
UDP traffic).
Scott
2010/2/3 Stromský Josef <jo...@elvac.eu>
> Dear Sirs.
>
> We were using the log4net with chainsaw (over UDP) on the WinXP for a few
> years with absolutely no complications. However, once we upgraded to Windows
> 7, messages sent over UDP did not reach the chainsaw. We tried almost
> everything. Is this a known issue or do you have any clue for us.
>
> Thank you for any advice.
>
> Regards,
>
> Josef Stromsky
>
RE: Log4net UDP Appender and Chainsaw on Windows 7
Posted by Parx Shearer <Pa...@medhost.com>.
Taking a shot in the dark, perhaps it is an ipv4/ipv6 problem as discovered by KazMax.
-----Original Message-----
From: KazMax [mailto:andrew@kazmax.co.uk]
Sent: Tuesday, July 21, 2009 6:02 AM
To: log4net-dev@logging.apache.org
Subject: Re: Log4Net and Windows 7 - SOLUTION FOUND!
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
KazMax wrote:
>
> 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<an...@kazmax.co.uk> 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.
>>>>
>>>>
>>>
>>>
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Log4Net-and-Windows-7-tp24581800p24585684.html
Sent from the Log4net - Dev mailing list archive at Nabble.com.
Regards,
Parx Shearer
MEDHOST, Inc.
From: Stromský Josef [mailto:josef.stromsky@elvac.eu]
Sent: Wednesday, February 03, 2010 10:58 AM
To: log4net-dev@logging.apache.org
Subject: Log4net UDP Appender and Chainsaw on Windows 7
Dear Sirs.
We were using the log4net with chainsaw (over UDP) on the WinXP for a few years with absolutely no complications. However, once we upgraded to Windows 7, messages sent over UDP did not reach the chainsaw. We tried almost everything. Is this a known issue or do you have any clue for us.
Thank you for any advice.
Regards,
Josef Stromsky
unsubscribe
Posted by Marcin Skoczylas <Ma...@pb.edu.pl>.
unsubscribe
Re: Log4net UDP Appender and Chainsaw on Windows 7
Posted by Scott Deboy <sc...@gmail.com>.
Another option you may find useful: use a file appender instead of a UDP
appender, and configure Chainsaw to use a LogFilePatternReceiver (which will
parse and tail the log file).
There are two versions of LogFilePatternReceiver - the 'regular' version
(which can process files using file: and http: URLs) and the VFS receiver,
which extends this ability to include support for files accessible via the
Apache Jakarta Commons VFS library (for example, log files stored on an
ssh-accessible server or a remote windows share).
You can find example LogFilePatternReceiver configurations from Chainsaw's
Welcome tab. The documentation for receivers is available from Chainsaw's
help/receiver javadoc menu.
Here's the link to the VFS supported file systems:
http://commons.apache.org/vfs/filesystems.html
Scott
On Thu, Feb 4, 2010 at 12:55 AM, Ulrich Proeller <
ulrich.proeller@prosa-gmbh.de> wrote:
>
> Hello Josef,
>
> this is a known problem with log4net 1.2.10 and Windows Vista/7.
> Caused by the additional support of the IPv6 protocoll, the UDP appender in
> log4net 1.2.10.0 doesn't work, if the parameter "RemoteAddress" is set to
> the "normal" Value 127.0.0.1. A workaround is to set the localhost address
> to 127.0.0.2 instead.
>
> Of course, you can also use Log4View instead of Chainsaw and utilize more
> reliable the TCP appender which comes with Log4View (www.log4view.com) ;-)
> --
> View this message in context:
> http://old.nabble.com/Log4net-UDP-Appender-and-Chainsaw-on-Windows-7-tp27439707p27449484.html
> Sent from the Log4net - Dev mailing list archive at Nabble.com.
>
>
Re: Log4net UDP Appender and Chainsaw on Windows 7
Posted by gecon27 <ge...@gmail.com>.
Hello,
What if I want to redirect output to another machine (WinXP), running a
log4net UDP viewer?
On the 64-bit machine (Windows 2008), I set in "RemoteAddress" the IPv4
address of that machine (WinXP), but it doesn't work (no UDP packages are
generated).
Any ideas?
Thank you,
Ioannis
Ulrich Proeller wrote:
>
> Hello Josef,
>
> this is a known problem with log4net 1.2.10 and Windows Vista/7.
> Caused by the additional support of the IPv6 protocoll, the UDP appender
> in log4net 1.2.10.0 doesn't work, if the parameter "RemoteAddress" is set
> to the "normal" Value 127.0.0.1. A workaround is to set the localhost
> address to 127.0.0.2 instead.
>
> Of course, you can also use Log4View instead of Chainsaw and utilize more
> reliable the TCP appender which comes with Log4View (www.log4view.com) ;-)
>
--
View this message in context: http://old.nabble.com/Log4net-UDP-Appender-and-Chainsaw-on-Windows-7-tp27439707p28386831.html
Sent from the Log4net - Dev mailing list archive at Nabble.com.
Re: Log4net UDP Appender and Chainsaw on Windows 7
Posted by Ulrich Proeller <ul...@prosa-gmbh.de>.
Hello Josef,
this is a known problem with log4net 1.2.10 and Windows Vista/7.
Caused by the additional support of the IPv6 protocoll, the UDP appender in
log4net 1.2.10.0 doesn't work, if the parameter "RemoteAddress" is set to
the "normal" Value 127.0.0.1. A workaround is to set the localhost address
to 127.0.0.2 instead.
Of course, you can also use Log4View instead of Chainsaw and utilize more
reliable the TCP appender which comes with Log4View (www.log4view.com) ;-)
--
View this message in context: http://old.nabble.com/Log4net-UDP-Appender-and-Chainsaw-on-Windows-7-tp27439707p27449484.html
Sent from the Log4net - Dev mailing list archive at Nabble.com.