[syslog-ng] is connection broken logged?
Kevin
kkadow at gmail.com
Sat Jul 9 05:50:43 CEST 2005
On 7/8/05, Richard Legault <rlegault at sandvine.com> wrote:
> We are using version 1.6.0rc4
>
> As part of our regression testing we attempt to send a log message to a host that is non-existent (123.124.125.126)
> We expect to see in our log the error message Connection Broken, we are not seeing that.
But it's a UDP destination, so syslog-ng actually could (assuming your server
has a default route set) generate a UDP packet with that destination IP...
it just never actually arrives.
IOW, UDP is connectionless, so there is no connection to be broken.
> here is the parts of our conf file that are relevant
>
>
> destination tcsvlogfile { file("/var/log/svlogtc"); };
> destination badsyslogsrvr { udp("123.124.125.126" port(514)); };
>
> filter f_ic17 { match( "ic_17 test message" ); };
>
> log { source(src); filter(f_ic17); destination(badsyslogsrvr); };
> log { source(src); destination(tcsvlogfile); };
It would be interesting to try the same test, but with a TCP
destination instead.
Kevin Kadow
More information about the syslog-ng
mailing list