summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobert Navarro <crshman@gmail.com>2026-09-17 13:59:55 -0700
committerRobert Navarro <crshman@gmail.com>2026-09-17 13:59:55 -0700
commit011b53cbfe8a273a931069ea592ace7a5aa18dbc (patch)
tree57c73c7d05390d9aff7badf68b042d462a060960
parent03500232bca1e1e2eda017428171faf9b4a3dc27 (diff)
downloadvyos-1x-011b53cbfe8a273a931069ea592ace7a5aa18dbc.tar.gz
vyos-1x-011b53cbfe8a273a931069ea592ace7a5aa18dbc.zip
journald: T9183: stop forwarding journal entries to syslog
rsyslog reads the journal directly through imjournal (rsyslog.conf.j2 loads it alongside imuxsock), so journald forwarding the same entries to /dev/log delivers every non-kernel message twice. Both copies land in /var/log files and go to every remote syslog target, differing only in PID formatting. Ship the setting as a journald drop-in here rather than as a full journald.conf in vyos-build, so the image carries only the settings VyOS actually overrides. MaxLevelSyslog=debug comes across from that file; the rest of it was commented-out systemd defaults. Tested on a live 2026.09.11 router: with the drop-in in place a single logger event produces one entry, remote targets receive one copy, and kernel messages (imklog) and HAProxy's own socket are unaffected.
-rw-r--r--src/etc/systemd/journald.conf.d/10-override.conf7
1 files changed, 7 insertions, 0 deletions
diff --git a/src/etc/systemd/journald.conf.d/10-override.conf b/src/etc/systemd/journald.conf.d/10-override.conf
new file mode 100644
index 000000000..95e150e9c
--- /dev/null
+++ b/src/etc/systemd/journald.conf.d/10-override.conf
@@ -0,0 +1,7 @@
+[Journal]
+# rsyslog reads the journal directly through imjournal, so forwarding the same
+# entries to /dev/log delivers every non-kernel message twice: once via
+# imuxsock and once via imjournal. Local files under /var/log and every remote
+# syslog target get both copies (T9183).
+ForwardToSyslog=no
+MaxLevelSyslog=debug