Newer
Older
gnexus-book / 10-systems / hosts / jellyfin.md

owner: gmikcon status: active last_reviewed: 2026-10-07 review_interval: "90d" confidence: high

source_of_truth: ssh-host

jellyfin

Home LAN media server running Jellyfin — the family media library and streaming backend (watched via Jellyfin clients; torrent downloads arrive via Transmission elsewhere).

Identity

  • Hostname: jellyfin
  • IP: 192.168.1.153
  • User: ubuntu (sudo with same password)
  • Credentials: gnexus-creds secret jellyfin (192.168.1.153) — SSH ubuntu (id 84a01b86-ec1d-41d1-927b-253f9b4c1770, SSH = sudo password; verified by SSH login 2026-10-07)

Platform

  • OS: Ubuntu 22.04.4 LTS
  • Kernel: 5.15.0-112-generic
  • RAM: 16 GB
  • Swap: 1.4 GB (swappiness 60)
  • Disks: / 29 GB (~48% used), /home 161 GB (~0.5% used)
  • Uptime: long-running (40+ days as of 2026-10-07)

Services

  • jellyfin.service — Jellyfin Media Server, HTTP port 8096 (health endpoint /health returns 200 "Healthy")
  • ssh.service — port 22
  • hard-monitor.service — GHard Monitor agent

Monitoring

  • GHard panel: server jellyfin, id 39, status online, interval 30s.
  • Not registered as a health-check service on the panel (only server metrics).

Known issue: daily OOM-kill cycle (documented 2026-10-07)

Diagnosed by navi rei via SSH (read-only) after repeated ram_high/swap_high/swap_recovered events:

  • Pattern: every evening (~20:48–21:12 UTC, drifting later each day) an 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.
  • Not cron/timers: /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).
  • Slow memory leak suspected: the kill time drifts later each day (20:48 → 21:10 over several days), consistent with a leak in the transcoding path.
  • Current mitigation: none applied — systemd auto-restart masks the outage; playback interruptions are brief.
  1. systemd drop-in for jellyfin.service: MemoryMax=4G (or similar) so a runaway ffmpeg is capped before global OOM.
  2. Lower vm.swappiness to 10 (swap currently fills to 100% before OOM fires).
  3. In Jellyfin settings: enable hardware-accelerated transcoding and/or cap transcode threads; review the library-scan schedule.
  4. Consider upgrading RAM if transcoding demand is real (16 GB is tight for 4K remux + scan).

Notes

  • Host was missing from gnexus-book inventory until 2026-10-07 (added by navi rei after the OOM incident).
  • No docker on this host; Jellyfin runs as a native systemd service.