[syslog-ng] startup and network sources

[Scheidler, Balázs]

You mean bind address is specified by dns? You could add that to the hosts
file.

Bazsi

On Wed, Apr 17, 2019, 23:48 Evan Rempel <erempel at uvic.ca wrote:

> I've been looking at an interesting scenario on Redhat 7 (systemd) where
> syslog-ng fails to start because it can not resolve a network source name.
> This happens because the network has not started. Systemd attempts to
> restart syslog-ng a few times and then decides that  it is restarting
> syslog-ng too quickly and gives up on it.
>
>
> 2019-04-17T05:13:30.009 daemon.warning systemd[1]: start request repeated
> too quickly for syslog-ng.service
> 2019-04-17T05:13:30.010 daemon.err systemd[1]: Failed to start System
> Logger Daemon.
> 2019-04-17T05:13:30.010 daemon.notice systemd[1]: Unit syslog-ng.service
> entered failed state.
> 2019-04-17T05:13:30.010 daemon.warning systemd[1]: syslog-ng.service
> failed.
>
>
> My first reaction was to add the "Wants=network-online.target" to the
> service definition to make syslog-ng start after the network has started,
> but that would mean that if I boot up without a network that syslog-ng
> would never start, and that seems incorrect to me.
>
> Is there a way to to configure a network source to be optional and
> continue to retry binding to it after startup?
>
> How do others handle this issue?
>
> --
> Evan
>
>
> ______________________________________________________________________________
> 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/20190418/bdb9f919/attachment.html>