wiki: publish pending edits (2026-10-20)
This commit is contained in:
@@ -3,9 +3,9 @@ title: Hermes Gateway Resource Resilience
|
||||
type: runbook
|
||||
status: active
|
||||
created: 2026-07-25
|
||||
updated: 2026-07-25
|
||||
review_after: 2026-10-23
|
||||
verified_on: 2026-07-25
|
||||
updated: 2026-10-20
|
||||
review_after: 2026-11-19
|
||||
verified_on: 2026-10-20
|
||||
version_applies_to: Proxmox CT460
|
||||
confidence: high
|
||||
tags: [hermes, infrastructure, runbook]
|
||||
@@ -50,12 +50,22 @@ File:
|
||||
|
||||
```ini
|
||||
[Service]
|
||||
MemoryHigh=1G
|
||||
MemoryMax=1536M
|
||||
MemorySwapMax=768M
|
||||
MemoryHigh=2G
|
||||
MemoryMax=3G
|
||||
MemorySwapMax=1G
|
||||
OOMPolicy=kill
|
||||
```
|
||||
|
||||
> **⚠ Limits have been RAISED since 2026-07-25 (verified 2026-10-20).** The Camofox drop-in now
|
||||
> reads `MemoryHigh=2G`, `MemoryMax=3G`, `MemorySwapMax=1G` — the page previously recorded
|
||||
> `1G` / `1536M` / `768M`. Effective values confirmed via
|
||||
> `systemctl --user show camofox-browser.service`:
|
||||
> `MemoryHigh=2147483648` (2 GiB), `MemoryMax=3221225472` (3 GiB),
|
||||
> `MemorySwapMax=1073741824` (1 GiB), `OOMPolicy=kill`.
|
||||
> The `OOMPolicy=kill` intent is unchanged; only the ceilings moved. The Camofox service **is**
|
||||
> running (`camofox-browser.service`, active/running) — it is the browser workload the containment
|
||||
> is meant to protect, and it is the unit that grew.
|
||||
|
||||
### Hermes Web UI
|
||||
|
||||
File:
|
||||
@@ -72,6 +82,20 @@ OOMPolicy=kill
|
||||
Camofox and Web UI are allowed to restart under extreme growth instead of
|
||||
consuming most of the container and taking Telegram down with them.
|
||||
|
||||
> **Re-verified 2026-10-20 — the gateway and Web UI controls are still exactly as documented.**
|
||||
> - Gateway drop-in `/home/hermes/.config/systemd/user/hermes-gateway.service.d/resource-resilience.conf`
|
||||
> still reads `OOMPolicy=continue`, `MemoryLow=512M`, `CPUWeight=1000` (no `MemoryHigh`/`MemoryMax`).
|
||||
> Effective: `OOMPolicy=continue`, `CPUWeight=1000`, `MemoryLow=536870912`,
|
||||
> `MemoryHigh=infinity`, `MemoryMax=infinity` — **matches the "Expected gateway values" note below.**
|
||||
> - Web UI: `OOMPolicy=kill`, `MemoryHigh=1073741824` (1 GiB), `MemoryMax=1610612736` (1.5 GiB),
|
||||
> `MemorySwapMax=1073741824` (1 GiB) — **matches the drop-in shown above, unchanged.**
|
||||
> - Camofox: see the raised limits noted above.
|
||||
> - `hermes-gateway.service` and `camofox-browser.service` are both **active (running)**.
|
||||
>
|
||||
> **Note:** the Web UI drop-in lives at `/etc/systemd/system/hermes-webui.service.d/` which the
|
||||
> `hermes` user cannot read (permission denied) — its *effective* values are still verifiable via
|
||||
> `systemctl show`, which is what the health-check section below uses.
|
||||
|
||||
## I/O priority limitation
|
||||
|
||||
Do not add `IOWeight` to the gateway drop-in unless Proxmox cgroup delegation
|
||||
@@ -102,7 +126,7 @@ runuser -u hermes -- env XDG_RUNTIME_DIR=/run/user/1000 \
|
||||
|
||||
Expected gateway values include `OOMPolicy=continue`,
|
||||
`MemoryLow=536870912`, `MemoryHigh=infinity`, `MemoryMax=infinity`, and
|
||||
`CPUWeight=1000`.
|
||||
`CPUWeight=1000`. **Confirmed live on 2026-10-20** — see the note under "Active controls".
|
||||
|
||||
## Backups and rollback
|
||||
|
||||
|
||||
Reference in New Issue
Block a user