🦉 wiki audit 2026-10-21: gateway unclean-exit orphaned run (new), Gitea config-backup push dead since 2026-08-08 (new), model default → nous, 503 back to monitoring, canned-substitute trigger corrected
This commit is contained in:
@@ -50,6 +50,23 @@ How Hermes's own configuration/state gets backed up, and what's missing.
|
||||
> 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.
|
||||
|
||||
## ⚠ 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
|
||||
`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` →
|
||||
`--- Backup complete: FAIL ---`. Full evidence and the proposed fix:
|
||||
[[incidents/2026-08-08-gitea-config-backup-push-dead]].
|
||||
|
||||
**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
|
||||
notification step failed.
|
||||
|
||||
## Relevant runbooks
|
||||
- [[runbooks/backup-wiki]]
|
||||
- [[runbooks/update-hermes-safely]]
|
||||
|
||||
Reference in New Issue
Block a user