wiki: nightly audit 2026-11-05 window — network-map re-verified by live probe (9377=Camofox not Stratos, 8790/5174 gone, +9120/9222/7777/6767/8085/9900, full Tailscale Serve table, two dead routes 8769/9123); commit pending 11-04 stocktake re-verifications; log + skills-index

This commit is contained in:
hermes
2026-11-05 01:22:45 +08:00
parent e4086ec18e
commit 3b5daccb4d
15 changed files with 942 additions and 552 deletions
+24 -3
View File
@@ -3,8 +3,8 @@ title: Backups
type: infrastructure
status: active
created: 2026-07-22
updated: 2026-10-22
verified_on: 2026-10-22
updated: 2026-11-04
verified_on: 2026-11-04
confidence: medium
tags: [infrastructure, backups]
sources: [raw/configs/hermes-config-sanitized.txt]
@@ -59,7 +59,7 @@ How Hermes's own configuration/state gets backed up, and what's missing.
`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
**76 commits ahead of `origin/main`**. Root cause is a credential: `origin` is
**89 commits ahead of `origin/main`** (was 76 on 2026-10-22 — **13 more nights of local-only commits** since). 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` →
@@ -71,6 +71,27 @@ since 2026-08-07.** The 2026-07-22 full zip and the wiki/authoring repos remain
Telegram failure notices *have* been firing daily (last: 2026-10-21 11:00:14, `message_id 8449`); the AgentMail
notification step failed.
**Re-verified 2026-11-04 — still dead, and the drift is now 89 commits.** Live `git -C ~/.hermes/config-backup`:
`origin` = `https://gitea.kangaroo-eel.ts.net/Anthony/hermes-config-backup.git` (**unchanged** — still HTTPS with
no userinfo and no credential helper, so the credential root cause has not been addressed); `rev-list --count
origin/main..HEAD` = **89**; `log origin/main -1` = **2026-08-07 11:00:47 +0800 1e1eb208** (`🦝 nightly backup:
2026-08-07 11:00:29 AWST`) — i.e. **nothing has reached Gitea in 89 days**. `backup.log` confirms the nightly
failure is current, not historical: the last two runs read
`[2026-11-02 11:00:32 AWST] ✗ Push to Gitea FAILED` / `--- Backup complete: FAIL ---` and
`[2026-11-03 11:00:31 AWST] ✗ Push to Gitea FAILED` / `--- Backup complete: FAIL ---`.
**A second, separate push failure is now also present:** the script attempts a `github` remote that **does not
exist** — `fatal: 'github' does not appear to be a git repository` → `✗ Push to GitHub FAILED`. So both off-box
targets are broken; the GitHub leg is a missing-remote error rather than a credential error, and would need
`git remote add github …` with credentials before it can work at all.
**The cron row still lies:** `e27da6c34bbb` reads `enabled: true, last_status: ok` in `jobs.json` while every
nightly execution has failed the push — the classic green-row/dead-artifact pattern.
**Full-backup gap unchanged:** the one full `hermes backup` zip on disk is still
`/home/hermes/hermes-backup-2026-07-22-180830.zip` (246 MB, 22 Jul) — **now 105 days old**. No new full zip has
been taken. `crontab -l -u hermes` is still empty and there are still **0 user systemd timers**, so nothing
schedules the full zip; only `e5ed215fc91c` (**Mnemosyne DB Backup**, weekly `0 3 * * 0`) and `e27da6c34bbb`
(config backup, daily) exist in the cron fleet, and neither takes a full `hermes backup`.
## Relevant runbooks
- [[runbooks/backup-wiki]]
- [[runbooks/update-hermes-safely]]