Am 22.03.2017 um 01:52 schrieb Nathan Dorfman: > On Wed, Mar 22, 2017 at 12:50:01AM +0100, Michael Biebl wrote: >> Please attach a complete journal log from the boot (journalctl -alb as root) > > Done, but might not be helpful. I've (cleanly) rebooted since then, > and now it's two *different* units that are failed. It looks like I've > somehow ended up with two competing services: > > root@stretch:/home/test# systemctl list-units *syslog* > UNIT LOAD ACTIVE SUB DESCRIPTION > > rsyslog.service loaded active running System Logging Service > > ● syslog.service loaded failed failed System Logging Service > > ● syslog.socket loaded failed failed Syslog Socket > > /lib/systemd/system/rsyslog.service is owned by rsyslog. However, I > also found some other files/symlinks, none of which belong to any > packages according to dpkg -S: > > lrwxrwxrwx 1 root root 35 Mar 21 19:54 > /etc/systemd/system/multi-user.target.wants/rsyslog.service -> > /lib/systemd/system/rsyslog.service > -rw-r--r-- 1 root root 290 Mar 21 16:02 /etc/systemd/system/syslog.service
That should be a symlink, not a real file. lrwxrwxrwx 1 root root 35 Jul 26 2016 /etc/systemd/system/syslog.service -> /lib/systemd/system/rsyslog.service that's also how it's setup by the rsyslog package (no idea how you ended up with syslog.service being a real file). So, most likely, due to syslog.service being a copy instead of a symlink, two instances are rsyslog are started, and one of them fails. Please fix that, reboot, and if the problem persists, attach a journal log from the boot. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
