Yep of course. I’m gonna have to look that one up! No worries, I’ll find out!
Did you disable all logging? You can start by checking if the logging service is enabled:
systemctl status systemd-journald.service
Here is the output:
~ >>> journalctl -u fstrim
– No entries –
~ >>> systemctl status systemd-journald.service
● systemd-journald.service - Journal Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
Active: active (running) since Sat 2022-07-02 07:11:45 BST; 17h ago
TriggeredBy: ● systemd-journald-audit.socket
● systemd-journald.socket
● systemd-journald-dev-log.socket
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Main PID: 236 (systemd-journal)
Status: “Processing requests…”
Tasks: 1 (limit: 9366)
Memory: 18.5M
CPU: 875ms
CGroup: /system.slice/systemd-journald.service
└─236 /usr/lib/systemd/systemd-journald
Jul 02 07:11:45 kyoto21 systemd-journald[236]: Journal started
Jul 02 07:11:45 kyoto21 systemd-journald[236]: Runtime Journal (/run/log/journal/f5d0c8a1eb014a8db12eb6738aa7721e) is 8.0M, ma>
Jul 02 07:11:45 kyoto21 systemd-journald[236]: Runtime Journal (/run/log/journal/f5d0c8a1eb014a8db12eb6738aa7721e) is 8.0M, ma>
Jul 02 07:11:45 kyoto21 systemd-journald[236]: Received client request to flush runtime journal.
Notice: journal has been rotated since unit was started, output may be incomplete.
You won’t show any entries for fstrim until after fstrim.timer has run on Monday if you either a) had disabled logging until now, or b) just enabled the fstrim.timer.
OK thanks. I know that fstrim has worked for the last 2 weeks, but there is no logging. I will have to re -enable the logs some how. I will check that one out.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.