diff --git a/10-systems/hosts/jellyfin.md b/10-systems/hosts/jellyfin.md index 675a2e6..d479734 100644 --- a/10-systems/hosts/jellyfin.md +++ b/10-systems/hosts/jellyfin.md @@ -1,7 +1,7 @@ --- owner: gmikcon status: active -last_reviewed: 2026-09-29 +last_reviewed: 2026-10-08 review_interval: 90d confidence: high source_of_truth: ssh-host @@ -11,6 +11,8 @@ KVM VM on `hp-proliant-dl380-g6` (libvirt), LAN `192.168.1.153`, Jellyfin 10.10.3, systemd unit `jellyfin`, port 8096. Public URL: https://jellyfin.gnexus.space (nginx on internal-proxy-vps `.226` → `http://192.168.1.153:8096`). SSH: `ubuntu@192.168.1.153` (password same as Navi swarm peers). Verified live 2026-09-29. +На hard-panel (GHard Monitor): сервер **id 39**, имя `jellyfin`, 16 ГБ RAM, агент интервал 30 с. + ## Health checks - `GET /health` → 200 "Healthy" @@ -33,3 +35,7 @@ Fix: start nfs-server on gprint. Gotcha: first start failed with `errno 12 (Cannot allocate memory)` — gprint has only 1.9 GiB RAM and 1.4 GiB was in buff/cache. `sync; echo 3 > /proc/sys/vm/drop_caches` freed 1.3 GiB and the service started. Rule: if Jellyfin hangs, check `df` on all NFS mounts of the VM first, then `rpcinfo -p 192.168.1.131` (must list nfs/mountd, not just portmapper). + +## Incident 2026-10-07 21:11 UTC: transient RAM spike, self-recovered + +hard-panel alert `ram_high` 92.23% (≥90%) on panel id 39 → Synapse → Navi rei. Через ~90 с панель сама записала `ram_recovered` (RAM 4.52%) и `swap_recovered` (swap 3.3%) в 21:12:38. Характер: разовый транзиент — RAM 92%→5% (~14.5 ГБ освободилось), swap упал с хронических ≥40% до 3%. Топ-процессы после: jellyfin ~2.3% mem, CPU 0%. Похоже на page-cache/транскод-всплеск с последующей выгрузкой; своп ≥40% наблюдался до этого (событие swap_high за пределами окна журнала). Действий не потребовалось, владелец уведомлён. Если ram_high на jellyfin начнёт повторяться регулярно — смотреть логи Jellyfin (`/var/log/jellyfin/`) и активные транскод-сессии. diff --git a/90-maintenance/pending-changes/20261007211620-8ddeefa7.json b/90-maintenance/pending-changes/20261007211620-8ddeefa7.json new file mode 100644 index 0000000..1a795a5 --- /dev/null +++ b/90-maintenance/pending-changes/20261007211620-8ddeefa7.json @@ -0,0 +1,19 @@ +{ + "id": "20261007211620-8ddeefa7", + "kind": "doc", + "target": "10-systems/hosts/jellyfin.md", + "summary": "jellyfin.md: добавлен panel id 39 и заметка о транзиентном RAM-всплеске 2026-10-07 21:11 UTC (самовосстановление за ~90 с)", + "reason": "Реакция на hard-panel алерт ram_high server_id=39: идентифицирован сервер jellyfin (192.168.1.153), транзиентный всплеск RAM самоустранился за ~90 с. Фиксирую panel id 39 и характер инцидента для будущих реакций.", + "payload": { + "content": "---\nowner: gmikcon\nstatus: active\nlast_reviewed: 2026-10-08\nreview_interval: 90d\nconfidence: high\nsource_of_truth: ssh-host\n---\n\n# Jellyfin VM\n\nKVM VM on `hp-proliant-dl380-g6` (libvirt), LAN `192.168.1.153`, Jellyfin 10.10.3, systemd unit `jellyfin`, port 8096. Public URL: https://jellyfin.gnexus.space (nginx on internal-proxy-vps `.226` → `http://192.168.1.153:8096`). SSH: `ubuntu@192.168.1.153` (password same as Navi swarm peers). Verified live 2026-09-29.\n\nНа hard-panel (GHard Monitor): сервер **id 39**, имя `jellyfin`, 16 ГБ RAM, агент интервал 30 с.\n\n## Health checks\n\n- `GET /health` → 200 \"Healthy\"\n- `GET /System/Info/Public` → JSON with version\n- Logs: `/var/log/jellyfin/jellyfinYYYYMMDD*.log` (rotated ~10 MB)\n\n## Storage (NFS mounts on the VM)\n\n| Mount on VM | NFS export | Note (2026-09-29) |\n| --- | --- | --- |\n| `/home/ubuntu/jf_storage/firstraid5_storage` | `192.168.1.130:/mnt/firstraid5` | 100% full, 0 B free; `music/` folder is empty |\n| `/home/ubuntu/jf_storage/secraid5_storage` | `192.168.1.130:/mnt/secraid5/jellyfin_storage` | 126 GB free (94% used) |\n| `/home/ubuntu/jf_cache` | `192.168.1.130:/mnt/secraid5/jellyfin_cache` | 99% free |\n| `/home/ubuntu/jf_storage/NetTera8` | `192.168.1.131:/mnt/NetTera8` | 100% full (7.3 TB used) |\n\n## Known incident (2026-09-29): NFS hang from gprint\n\nSymptom: Jellyfin \"not working\" — library scans/streams hang, processes stuck in D-state. Root cause: `nfs-server.service` on `gprint` (192.168.1.131, NetTera8 export) was `inactive (dead)` since 14:51 UTC (stopped during the 2026-09-29 gprint cleanup). The NetTera8 NFS mount on the Jellyfin VM hung on any access (`df`, `stat`, `ls` all timed out).\n\nFix: start nfs-server on gprint. Gotcha: first start failed with `errno 12 (Cannot allocate memory)` — gprint has only 1.9 GiB RAM and 1.4 GiB was in buff/cache. `sync; echo 3 > /proc/sys/vm/drop_caches` freed 1.3 GiB and the service started.\n\nRule: if Jellyfin hangs, check `df` on all NFS mounts of the VM first, then `rpcinfo -p 192.168.1.131` (must list nfs/mountd, not just portmapper).\n\n## Incident 2026-10-07 21:11 UTC: transient RAM spike, self-recovered\n\nhard-panel alert `ram_high` 92.23% (≥90%) on panel id 39 → Synapse → Navi rei. Через ~90 с панель сама записала `ram_recovered` (RAM 4.52%) и `swap_recovered` (swap 3.3%) в 21:12:38. Характер: разовый транзиент — RAM 92%→5% (~14.5 ГБ освободилось), swap упал с хронических ≥40% до 3%. Топ-процессы после: jellyfin ~2.3% mem, CPU 0%. Похоже на page-cache/транскод-всплеск с последующей выгрузкой; своп ≥40% наблюдался до этого (событие swap_high за пределами окна журнала). Действий не потребовалось, владелец уведомлён. Если ram_high на jellyfin начнёт повторяться регулярно — смотреть логи Jellyfin (`/var/log/jellyfin/`) и активные транскод-сессии." + }, + "status": "applied", + "created_at": "2026-10-07T21:16:20Z", + "updated_at": "2026-10-07T21:16:22Z", + "applied_at": "2026-10-07T21:16:22Z", + "validation": { + "status": "ok", + "issue_count": 0, + "issues": [] + } +}