Differences

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

--- packet:bpq_logging_reduction [2025/04/12 20:32] – m0mzf
+++ packet:bpq_logging_reduction [2025/04/14 20:05] (current) – [Newer versions of Raspberry Pi OS (i.e. Debian 12)] m0mzf
@@ Line 55: / Line 55: @@
 So let's get some control of this monster; edit the following file:
-<code>nano /etc/systemd/journald.conf</code>
+<code>sudo nano /etc/systemd/journald.conf</code>
 and uncomment / edit the following lines underneath ''[Journal]'':
@@ Line 73: / Line 73: @@
 <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, 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]]
+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]]
 To see what linbpq has been saying run
@@ Line 83: / Line 83: @@
 ====Writing all linbpq packets to syslog====
-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|and MQTT syslogger]]
+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]]
-< To do; set up mosquitto, set up LinBPQ to output MQTT >
+To do this you'll need to have LinBPQ publishing it's packets to MQTT. To get that set up [[packet:bpqmonweb|follow this guide]] - might as well go the whole hog and set up the web monitor too.
 Install Paho, download, install and compile the software:
@@ Line 92: / Line 92: @@
 mkdir ~/src; cd ~/src
 git clone https://github.com/RaymiiOrg/remys_fast_mqtt_logger
-cd remys_fast_mqtt_logger
+cd remys_fast_mqtt_logger; mkdir build; cd build
-mkdir build
-cd build
 cmake -DCMAKE_BUILD_TYPE=Release  ..
 </code>
@@ Line 109: / Line 107: @@
 -b "mosquitto:1883" \
 -t "PACKETNODE/ax25/trace/bpqformat/#" \
--u "bpqusername" \
+-u "bpqmonweb" \
--p "bpqpassword" \
+-p "bpqmonweb" \
 > /dev/null 2>&1
 </code>
@@ Line 143: / Line 141: @@
 <code>journalctl -u packet-syslog.service -n 1 -f</code>
-Expect this to use up maybe a dozen MB/day, depending on how busy your node is.
+Expect this to use up maybe a few MB/day, depending on how busy your node is.