counterweight
bf3d21fef7
Nothing in the repo pushes to, authenticates against, or is gated by Uptime
Kuma any more.
── The sixth instance of the banner bug ────────────────────────────────────
memos had `Restart memos` guarded by `uptime_kuma_enabled`, because the
deprecation banner was placed immediately above it and swept it in. It is a
HANDLER, so every memos config change since 2026-09-11 applied to disk and
silently never restarted the service. Ungated.
That is the same failure found in forgejo-runner's self-assert, phoenixd's timer
enable, mempool's three timer enables, fulcrum's restart handler and bitcoind's
restart handler. Every guard was read and asked "monitoring or deployment?"
before being deleted, which is the only reason this was caught.
── What was removed ────────────────────────────────────────────────────────
30 uptime_kuma_enabled guards across 7 unconverted service playbooks, and
the 29 Kuma monitor-creation tasks they gated (embedded Python that drove
the Kuma API, temp credential files, cleanup)
7 dead uptime_kuma_api_url definitions
7 stale DEPRECATED banners
uptime_kuma_enabled and subdomains.uptime_kuma from group_vars/all
healthcheck_push_urls from the vault - 30 push tokens
services/ntfy/setup_ntfy_uptime_kuma_notification.yml -> archive/
The explanatory comments in the six converted roles are KEPT on purpose. They
record why a handler is ungated, and deleting the explanation invites someone
to helpfully re-add the guard.
── The probes moved rather than died ───────────────────────────────────────
Eight per-service health checks were still pushing to Kuma. They are not
superseded by infra/401: that answers "is the unit running", these answer "does
the service actually respond" - an RPC call to bitcoind, a TCP connect to
Fulcrum's Electrum port, an HTTP fetch from Mempool's backend. A process can be
perfectly `active` and useless.
So they were repointed, not deleted. Gatus external endpoints take a POST with
a bearer token and success=true|false where Kuma took a GET with ?status=up, so
report() now maps up/down to true/false internally and no call site changed.
Registered by infra/403 as the `probe` group, one token per host.
Two bugs fixed while in there:
* forgejo-runner's check only ever reported SUCCESS - it exited before pushing
when the runner was down, so a failure was invisible until the heartbeat
window expired. Reporting the failure is the entire point of a check.
* All six healthcheck .service units were mode 0644 and now carry a bearer
token. They are 0600.
Verified: 91 endpoints, 91 UP, 0 DOWN. Every probe triggered by hand and
confirmed arriving. Zero Kuma URLs left in the vault, zero live references in
any playbook or role.
Still standing, deliberately: the Kuma container on watchtower, its Caddy vhost,
and the uptime.contrapeso.xyz DNS record. Turning the service off is a separate
decision from removing the code that talked to it.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| defaults | ||
| handlers | ||
| tasks | ||
| templates | ||
| README.md | ||
phoenixd
Deploys and runs phoenixd, an ACINQ Lightning node, on the edge host. LNBits uses it as a wallet backend. The HTTP API stays on loopback — phoenixd is never published through Caddy.
Converted from deploy_phoenixd_playbook.yml (552 lines) under Plan 6. The
playbook is now 18 lines.
Phases
install.yml |
packages, system user, directories, versioned download and install |
service.yml |
systemd unit, start, then first-boot checks (config written, seed created) |
healthcheck.yml |
check script, unit, timer |
The seed
{{ phoenixd_data_dir }}/seed.dat is the funds. phoenixd is deliberately
excluded from the automated backups (Plan 5, Model C): the seed is twelve fixed
words that never change, so an automated job would only manufacture more copies
of a static secret on more machines. Write them down offline, once.
Note the live file is mode 0644. That is phoenixd's own doing, not this role's,
and it is worth tightening.
Monitoring: one variable, no product knowledge
The check asks the node itself — the service must be active and
phoenix-cli getinfo must return a nodeId — and records the answer in its exit
code, which systemd keeps:
systemctl is-failed phoenixd-healthcheck.service
That is a complete answer with no monitoring system involved. To report
elsewhere, set healthcheck_push_url to anything accepting an HTTP ping. Gone
from this role: the embedded Python that created monitors over the Uptime Kuma
API, the /tmp credentials file, the push-URL file written and parsed back, and
the systemd Environment= rewrite.
Two things the conversion fixed
The check used to log an error once a minute. Its Environment= push URL had
been empty since the decommissioning, and the script printed
ERROR: UPTIME_KUMA_PUSH_URL not set on every fire — roughly 1,400 times a day.
The exit code was still correct, so nothing was broken; it was pure noise, and
noise that trains you to ignore the log. An unset push URL is now normal and
silent.
Enable and start phoenixd health check timer was guarded by
uptime_kuma_enabled and so had not run since the decommissioning — while the
timer itself was still live on the host from before. Ansible had quietly stopped
managing something that was still running. Ungated.