[syslog-ng] Behaviour with unavailable TCP destination

Scheidler, Balázs balazs.scheidler at balabit.com
Sun Jul 19 21:47:24 CEST 2015


Yes, syslog-ng continuously tries to connect to the server and sends
messages to the server buffered until that point.
On Jul 17, 2015 12:31 PM, "ZeroUno" <zerozerounouno at gmail.com> wrote:

> Hello,
> I was wondering what happens when you define a tcp() destination in
> syslog-ng.conf and then the destination is temporarily not available.
> I was not able to find the answer in the docs.
>
> Are any messages lost?
> Or are they kept somewhere and sent again when the destination becomes
> available again?
>
> Thank you.
>
> --
> 01
>
>
> ______________________________________________________________________________
> 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/20150719/66213374/attachment.htm 


More information about the syslog-ng mailing list