audit(2026-10-19): degenerate-stream incident page + push-notifications page; refresh scheduled-tasks, current-state, index, log, messaging, mnemosyne, tailscale, proxmox
This commit is contained in:
@@ -3,8 +3,8 @@ title: Messaging Integrations
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-11
|
||||
verified_on: 2026-10-11
|
||||
updated: 2026-10-19
|
||||
verified_on: 2026-10-19
|
||||
confidence: high
|
||||
tags: [messaging, telegram, discord, email, integrations]
|
||||
sources: [raw/configs/hermes-config-sanitized.txt, live-jobs-json, live-himalaya-debug]
|
||||
@@ -93,3 +93,23 @@ not merely an application-level refusal.
|
||||
|
||||
**Open item:** re-probe the host; if the host is back but the adapter stays down, restart the
|
||||
gateway's Mattermost platform.
|
||||
|
||||
## 2026-10-19 00:15 AWST — Mattermost adapter: cause identified (CT255 stopped), still down
|
||||
|
||||
This pass replaced the 10-11 observation's "cause not determined" with a definite cause. Live probes,
|
||||
2026-10-19 00:0x-00:15 AWST:
|
||||
|
||||
- `tailscale status`: peer `mattermost` (`100.98.116.14`) — **offline, last seen 29d ago**, `tx 7176 rx 0`.
|
||||
- `gateway.log`: the reconnect loop is unchanged — `Reconnecting mattermost (attempt 470)` at 00:08:36
|
||||
and `(attempt 471)` at 00:14:07, each followed by `Mattermost: disconnected` and
|
||||
`Reconnect mattermost error: mattermost connect timed out after 30s, next retry in 300s`
|
||||
(5-minute cadence; 3,992 such lines in the retained `gateway.log`).
|
||||
- Probed from CT460 at the configured endpoint (`MATTERMOST_URL=http://100.98.116.14:8065/`):
|
||||
**TCP 8065 refused/closed and 100 % ICMP loss** — the host is unreachable, not the application.
|
||||
- **Cause: CT255 (`mattermost`) is `stopped` on the PVE host** (see [[infrastructure/proxmox]]).
|
||||
The attempt counter restarted at the gateway restart of 2026-10-17 05:10 and now reads 471.
|
||||
- Impact unchanged: messaging path only. No cron job delivers via Mattermost, and the cron fleet
|
||||
performed normally throughout.
|
||||
|
||||
**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.
|
||||
|
||||
Reference in New Issue
Block a user