owner: gmikcon status: active last_reviewed: 2026-10-07 review_interval: "90d" confidence: high
Home LAN media server running Jellyfin — the family media library and streaming backend (watched via Jellyfin clients; torrent downloads arrive via Transmission elsewhere).
jellyfin192.168.1.153ubuntu (sudo with same password)jellyfin (192.168.1.153) — SSH ubuntu (id 84a01b86-ec1d-41d1-927b-253f9b4c1770, SSH = sudo password; verified by SSH login 2026-10-07)/ 29 GB (~48% used), /home 161 GB (~0.5% used)jellyfin.service — Jellyfin Media Server, HTTP port 8096 (health endpoint /health returns 200 "Healthy")ssh.service — port 22hard-monitor.service — GHard Monitor agentjellyfin, id 39, status online, interval 30s.Diagnosed by navi rei via SSH (read-only) after repeated ram_high/swap_high/swap_recovered events:
ffmpeg process spawned by Jellyfin (uid 109) grows to ~14.5–14.8 GB RSS on the 16 GB box; the kernel OOM-killer kills it, jellyfin.service fails with oom-kill and systemd restarts it immediately. Swap fills to 100% during the ramp-up and then drains over ~24 h — producing daily swap_high → swap_recovered event pairs on the panel./etc/cron.d, user crontabs and systemd timers are standard; the trigger is Jellyfin activity itself (library scan with ~140 ffprobe calls + evening remux playback sessions).jellyfin.service: MemoryMax=4G (or similar) so a runaway ffmpeg is capped before global OOM.vm.swappiness to 10 (swap currently fills to 100% before OOM fires).