edge-host: fix edge-alloy ExecStart (Arch binary is grafana-alloy) #116

2026-07-07T07:08:37Z

k.renner commented

2026-07-07 07:08:37 +00:00

Follow-up bugfix to #114. The edge-alloy.service unit pointed ExecStart at /usr/bin/alloy, but the Arch grafana-alloy package installs the binary as /usr/bin/grafana-alloy — the service crash-looped with status=203/EXEC.

Makes the path a variable (edge_alloy_bin, default /usr/bin/grafana-alloy) and uses it in the unit template.

Verified live on edge-1 before/after: the binary runs (v1.13.2), the alloy user exists (in systemd-journal), and the deployed /etc/alloy/edge.alloy config parses cleanly (grafana-alloy fmt) — so this one path was the only fault. Everything else from #114 (journald volatile, docker journald driver, noatime, trim + wear timers) is already correctly applied and confirmed on the host.

After merge I'll re-run install-edge-host.yml; only the alloy unit changes, so it just restarts edge-alloy (no container bounce) and log delivery to Loki goes live.

Follow-up bugfix to #114. The `edge-alloy.service` unit pointed `ExecStart` at `/usr/bin/alloy`, but the Arch `grafana-alloy` package installs the binary as **`/usr/bin/grafana-alloy`** — the service crash-looped with `status=203/EXEC`. Makes the path a variable (`edge_alloy_bin`, default `/usr/bin/grafana-alloy`) and uses it in the unit template. **Verified live on edge-1** before/after: the binary runs (v1.13.2), the `alloy` user exists (in `systemd-journal`), and the deployed `/etc/alloy/edge.alloy` config parses cleanly (`grafana-alloy fmt`) — so this one path was the only fault. Everything else from #114 (journald volatile, docker journald driver, noatime, trim + wear timers) is already correctly applied and confirmed on the host. After merge I'll re-run `install-edge-host.yml`; only the alloy unit changes, so it just restarts edge-alloy (no container bounce) and log delivery to Loki goes live.

k.renner added 1 commit 2026-07-07 07:08:37 +00:00

edge-host: fix edge-alloy ExecStart — Arch binary is grafana-alloy 842b60c5b2

PR #114 pointed the edge-alloy.service unit at /usr/bin/alloy, but the Arch
`grafana-alloy` package installs the binary as /usr/bin/grafana-alloy. The
unit crash-looped with status=203/EXEC ("Unable to locate executable
/usr/bin/alloy"). Make the path a variable (edge_alloy_bin) and default it to
the real path. Verified on edge-1: the binary runs (v1.13.2), the alloy user
exists (in systemd-journal), and the deployed config parses cleanly — only
the ExecStart path was wrong.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

k.renner merged commit eef50e8872 into master

2026-07-07 07:10:31 +00:00

k.renner referenced this issue from a commit

2026-07-07 07:10:32 +00:00

Merge pull request 'edge-host: fix edge-alloy ExecStart (Arch binary is grafana-alloy)' (#116) from fix/edge-alloy-binary-path into master

claude-bot referenced this pull request

2026-10-28 02:12:40 +00:00

docs(mosquitto): Shelly MQTT server now set via shelly-manager group settings #1508

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: konairius/homelab#116