Move the ops box's Uptime Kuma to 2.5.5, rehearsed on a copy of its data #135

Merged

cruelacid merged 3 commits from worktree-kuma-2 into main 2026-09-23 21:31:19 +01:00

Conversation 0 Commits 3 Files changed 3 +85 -22

cruelacid commented 2026-09-23 20:21:09 +01:00

Owner

Copy link

Task: NEC-88

Pins the ops box's Uptime Kuma to 2.5.5 by digest, replacing :1. This PR only changes the pin and the runbook. The box itself is upgraded afterwards, by the procedure in deploy/UPGRADES.md (snapshot, banner, named-service pull).

Rehearsed off the box on an online .backup of the live kuma.db:

• Migration took 47 s locally, 45 s of it the aggregate-table step.
• All 17 monitors, both push tokens, both maintenances and their links, 34 notification links, and the status page with status.nectenda.com came across unchanged. The only difference is a new, empty column on monitor_group.
• 2.x keeps only "important" raw heartbeats after aggregating: 161,625 rows became 15,307. The uptime history is kept in the aggregates.
• kuma-compat.mjs passed 12/12 on the migrated copy and 12/12 on 1.23.17. The version branch differs visibly between them: conditions and incidents[] on 2.x, versus no conditions and a single incident on 1.x.
• One unexplained miss: the first login against the fresh 2.5.5 container got no acknowledgement within 8 s. A retry worked and it didn't recur.

Changelog

NONE

🤖 Generated with Claude Code

https://claude.ai/code/session_014jXw5B2oryJCk6KxdkjZJR

Task: NEC-88 Pins the ops box's Uptime Kuma to `2.5.5` by digest, replacing `:1`. This PR only changes the pin and the runbook. The box itself is upgraded afterwards, by the procedure in `deploy/UPGRADES.md` (snapshot, banner, named-service pull). **Rehearsed off the box** on an online `.backup` of the live `kuma.db`: - Migration took 47 s locally, 45 s of it the aggregate-table step. - All 17 monitors, both push tokens, both maintenances and their links, 34 notification links, and the status page with `status.nectenda.com` came across unchanged. The only difference is a new, empty column on `monitor_group`. - 2.x keeps only "important" raw heartbeats after aggregating: 161,625 rows became 15,307. The uptime history is kept in the aggregates. - `kuma-compat.mjs` passed 12/12 on the migrated copy and 12/12 on 1.23.17. The version branch differs visibly between them: `conditions` and `incidents[]` on 2.x, versus no `conditions` and a single `incident` on 1.x. - One unexplained miss: the first `login` against the fresh 2.5.5 container got no acknowledgement within 8 s. A retry worked and it didn't recur. ## Changelog NONE 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_014jXw5B2oryJCk6KxdkjZJR

cruelacid added the

area:ops

label 2026-09-23 20:21:09 +01:00

cruelacid added 1 commit 2026-09-23 20:21:09 +01:00

Move the ops box's Uptime Kuma to 2.5.5, rehearsed on a copy of its data ... 79aba91a35

The pin was `:1`, which can never express the move to 2.x. It is now
2.5.5 by digest. Before changing it, an online `.backup` of the live
kuma.db was opened by 2.5.5 off the box: the migration took 47 s, every
monitor, push token, maintenance link and the status page's custom
domain came across unchanged, and kuma-compat.mjs passed 12/12 on the
migrated copy and on 1.23.17, with the version branch visibly different.

UPGRADES.md records the result, including that 2.x deletes most raw
heartbeats after aggregating them, and fixes the rehearsal recipe: take
the copy with .backup rather than through snapshot.sh (which retires the
oldest snapshot), and switch notifications off in the copy so it cannot
send real DOWN alerts.

Task: NEC-88

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014jXw5B2oryJCk6KxdkjZJR

cruelacid added 1 commit 2026-09-23 20:31:04 +01:00

Record the repro-runaway hang recurring on a run that overlapped nothing ... 27ff09c658

Run 611 on this branch hung the same test the same way, with no other e2e
job running and nothing under packages/ changed. The server log is silent
for the five minutes, which says the vault stopped talking rather than
looped. Tracked as NEC-89.

Task: NEC-88

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014jXw5B2oryJCk6KxdkjZJR

cruelacid force-pushed worktree-kuma-2 from 27ff09c658 to 5dbbef9c8f 2026-09-23 20:36:49 +01:00 Compare

cruelacid added 1 commit 2026-09-23 21:26:02 +01:00

Record the repro-runaway hang's third occurrence, on run 615 ... 6bb4465311

Two hangs in three runs on this branch, none overlapping another suite.

Task: NEC-88

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014jXw5B2oryJCk6KxdkjZJR

cruelacid merged commit 6bb4465311 into main 2026-09-23 21:31:19 +01:00

cruelacid referenced this pull request 2026-09-24 07:10:53 +01:00

Read digest-pinned containers in the inventory, and log the Kuma upgrade #136

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

area:docs

docs/

  

area:identity

packages/identity

  

area:ops

deploy/, CI, hosting

  

area:plugin

packages/plugin

  

area:server

packages/server

  

channel:community

Obsidian forum, Obsidian Discord, Reddit

  

channel:direct

Cold outreach to named firms

  

channel:owned

nectenda.com pages, the feedback board

  

channel:press

Hacker News, newsletters, outlets, YouTube creators

  

channel:social

Bluesky, Mastodon, X, YouTube accounts

  

e2ee-constrained

End-to-end encryption changes the shape of the answer

  

gate:at-ga

Held until Gates A-C close and terms/privacy leave DRAFT

  

gate:pre-ga

Safe to do before the launch gates close

  

marketing

Reach and positioning; work published off nectenda.com

  

parity

Relay feature-parity programme

  

relay:absent

4 - Not supported, not requested, not planned at Relay

  

relay:planned

2 - On Relay's roadmap (Active/Planned) or has an open PR

  

relay:requested

3 - Asked for by Relay users or under 'Considering'; not committed

  

relay:supported

1 - Relay ships this today

  

risk:additive

New message type, table or column; backward compatible

  

risk:contract

Changes something existing accounts or stored data depend on

  

risk:none

Client-only; the server is untouched

  

usability

How the product is understood and learned, not what it does

No labels

area:docs

area:identity

area:ops

area:plugin

area:server

channel:community

channel:direct

channel:owned

channel:press

channel:social

e2ee-constrained

gate:at-ga

gate:pre-ga

marketing

parity

relay:absent

relay:planned

relay:requested

relay:supported

risk:additive

risk:contract

risk:none

usability

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

Nectenda/nectenda!135

No description provided.