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>
62 lines
2.4 KiB
YAML
62 lines
2.4 KiB
YAML
---
|
|
# Everything here answers "is Fulcrum healthy" and records the answer. The
|
|
# Uptime Kuma specifics that used to follow — an embedded Python script creating
|
|
# monitors over the API, a /tmp credentials file, push-URL extraction and a
|
|
# systemd Environment= rewrite — are gone. Where it reports is now one variable,
|
|
# healthcheck_push_url. See the role README.
|
|
- name: Create Fulcrum health check script
|
|
ansible.builtin.template:
|
|
src: healthcheck.sh.j2
|
|
dest: /usr/local/bin/fulcrum-healthcheck-push.sh
|
|
owner: root
|
|
group: root
|
|
mode: '0755'
|
|
validate: "bash -n %s"
|
|
|
|
- name: Create systemd service for Fulcrum health check
|
|
ansible.builtin.template:
|
|
src: healthcheck.service.j2
|
|
dest: /etc/systemd/system/fulcrum-healthcheck.service
|
|
owner: root
|
|
group: root
|
|
mode: "0600"
|
|
|
|
- name: Create systemd timer for Fulcrum health check
|
|
ansible.builtin.template:
|
|
src: healthcheck.timer.j2
|
|
dest: /etc/systemd/system/fulcrum-healthcheck.timer
|
|
owner: root
|
|
group: root
|
|
mode: '0644'
|
|
|
|
- name: Reload systemd daemon for health check
|
|
systemd:
|
|
daemon_reload: yes
|
|
|
|
# state: restarted, not started. The hand-written timer had got itself stuck
|
|
# `active` with no next elapse and had not fired since 2026-02-17; `started` on
|
|
# an already-active timer is a no-op and would have left it stuck. Restarting
|
|
# re-arms it. See the note in healthcheck.timer.j2.
|
|
- name: Enable and restart the Fulcrum health check timer
|
|
systemd:
|
|
name: fulcrum-healthcheck.timer
|
|
enabled: yes
|
|
state: restarted
|
|
daemon_reload: yes
|
|
|
|
# Run the check once, which is both a smoke test and the thing that actually
|
|
# arms the timer.
|
|
#
|
|
# This timer is OnBootSec + OnUnitActiveSec with no OnCalendar. OnBootSec is
|
|
# monotonic and had long since elapsed; OnUnitActiveSec schedules relative to the
|
|
# SERVICE last being active, and the service had not run since 2026-02-17 — so
|
|
# there was no reference to schedule from and the timer sat `active` and
|
|
# `enabled` with NextElapseUSecMonotonic=infinity. Restarting the timer alone
|
|
# does not supply that reference; running the service does.
|
|
#
|
|
# (Diagnosing this is easy to get wrong: NextElapseUSecRealtime is always empty
|
|
# for a monotonic timer, so it looks broken even when it is fine. Read
|
|
# NextElapseUSecMonotonic, or just use `systemctl list-timers`.)
|
|
- name: Run the Fulcrum health check once to arm the timer
|
|
command: systemctl start fulcrum-healthcheck.service
|
|
changed_when: false
|