counterweight
a0c23ae766
802-line playbook becomes 68 lines (three plays: the role, the Caddy dashboard, the Stratum socket proxy) plus a 345-line role. datum_gateway_vars.yml is deleted; its content is the role's defaults. Verified after a real run with zero miners connected: datum-gateway restarted cleanly onto the reformatted config, deployed config.json semantically identical to what was there (pool_address bc1qvrj3g84..., pool_pass_* false, ports unchanged), health check timer firing, and the Knots side untouched - bitcoind still up since 2026-08-19 with blocknotify intact. TWO PIECES OF DRIFT WHERE THE NODE WAS RIGHT, both confirmed with the operator: - datum_mining_address: the vault held bc1qdse9dsg... while the node had been mining to bc1qvrj3g... since 2026-08-08. This is WHERE BLOCK REWARDS ARE PAID. And unlike fulcrum and bitcoin-knots, the `Restart datum-gateway` handler here was never gated, so the stale value would have applied immediately rather than sitting inert on disk. - pool_pass_workers / pool_pass_full_users: false on the node, true in the vars file. Both corrected in the vault and role defaults with notes recording why. Comparing this config needs semantics, not text: the live file is single-line JSON and the template renders pretty-printed, so a textual diff is pure noise. Rendering it and comparing parsed JSON is what surfaced both differences. config.json carries bitcoind.rpcpassword and api.admin_password, and --diff prints rendered content - so `--check --diff` put them on the terminal. The task now sets diff: false by default (-e datum_reveal_config=true to opt in). Those two should be rotated. I also mis-reported pool_pass_workers/pool_pass_full_users as exposed credentials because my masking matched "pass" in the key name. They are BOOLEANS, and mining.pool_address is a Bitcoin address, public by nature. Only the two real passwords above were exposed. `Configure cmake build` and `Compile datum_gateway` are bare command: tasks with no changed_when, so they recompile on every run. The build is reproducible - Install datum_gateway binary sees identical content and leaves the installed binary's timestamp alone - but it is wasted work each time. Documented as the idempotent floor. Ownership parity checked mechanically against `git show HEAD:` keyed by task name: 7/7 match, 9 Kuma tasks dropped. This completes Plan 6 Stage 2: all six services in the list are roles. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
50 lines
1.8 KiB
YAML
50 lines
1.8 KiB
YAML
---
|
|
# Everything here answers "is DATUM Gateway 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, a push-URL file read back and
|
|
# parsed, and a systemd Environment= rewrite — are gone. Where it reports is now
|
|
# one variable, healthcheck_push_url.
|
|
- name: Create DATUM Gateway health check script
|
|
ansible.builtin.template:
|
|
src: healthcheck.sh.j2
|
|
dest: /usr/local/bin/datum-gateway-healthcheck-push.sh
|
|
owner: root
|
|
group: root
|
|
mode: '0755'
|
|
validate: "bash -n %s"
|
|
|
|
- name: Create datum-gateway health check systemd service
|
|
ansible.builtin.template:
|
|
src: healthcheck.service.j2
|
|
dest: /etc/systemd/system/datum-gateway-healthcheck.service
|
|
owner: root
|
|
group: root
|
|
mode: '0644'
|
|
notify: Restart datum-gateway health check timer
|
|
|
|
- name: Create datum-gateway health check systemd timer
|
|
ansible.builtin.template:
|
|
src: healthcheck.timer.j2
|
|
dest: /etc/systemd/system/datum-gateway-healthcheck.timer
|
|
owner: root
|
|
group: root
|
|
mode: '0644'
|
|
notify: Restart datum-gateway health check timer
|
|
|
|
- name: Reload systemd daemon after health check units
|
|
systemd:
|
|
daemon_reload: yes
|
|
|
|
# Ungated: enabling a timer is deployment, not monitoring.
|
|
- name: Enable and restart the datum-gateway health check timer
|
|
systemd:
|
|
name: datum-gateway-healthcheck.timer
|
|
enabled: yes
|
|
state: restarted
|
|
daemon_reload: yes
|
|
|
|
# Arms the timer and smoke-tests the check. See roles/bitcoin_knots/README.md for
|
|
# why restarting the timer alone is not enough with OnBootSec + OnUnitActiveSec.
|
|
- name: Run the DATUM Gateway health check once to arm the timer
|
|
command: systemctl start datum-gateway-healthcheck.service
|
|
changed_when: false
|