Hi Greg, I'm sorry, I was unsure what kind of logs to give, thanks for giving me some instructions. ❯ 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 ❯ 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/ ❯ 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.
On Tue, Jan 31, 2023 at 11:09:59AM +0100, debian@sioban.net wrote:Le 31/01/2023 à 11:08, Nicolas George a écrit :debian@sioban.net (12023-01-31):A dependency job for rsyslog.service failed. See 'journalctl -xe' for details.Have you considered seeing journalctl -xe for details?Hi, Yes, that was my first action. The last line of log is from Oct 24 :/I don't know how you expect anyone to help you if you don't provide any details. Try some or all of these commands: df /var/log /var/log/journal systemctl status rsyslog.service journalctl -u rsyslog.service | tail Also note that some of these commands give additional detail when run as root. Solving your problem may involve figuring out *which* "dependency job" failed, and why. So, once you identify what's actually failing, you may have to drill down into that one, the same way you started out drilling down into rsyslog.service.