audit(2026-10-26): runaway Gmail digest + dead Nous credential; model default reverted to OmniRoute; conduit 0.69.2 live; freshness floor still 2026-10-08
This commit is contained in:
@@ -3,8 +3,8 @@ title: Messaging Integrations
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-19
|
||||
verified_on: 2026-10-19
|
||||
updated: 2026-10-26
|
||||
verified_on: 2026-10-26
|
||||
confidence: high
|
||||
tags: [messaging, telegram, discord, email, integrations]
|
||||
sources: [raw/configs/hermes-config-sanitized.txt, live-jobs-json, live-himalaya-debug]
|
||||
@@ -113,3 +113,15 @@ This pass replaced the 10-11 observation's "cause not determined" with a definit
|
||||
|
||||
**Open item:** start CT255, or retire the platform block. The 5-minute reconnect loop continues until
|
||||
one of those happens — restarting the adapter while the host is stopped achieves nothing.
|
||||
|
||||
## 2026-10-26 00:1x AWST — Mattermost still down; attempt counter reset by the 10-25 restart
|
||||
|
||||
- **Cause unchanged: CT255 (`mattermost`) is `stopped`.** `tailscale status` shows the peer **offline, last seen
|
||||
36 d ago**, `tx 312 / rx 0` — `rx` has read 0 in every audit since 2026-10-11, i.e. no packet has come back.
|
||||
- **Reconnect loop still running:** **268** `mattermost connect timed out` lines on 2026-10-25 vs **264** on
|
||||
2026-10-24 (≈1 per 5 min, as designed); **2** so far on 2026-10-26.
|
||||
- **The attempt counter reset to 54** with the 19:27:13 gateway restart (`Reconnecting mattermost (attempt 54)`
|
||||
at 2026-10-26 00:07:06). The previous reset was the 2026-10-17 05:10 restart. ⚠ The counter measures **this
|
||||
process's** attempts, not the outage's length — do not quote it as downtime.
|
||||
- **Impact unchanged:** messaging path only; no cron job delivers via Mattermost.
|
||||
- **Not attempted:** `pct start 255` — starting a service on the PVE host is Anthony's call.
|
||||
|
||||
Reference in New Issue
Block a user