[syslog-ng] syslog-ng restarts due to interface not ready

[Alexandre Santos]

Hi,

I have a configuration where one of my sources is a syslog source:

syslog(ip(127.1.1.1) transport("udp") port(514) keep-alive(no));


But when the system starts up, the interface is not ready yet, and I get
the following errors:


Jun 26 09:17:50 localhost systemd[1]: Starting System Logger Daemon...
Jun 26 09:17:52 localhost syslog-ng[2301]: [2020-06-26T09:17:52.485148]
WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!;
Jun 26 09:17:52 localhost syslog-ng[2301]: [2020-06-26T09:17:52.487159]
Current position not matches to the saved cursor position, seek to head;
cursor='s=f62c0e80f50948deb29cf2d28230a
Jun 26 09:17:52 localhost syslog-ng[2301]: [2020-06-26T09:17:52.487867]
Error resolving hostname; host='127.1.1.1'
Jun 26 09:17:52 localhost syslog-ng[2301]: [2020-06-26T09:17:52.487878]
Error initializing message pipeline; plugin_name='syslog',
location='/etc/syslog-ng/syslog-ng.conf:43:5'
Jun 26 09:17:52 localhost systemd[1]: syslog-ng.service: Main process
exited, code=exited, status=2/INVALIDARGUMENT
Jun 26 09:17:52 localhost systemd[1]: syslog-ng.service: Failed with result
'exit-code'.
Jun 26 09:17:52 localhost systemd[1]: Failed to start System Logger Daemon.
Jun 26 09:17:52 localhost systemd[1]: syslog-ng.service: Service
RestartSec=100ms expired, scheduling restart.
Jun 26 09:17:52 localhost systemd[1]: syslog-ng.service: Scheduled restart
job, restart counter is at 1.


When the systemd reaches the 5 attempts it disables the syslog-ng.service.


Do you know some way to fix this, by adding something, the syslog-ng
configuration?


Thanks in Advance,

Alex
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.balabit.hu/pipermail/syslog-ng/attachments/20200626/2b3ff976/attachment.html>