[syslog-ng] Upon syslog-ng reload /restart a flood of logs is received at a tcp port (destination)

Mitzki, András andras.mitzki at balabit.com
Wed Oct 14 10:31:07 CEST 2015


Hello Shruthi Rao,

You are using an old version of syslog-ng.
Please upgrade it to the newer version. If the issue is still exist we can
help easier.
You can find information about the installation of newer version to your
system at:
https://syslog-ng.gitbooks.io/getting-started/content/chapters/chapter_0/section_2.html
and at
https://czanik.blogs.balabit.com/2015/09/balabits-syslog-ng-at-the-annual-susecon/

Best regards
Andras


On Fri, Oct 9, 2015 at 1:48 PM, Shruthi Rao <shruthirao5 at gmail.com> wrote:

>
> I have configured a destination in syslog to a tcp port on localhost
>
> options { long_hostnames(off); sync(0); perm(0640); stats(3600); };
>
> source src { internal(); unix-dgram("/dev/log"); udp(); };
>
> destination mgagent{ tcp("127.0.0.1" port(5009) template("$TAG $HOST
> $PROGRAM $MSGONLY\n")); };
>
> I have a tcp server n the localhost ,receiving logs on this port and it
> does further processing .
>
> Whenever syslog-ng is reloaded or restarted and te tcp server is running ,
> a flood of the logs is sent on this tcp port ( which is handled by the tcp
> server) , but this is not wanted. The logs which were already sent before
> restart is sent repeatedly . Is there any way to stop or prevent this .
>
> syslog version is syslog-ng 2.0.9 on SLES 11 SP3
>
> -Thanks
>
>
> ______________________________________________________________________________
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> Documentation:
> http://www.balabit.com/support/documentation/?product=syslog-ng
> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20151014/f7b1f3ac/attachment.htm 


More information about the syslog-ng mailing list