vinzenz/hyperhive
vinzenz/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

swarm-bao: let the journald receiver read the host-linked journal

Browse source 
The container's collector has never shipped a line. `journalctl --follow`
— which the journald receiver passes unconditionally — scopes itself to
the current boot unless `--merge` is given too, and `--link-journal=host`
makes /var/log/journal the HOST's journal tree, where this container's
current boot has no entry. journalctl exited 1 with "No journal boot
entry found for the specified boot (+0)" and the receiver respawned it
every ~2s, so nothing was ever read and nothing was ever exported.

`merge = true` is the receiver's key for `--merge` (buildArgs() in
pkg/stanza/operator/input/journald/config_linux.go at tag
receiver/journaldreceiver/v0.151.0, the deployed collector's version),
and --merge is what clears the implicit boot scope in journalctl.c
(systemd v260.4, the version on the host).

The module-eval arm pins both halves: the boot filter is gone AND the
directory is still the host-linked one — either alone is satisfiable by
the broken config.
This commit is contained in:
atlas 2026-09-23 23:19:31 +02:00
commit c0c031a5e4
2 changed files with 25 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
nix/host-modules/swarm-bao.nix
View file

@ -2530,6 +2530,12 @@ in
# this machine id. Dropping this line leaves a collector that
# validates, starts, reports healthy and forwards nothing.
directory = "/var/log/journal";
# ⚠️ `--merge`, and it is what makes this receiver read
# anything at all: `journalctl --follow` scopes itself to the
# current boot, which has no entry under the host's journal
# tree — so every start died with "No journal boot entry found
# for the specified boot (+0)" in a ~2s crash-loop.
merge = true;
storage = "file_storage";
};

19
nix/module-eval/bao-otel-collector.nix
View file

@ -246,6 +246,25 @@ let
&& p.exporters == [ "otlphttp" ]
&& s ? exporters.otlphttp;
}
{
# 🩸 The receiver read NOTHING before this, on every deploy there has
# ever been: `journalctl --follow` (the receiver passes `--follow`
# unconditionally) scopes itself to the current boot unless `--merge` is
# also given, and under `--link-journal=host` the directory below is the
# HOST's journal tree, where this container's current boot has no entry.
# journalctl exited 1 with "No journal boot entry found for the specified
# boot (+0)" and the receiver restarted it every ~2s forever.
#
# Both halves, because each alone is satisfiable by the broken config:
# `merge` is only a fix while the directory stays the host-linked one,
# and the directory is only readable while `merge` clears the boot scope.
name = "the store's forwarder reads the host-linked journal without a boot filter";
ok =
let
j = (baoForwarder baoWithCollector).settings.receivers.journald;
in
(j.merge or false) == true && j.directory == "/var/log/journal";
}
{
# The whole journal, which is what the shared collector's unit allowlist
# is not. A `units` list here would render and deploy perfectly while