Jellyfin Instability and Crashes

[TheDreadPirate]

You can also zip the log file and attach it to a forum post. You have to open the full reply editor to attach files.

[Jam]

There seems to be a file size limit of 2.1MB on the forums. Due to extended logging, it's 42MB.

I've attached it to filebin here: https://filebin.net/9y9by2y0vdbbkbos
It has a preview when you click the file name.

[TheDreadPirate]

This was why I suggested zipping the file. Should compress down to under 2.1MB.

Regardless, this log seems to be a common factor from the prior logs.

Code:

[2024-07-26 21:57:50.591 +01:00] [ERR] [50] Jellyfin.Api.WebSocketListeners.SessionInfoWebSocketListener: Error sending web socket message Sessions
System.Net.WebSockets.WebSocketException (0x80004005): The WebSocket is in an invalid state ('Closed') for this operation. Valid states are: 'Open, CloseReceived'
   at System.Net.WebSockets.ManagedWebSocket.SendAsync(ReadOnlyMemory`1 buffer, WebSocketMessageType messageType, WebSocketMessageFlags messageFlags, CancellationToken cancellationToken)
--- End of stack trace from previous location ---

IMO, you should probably go ahead and submit a bug report to the jellyfin server git. This looks like a proper bug.

https://github.com/jellyfin/jellyfin/issues

[Jam]

Ah apologies, it's late here and didn't quite read the message in full, will note that for next time.

Glad we were able to somewhat locate the issue though! I am more than happy to create that issue my only question is what am I logging it under and what am I specifying is the bug? I'm not quite sure what accurate information to give as I am quite unsure myself.

Thanks

[TheDreadPirate]

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.

[Jam]

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.

I think you're onto something because leading up to the events of a crash, the Active Devices on the Admin Dashboard, do not load.


EDIT: I have now posted this onto GitHub.
https://github.com/jellyfin/jellyfin/issues/12346