On Tue, Jan 31, 2023 at 03:52:32PM +0100, deb...@sioban.net wrote: > ❯ df /var/log /var/log/journal > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/md24 46096212 1620728 42101496 4% /var/log > /dev/md24 46096212 1620728 42101496 4% /var/log
OK, not out of disk space. That's good. Also, interesting that you have /var/log as a separate file system. That's uncommon (but nothing wrong with it). > ❯ systemctl status rsyslog.service > ● rsyslog.service - System Logging Service > Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor > preset: enabled) > Active: inactive (dead) > TriggeredBy: ● syslog.socket > Docs: man:rsyslogd(8) > man:rsyslog.conf(5) > https://www.rsyslog.com/doc/ Frustratingly devoid of details. It says "enabled" though, which is normal. > ❯ journalctl -u rsyslog.service | tail > -- Journal begins at Sun 2022-10-23 19:55:11 CEST, ends at Mon 2022-10-24 > 14:14:33 CEST. -- > Oct 24 14:14:02 shax systemd[1]: Stopping System Logging Service... > Oct 24 14:14:02 shax systemd[1]: rsyslog.service: Succeeded. > Oct 24 14:14:02 shax systemd[1]: Stopped System Logging Service. > Oct 24 14:14:02 shax systemd[1]: rsyslog.service: Consumed 47.066s CPU time. > > -- > > Unfortunately the 24 oct is too far for me to remember exactly what happened > there. > There is nothing in journalct -xe which might explain. How about: systemctl cat rsyslog.service Maybe you've customized or changed something that will be visible. Another approach you can take is to Google your error message, and see if any of the results are helpful. The idea that the unit file may have been customized came from one of the Google results that I got.
