Differences

This shows you the differences between two versions of the page.

--- packet:bpq_logging_reduction [2026/01/08 00:03] – g5rkt
+++ packet:bpq_logging_reduction [2026/03/26 06:54] (current) – g5rkt
@@ Line 43: / Line 43: @@
 }</code>
-====Newer versions of Raspberry Pi OS (i.e. Debian 12)====
+====Newer versions of Raspberry Pi OS (i.e. Debian 12+)====
 SystemD's journald is a complex beast which works very differently to classic *nix sysloggers. All logs are stored together in binary files and queried with ''journalctl'', instead of being stored as separate files in ''/var/log''. You'll find your journal files in ''/var/log/journal'', see how big they are by running
@@ Line 71: / Line 71: @@
 and optionally delete the old journal files
-<code>sudo rm -rf /var/log/journal</code>
+<code>sudo rm -rf /var/log/journal/*</code>
 There will still be some stuff ending up in /var/log - on a Debian system this will be logs from apt, dpkg etc, and other packages (ginx, mosquitto etc) by default are configured to write directly to it, but all syslogging will now be in RAM and sizes kept under control. As the syslog is in RAM rebooting the Pi / if the Pi crashes all the logs will be lost. If you want persistent log storage (for example on a Pi 5 with an NVMe SSD) then you can get some control by vacuuming / configuring journald - that's beyond the scope of "save your SD card" so there's some good reading [[https://linuxhandbook.com/clear-systemd-journal-logs/|here]]
@@ Line 82: / Line 82: @@
 ====Writing all linbpq packets to syslog====
+**This section has now essentially been deprecated by the fabulous work to send data to [[https://pacmon.m0ahn.compute.oarc.uk/|PacMon]] - use that instead!!**
 If you really want to you can save out all the packets your station has heard to syslog. With some parsing this could be a useful diagnostic tool; here's one way to do it using [[https://raymii.org/s/software/Fast_MQTT_Logger.html|an MQTT syslogger]]