[syslog-ng] syslog-ng not reconnecting when using tcp

[prasad padiyar]

Thanks for the kind reply.

> 1. How many number of times the connection is retried.

It is retried every time_reopen() seconds until it succeeds, or
syslog-ng is stopped.

But somehow I do not see this happening in my case. Is there some
configuration in syslog-ng.conf that does this (retrying until it succeeds
or syslog-ng is stopped) ?



On Wed, Apr 2, 2014 at 5:49 PM, Gergely Nagy <algernon at balabit.hu> wrote:

> prasad padiyar <prasad.padiyar at gmail.com> writes:
>
> [...]
>
> > syslog-ng version:
> >
> > syslog-ng 1.6.12
> [...]
>
> > I got a reply from one of the balabit guys that i have to use version
> 3.4.
>
> Indeed, 1.6 is ancient.
>
> > 1. How many number of times the connection is retried.
>
> It is retried every time_reopen() seconds until it succeeds, or
> syslog-ng is stopped.
>
> > 2. when exactly the connection retry happens (when will it get to know
> when
> > it has to retry)
>
> The retry happens after syslog-ng disconnected (and syslog-ng
> disconnects when it notices a network error, usually during a write() or
> a poll()), after time_reopen() seconds have passed.
>
> > 3. time_reopen(40), what exactly is 40seconds here.
>
> The 40 seconds here is the time spent with the destination suspended
> after an error, before trying to reconnect again.
>
> Hope that answers your questions!
>
> --
> |8]
>
>
> ______________________________________________________________________________
> 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
>
>


-- 
Regards,
Prasad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.balabit.hu/pipermail/syslog-ng/attachments/20140402/4652850b/attachment.htm