http://bugzilla.suse.com/show_bug.cgi?id=1118068 http://bugzilla.suse.com/show_bug.cgi?id=1118068#c1 --- Comment #1 from Dr. Werner Fink --- Created attachment 791575 --> http://bugzilla.suse.com/attachment.cgi?id=791575&action=edit /etc/systemd/system/syslogd.service For SLES-15 and Tumbleweed this already fixed a long time @@ -18,23 +18,19 @@ Description=System Logging Service Conflicts=syslog-ng.service rsyslog.service Requires=var-run.mount -Requires=syslog.target +Requires=syslog.socket Requires=network.target Requires=klogd.service -Before=syslog.target Before=klogd.service -After=var-run.mount -After=network.target you might test out the attached service unit file, which *after* current syslog service has been stopped with systemctl, should be used as /etc/systemd/system/syslogd.service by daemon-reload, activation, and start. Does this work for you? -- You are receiving this mail because: You are on the CC list for the bug.