/var/log/messages. This is very impractical for troubleshooting. The command
systemd-journalctl --no-tailshows that
rsyslog.servicefails to start correctly. Bummer!
Starting the daemon by hand, does not give any issues, so at least rsyslogd does not have an issue itself.
Checking the configuration, there are two unit files that may be used to start
/usr/lib/systemd/system/rsyslog.service) that comes with the rsyslogd package:
[Unit]All looks pretty neat, there is no very obvious issue here. However, on checking what this
Description=System Logging Service
ExecStartPre=/bin/systemctl stop systemd-kmsg-syslogd.service
ExecStart=/sbin/rsyslogd -n $SYSLOGD_OPTIONS
systemd-kmsg-syslogd.serviceis and does, I seem to be unable to find the unit file that defines this service. Just guessing, but if the
ExecStartPrefails, it may not even try to start the rsyslog-daemon. Just commenting out the
ExecStartPreis Not Done with the systemd configuration files. The advised way to change unit files which live under /usr/lib/systemd should be copied to the
# cd /etc/systemd/systemNow is is possible to change the unit file, without changing a file that may be replaced by a update of the rsyslog package. Commenting out the
# rm syslog.service
# ln -s /usr/lib/systemd/system/rsyslog.service syslog.service
# cd multi-user.target.wants
# rm rsyslog.service
# ln -s ../syslog.service rsyslog.service
ExecStartPrein the new copy of
syslog.serviceand rebooting, makes syslog work for me and
/var/log/messagescontains all the logs as expected.
More brokenness in my systemd configurationOne more annoying thing is that
systemctlis not very usable:
# systemctl status rsyslog.serviceAlthough D-Bus is running:
Failed to get D-Bus connection: No connection to service manager.
# ps v -C dbus-daemon
PID TTY STAT TIME MAJFL TRS DRS RSS %MEM COMMAND
1474 ? Ss 0:00 6 265 2770 1436 0.3 /bin/dbus-daemon --system --address=systemd: --nofork --systemd-activation
I'm not sure what causes that (SElinux is disabled), but it is currently no big issue for me.