+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Jellyfin 10.9.1 locking up (/t-jellyfin-10-9-1-locking-up)
Jellyfin 10.9.1 locking up - dontcryforme - 2024-05-13
I'm running the linuxserver/jellyfin:10.9.1 container. everything working fine and then Jellyfin locks up, everything freeze, cant connect via web or Android TV. I have to restart the container.
Had a look at the log file, and this was the last bit before having to restart the container.
Code:
[2024-05-13 21:32:00.057 +02:00] [INF] [51] Jellyfin.Plugin.PlaybackReporting.EventMonitorEntryPoint: Processing playback tracker : "b3e52a6b46e3f3ee98055a3ef1373b836f6cefd8-07e4f4f654074d04b991c825bf219e18-b20495b8de9b75181322a26bcd40801a"
[2024-05-13 21:32:26.670 +02:00] [INF] [58] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
[2024-05-13 21:32:26.670 +02:00] [INF] [58] Emby.Server.Implementations.Session.SessionWebSocketListener: Sending ForceKeepAlive message to 1 inactive WebSockets.
[2024-05-13 21:33:02.751 +02:00] [INF] [100] Emby.Server.Implementations.Session.SessionWebSocketListener: Lost 4 WebSockets.
[2024-05-13 21:39:39.809 +02:00] [INF] [518] Emby.Server.Implementations.Session.SessionManager: Playback stopped reported by app "Android TV" "0.16.10" playing "<<<movie>>>>". Stopped at "5581614" ms
[2024-05-13 21:41:20.808 +02:00] [INF] [628] Emby.Server.Implementations.Session.SessionManager: Sending shutdown notifications
[2024-05-13 21:41:27.322 +02:00] [ERR] [634] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request: "Unexpected end of request content". URL "POST" "/Users/AuthenticateByName".
[2024-05-13 21:41:29.348 +02:00] [ERR] [636] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "xxx.xxx.xxx.xxx" WebSocketRequestHandler error
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 ---
at Emby.Server.Implementations.HttpServer.WebSocketConnection.ProcessInternal(PipeReader reader)
at Emby.Server.Implementations.HttpServer.WebSocketConnection.ReceiveAsync(CancellationToken cancellationToken)
at Emby.Server.Implementations.HttpServer.WebSocketManager.WebSocketRequestHandler(HttpContext context)
at Emby.Server.Implementations.HttpServer.WebSocketManager.WebSocketRequestHandler(HttpContext context)
[2024-05-13 21:41:29.450 +02:00] [ERR] [636] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "xxx.xxx.xxx.xxx" WebSocketRequestHandler error
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 ---
at Emby.Server.Implementations.HttpServer.WebSocketConnection.ProcessInternal(PipeReader reader)
at Emby.Server.Implementations.HttpServer.WebSocketConnection.ReceiveAsync(CancellationToken cancellationToken)
at Emby.Server.Implementations.HttpServer.WebSocketManager.WebSocketRequestHandler(HttpContext context)
at Emby.Server.Implementations.HttpServer.WebSocketManager.WebSocketRequestHandler(HttpContext context)
[2024-05-13 21:41:29.450 +02:00] [ERR] [636] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "xxx.xxx.xxx.xxx" WebSocketRequestHandler error
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 ---
at Emby.Server.Implementations.HttpServer.WebSocketConnection.ProcessInternal(PipeReader reader)
at Emby.Server.Implementations.HttpServer.WebSocketConnection.ReceiveAsync(CancellationToken cancellationToken)
at Emby.Server.Implementations.HttpServer.WebSocketManager.WebSocketRequestHandler(HttpContext context)
at Emby.Server.Implementations.HttpServer.WebSocketManager.WebSocketRequestHandler(HttpContext context)
[2024-05-13 21:41:29.451 +02:00] [ERR] [636] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "xxx.xxx.xxx.xxx" WebSocketRequestHandler error
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 ---
at Emby.Server.Implementations.HttpServer.WebSocketConnection.ProcessInternal(PipeReader reader)
at Emby.Server.Implementations.HttpServer.WebSocketConnection.ReceiveAsync(CancellationToken cancellationToken)
at Emby.Server.Implementations.HttpServer.WebSocketManager.WebSocketRequestHandler(HttpContext context)
at Emby.Server.Implementations.HttpServer.WebSocketManager.WebSocketRequestHandler(HttpContext context)RE: Jellyfin 10.9.1 locking up - PoMpls - 2024-05-13
This has happened to me twice too, since I updated to 10.9 and it did it again just now 10 minutes ago already updated to 10.9.1
Between one thing and another it is exhausting
.... if I know, I didn't update from 10.8.13 which worked like a charmEDIT:
It's happened again, it's when I watch live TV
Code:
Emby.Server.Implementations.Session.SessionWebSocketListener: Lost 1 WebSocketsRE: Jellyfin 10.9.1 locking up - STM - 2024-05-13
<- Ignore this post please.