[syslog-ng] "Error resolving hostname" for UDP Destination
balazs.scheidler at balabit.com
Sat Aug 22 07:20:48 CEST 2015
Earlier syslog-ng immediately exited at startup, now it is considering dns
resolution errors just like connection failures so time-reopen applies.
Time-reopen defaults to 60 seconds as I remember as well and I can't
remember any patch that would have changed it.
On Aug 22, 2015 1:01 AM, "David Hauck" <davidh at netacquire.com> wrote:
> Hi Fabien,
> On Monday, June 15, 2015 7:08 AM, I wrote:
> > On Monday, June 15, 2015 12:50 AM Fabien Wernli wrote:
> >> Hi David,
> >> On Fri, Jun 12, 2015 at 05:09:03PM +0000, David Hauck wrote:
> >>> Starting syslog-ng: Error resolving hostname;
> >>> host='test.nacc.netacquire.dom' Error initializing message pipeline;
> >>> Unfortunately, this results in the entire process failing to start.
> >> This looks a hell lot like a resolved issue  on github
> >>  https://github.com/balabit/syslog-ng/issues/318
> > Yes, indeed! And this looks to have been included in v3.6.3 - I'll give
> this a try.
> I've finally had a chance to test this and see that it indeed fixes
> outright error. However, I now see the following messages appear every 10s:
> 20150821 15:54:37.994 err syslog(syslog-ng):Error resolving hostname;
> 20150821 15:54:37.994 err syslog(syslog-ng):Initiating connection failed,
> reconnecting; time_reopen='10'
> Is there a way to change the timeout? Is this the time-reopen global
> option? Besides DNS lookup retries, what other operations are subject to
> this timeout? Finally, the default (3.7) OSE documentation indicates the
> time-reopen default is 60s (not 10s like I'm seeing).
> Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng
> FAQ: http://www.balabit.com/wiki/syslog-ng-faq
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the syslog-ng