I understand it is not desirable to have duplicate logging, but there is a corner case where logging that is done during systemd shutdown is lost because rsyslog is killed. This makes shutdown look broken due to it being non-deterministic exactly when rsyslog is killed.
Currently, the easiest way to get accurate logging is creating /var/log/journal. ## Sometimes shutdown logs are brief: Oct 13 18:51:07 HOST systemd[1]: Stopped target Cloud-init target. Oct 13 18:51:07 HOST systemd[1]: Starting Unattended Upgrades Shutdown... Oct 13 18:51:07 HOST systemd[1]: Stopping Session 1 of user ubuntu. Oct 13 18:51:07 HOST systemd[1]: Stopped target Graphical Interface. Oct 13 18:51:07 HOST systemd[1]: Stopping Accounts Service... Oct 13 18:51:07 HOST rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="759" x-info="http://www.rsyslog.com";] exiting on signal 15. ## Sometimes more detailed Oct 13 18:57:33 HOST systemd[1]: Stopping Session 1 of user ubuntu. Oct 13 18:57:33 HOST systemd[1]: Stopping User Manager for UID 1000... Oct 13 18:57:33 HOST systemd[1]: Stopped target Timers. Oct 13 18:57:33 HOST systemd[1]: Stopped Daily apt activities. Oct 13 18:57:33 HOST systemd[1277]: Reached target Shutdown. Oct 13 18:57:33 HOST systemd[1277]: Stopped target Default. Oct 13 18:57:33 HOST systemd[1277]: Stopped target Basic System. Oct 13 18:57:33 HOST systemd[1277]: Stopped target Timers. Oct 13 18:57:33 HOST systemd[1277]: Stopped target Sockets. Oct 13 18:57:33 HOST systemd[1277]: Starting Exit the Session... Oct 13 18:57:33 HOST systemd[1]: Stopped Daily Cleanup of Temporary Directories. Oct 13 18:57:33 HOST systemd[1277]: Stopped target Paths. Oct 13 18:57:33 HOST systemd[1]: Stopped target Graphical Interface. Oct 13 18:57:33 HOST systemd[1]: Stopped Timer to automatically refresh installed snaps. Oct 13 18:57:33 HOST systemd[1]: Stopping ACPI event daemon... Oct 13 18:57:33 HOST systemd[1]: Starting Unattended Upgrades Shutdown... Oct 13 18:57:33 HOST systemd[1]: Stopping Accounts Service... Oct 13 18:57:33 HOST systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch. Oct 13 18:57:33 HOST systemd[1]: Stopping Virtual machine log manager... Oct 13 18:57:33 HOST systemd[1]: Stopped target Cloud-init target. Oct 13 18:57:33 HOST systemd[1277]: Received SIGRTMIN+24 from PID 1592 (kill). Oct 13 18:57:33 HOST systemd[1]: Stopped Execute cloud user/final scripts. Oct 13 18:57:33 HOST systemd[1]: Stopped Apply the settings specified in cloud-config. Oct 13 18:57:33 HOST systemd[1]: Stopped target Cloud-config availability. Oct 13 18:57:33 HOST rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="737" x-info="http://www.rsyslog.com";] exiting on signal 15. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618188 Title: systemd journal should be persistent by default: /var/log/journal should be created; remove rsyslog from default installs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
