2024-07-26, 10:04 PM
In the github ticket, copy and paste directly the few minutes before that websocket error and then the rest of the log after it until the crash. But you should be able to attach the ZIPPED log so the whole thing can be seen if needed.
My understanding is that the websocket with the client is entering a state that the websocket listener isn't expecting and isn't handling it gracefully.
My understanding is that the websocket with the client is entering a state that the websocket listener isn't expecting and isn't handling it gracefully.
Jellyfin 10.9.11
Ubuntu 24.04 LTS (bare metal)
Intel i3 12100 on Asus Prime H610M-E D4 mATX
32GB DDR4-3600
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
WD Green 3TB (Samba shares)
WD Red 3TB CMR (WIP Media, Test libraries)
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
Fractal Meshify 2
Corsair CX430
Ubuntu 24.04 LTS (bare metal)
Intel i3 12100 on Asus Prime H610M-E D4 mATX
32GB DDR4-3600
Intel Arc A380
OS drive - SK Hynix P41 1TB
Storage
WD Green 3TB (Samba shares)
WD Red 3TB CMR (WIP Media, Test libraries)
3x WD Red Pro 6TB CMR in RAIDZ1 (JF Library)
Fractal Meshify 2
Corsair CX430