🦉 wiki audit 2026-10-22: omni-101 pre-dispatch filter skip (3rd failure mode, new page), Hermes 0.22.3 update with snapshot skipped, Gitea backup backlog 76

- new: incidents/2026-10-21-omniroute-pre-dispatch-filter-skip.md
- systems/hermes-agent.md: version -> 0.22.3 (5b147ab036), 22:47-22:57 update, snapshot stage skipped, advisories unactioned
- systems/scheduled-tasks.md: 2026-10-21 = 171 completed / 1 failed; non-clean stays 9 with 08eb86f02d37 out, dca8482e4f76 in
- systems/omniroute.md: one pin, three signatures in eight days
- incidents/2026-10-16-omniroute-503-resource-pressure.md: window update, stays monitoring
- incidents/2026-08-08-gitea-config-backup-push-dead.md: 2026-10-21 run, backlog 75 -> 76, message_id 8449
- infrastructure/backups.md: 76 commits; pre_update_backup:false now exercised
- current-state.md, index.md, log.md updated
This commit is contained in:
Tony0410
2026-10-22 00:16:39 +08:00
parent c1d3b59260
commit 3919ec8557
10 changed files with 225 additions and 26 deletions
+8 -4
View File
@@ -3,8 +3,8 @@ title: Backups
type: infrastructure
status: active
created: 2026-07-22
updated: 2026-10-20
verified_on: 2026-10-20
updated: 2026-10-22
verified_on: 2026-10-22
confidence: medium
tags: [infrastructure, backups]
sources: [raw/configs/hermes-config-sanitized.txt]
@@ -49,13 +49,17 @@ How Hermes's own configuration/state gets backed up, and what's missing.
> tarball step in [[runbooks/backup-wiki]] has never been executed (the runbook's `mkdir -p` would
> create it on first use).
- `pre_update_backup: false` means an in-place `hermes update` will not auto-snapshot first — the manual step in [[runbooks/update-hermes-safely]] step 1 is currently the only safety net.
**Exercised on 2026-10-21:** the 22:47 `hermes update` (0.22.2 → 0.22.3) recorded its `snapshot` stage as
`skipped` with reason `disabled by updates.pre_update_backup (mode: off)`, so that update shipped with **no
local snapshot and no off-box copy** — the Gitea mirror below has been dead since 2026-08-08.
→ [[systems/hermes-agent]]
## ⚠ Scheduled config backup — the Gitea mirror has been dead since 2026-08-08
`e27da6c34bbb` (**Hermes Config Backup to Gitea**, daily `0 11 * * *`, `hermes-config-backup.sh`) **commits
locally every night and fails to push every night — while its cron row still reads `last_status: ok` and its
execution row reads `completed`.** Last commit that reached Gitea: **2026-08-07 11:00:47**; the local repo is
**75 commits ahead of `origin/main`**. Root cause is a credential: `origin` is
**76 commits ahead of `origin/main`**. Root cause is a credential: `origin` is
`https://gitea.kangaroo-eel.ts.net/Anthony/hermes-config-backup.git` — HTTPS, no userinfo, no credential
helper — so the non-interactive push dies on
`fatal: could not read Username … No such device or address` → `✗ Push to Gitea FAILED` →
@@ -64,7 +68,7 @@ helper — so the non-interactive push dies on
**Consequence for this page: everything above describes a topology that has not carried `~/.hermes` off the box
since 2026-08-07.** The 2026-07-22 full zip and the wiki/authoring repos remain the only recent off-box copies.
Telegram failure notices *have* been firing daily (last: 2026-10-20 11:00, `message_id 8447`); the AgentMail
Telegram failure notices *have* been firing daily (last: 2026-10-21 11:00:14, `message_id 8449`); the AgentMail
notification step failed.
## Relevant runbooks