http://bugzilla.opensuse.org/show_bug.cgi?id=921252 --- Comment #4 from Per Jessen --- I have checked that /run/syslog-ng/additional-log-sockets.conf is present when syslog-ng is started, it is. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=921252 --- Comment #6 from Per Jessen --- As a work-around, I have added a drop-in: /etc/systemd/system/syslog-ng.service.d/extra.conf : [Service] ExecStart= ExecStart=/usr/local/bin/start-syslog-ng -F $SYSLOG_NG_PARAMS /usr/local/bin/start-syslog-ng does this: #!/bin/bash host service2.example.com >>/tmp/syslog-ng.log exec /usr/sbin/syslog-ng $@ It seems that my "host service2.example.com" primes the nscd cache, such that it works when syslog-ng is next started. I don't know why. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=921252 --- Comment #8 from Per Jessen --- What I don't understand is - my "host service2.spamchek.com" should really fail if it is a network or DNS problem. Instead it works and makes syslog-ng work too. I have three nameservers defined in /etc/resolv.conf nameserver 192.168.4.207 nameserver 192.168.4.200 nameserver 192.168.4.209 search example.com During boot-up, only 192.168.4.200 is reachable, 192.168.4.207 comes on later, 192.168.4.209 is dead. I think I'll put a packet trace on the network and see which nameservers are tried at startup. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=921252 --- Comment #12 from peter czanik --- FYI: It is to be fixed with syslog-ng 3.6.3 upstream (due in the coming weeks), and it is planned to be backported to 3.5 too. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=921252 http://bugzilla.opensuse.org/show_bug.cgi?id=921252#c14 --- Comment #14 from peter czanik --- syslog-ng 3.6.3 and 3.6.4 were released with many bugfixes including one for this: When the configured host was not available during the initialization of afsocket destination syslog-ng just didn't start. From now, syslog-ng starts in that case and will retry connecting to the host periodically. A package for testing is available at https://build.opensuse.org/project/show/home:czanik:syslog-ng36 (I built it, but did not have time for extensive testing, as I'm travelling abroad...) -- You are receiving this mail because: You are on the CC list for the bug.