Skip to content

Monitor Eddie: nightly power window, Kuma ping, ntfy down/up alerts - #78

Merged
mathewcsims merged 2 commits into
mainfrom
kuma-eddie-nas-ping-monitor
Aug 9, 2026
Merged

Monitor Eddie: nightly power window, Kuma ping, ntfy down/up alerts#78
mathewcsims merged 2 commits into
mainfrom
kuma-eddie-nas-ping-monitor

Conversation

@mathewcsims

Copy link
Copy Markdown
Owner

What

Response to the 2026-08-08→09 overnight NAS outage (Eddie's NIC locked up; only a physical power-cycle recovered it — the EX2 Ultra's known failure mode).

Live changes (already applied and verified via the SETUP.md Socket.IO playbook):

  • Uptime Kuma ping monitor Eddie (host) (id 40) → 10.0.1.12, cloned from the Slartibartfast host monitor (60s interval, 3 retries), tagged Homelab + new machine tag Eddie (sky #0284C7), added to the status page's Monitoring & infrastructure group in alphabetical position.
  • New Kuma notification ntfy (id 2, native provider, topic alerts, publisher access-token auth), attached to the monitor alongside Discord — alerts on both DOWN and UP. Priorities 3 (up) / 4 (down), deliberately never 5/max since the nightly power window fires a DOWN/UP pair daily.

This PR: documents all of the above in SETUP.md, plus Eddie's new nightly 04:00–06:00 Power Schedule window (chosen to sit after the 02:00 Mac backup run and end as the 06:00 verify starts; no backup job has touched Eddie since 2026-08-04).

Verification

  • First heartbeat UP at 0.36ms; monitor visible in the public status-page group.
  • Test push arrived on the alerts ntfy topic (testNotification event, "Sent Successfully").
  • Read-only DB check on the Pi: monitor 40 has notifications 1+2 attached; no new untagged monitors (the three pre-existing untagged ones — Docs, Fizzy, Super Productivity — are flagged as a separate task, not touched here).
  • Tonight's 04:00 window will exercise the full DOWN→UP alert path for real.

Note: the 04:00–06:00 Power Schedule itself is set on the NAS dashboard by hand — merge this once that's done so the doc matches reality.

🤖 Generated with Claude Code

mathewcsims and others added 2 commits August 9, 2026 08:46
334 findings flagged; nine candidate bumps existed; scanning old vs new
kept exactly one. Uptime Kuma 2.4.0 -> 2.5.0 fixes three CVEs and
introduces none -- notably last week's 2.5.0 build was CVE-identical and
rejected, while this week's rebuild of the same version carries the fixes,
so version and digest genuinely move independently. Everything else with a
newer artifact was count-identical, including litellm v1.95.0 and tailscale
v1.102.2; mysql:latest scans 3 lower but is a major jump to 26.7, not an
option for Ghost's LTS database.

The 38 unfixed CRITICALs sit in the four new apps, all LAN/tailnet-gated.
Fizzy's are genuinely reachable -- libraw/OpenEXR/ImageMagick decode
attacker-supplied card images -- and it had zero hardening; now capped with
a bare cap_drop ALL (verified safe: runs as uid 1000 from PID 1, no
root-then-drop) and limits sized from measured steady state. Super
Productivity hardened as defence in depth with the root-then-drop cap set
since its nginx binds :80. Paperless and HedgeDoc were already hardened.

All three deploys verified: Kuma with heartbeats flowing, Fizzy with
secrets confirmed non-blank inside the container, SP serving.

Also records the pass-cli session-wedge symptom and fix hit during deploy.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The NAS's NIC locked up overnight (2026-08-08→09) and only a physical
power-cycle brought it back — the EX2 Ultra's known drop-off-the-network
failure mode. Three responses, the live halves already applied:

- Eddie now powers off nightly 04:00–06:00 via its dashboard Power
  Schedule (2-hour block granularity), sitting after the 02:00 Mac
  backup run and ending as the 06:00 verify starts. No backup job has
  touched Eddie since 2026-08-04, so the window only affects Paperless's
  idle CIFS mount.
- New Uptime Kuma ping monitor "Eddie (host)" (id 40) on 10.0.1.12,
  cloned from the Slartibartfast host monitor per the Socket.IO
  playbook, tagged Homelab + new machine tag Eddie (sky #0284C7), added
  to the status page's Monitoring & infrastructure group.
- New Kuma notification "ntfy" (id 2, native provider, topic alerts,
  publisher access token) attached to the monitor alongside Discord.
  Priorities 3 up / 4 down — deliberately never max, since the nightly
  power window fires a DOWN/UP pair at 04:00/06:00 every day.

Verified live: first heartbeat UP at 0.36ms, test push arrived on the
alerts topic, monitor present in the public status page group, DB check
confirms both notifications attached and no new untagged monitors.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@mathewcsims
mathewcsims merged commit a7d51ed into main Aug 9, 2026
7 checks passed
mathewcsims added a commit that referenced this pull request Aug 9, 2026
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant