+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Docker container transcoding crash (/t-docker-container-transcoding-crash)
Docker container transcoding crash - Ranbato - 2025-07-23
Over the last month or so my Jellyfin has been crashing randomly while streaming to my Tizen TV client. I've seen this with 1080p h264 ac3 files as well as DVD MPEG files.
I tried duplicating it streaming to Chrome, but was unsuccessful.
I'm running on a UGreen DX6800 Pro with 32GB RAM and ~25TB storage
Intel Core i5-1235U
Jellyfin 10.10.7
Hardware transcoding is turned on
I'm running 24 Docker containers, but CPU stays below 15-25% usage and memory usage is about 40%
VGA compatible controller: Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] (rev 0c)
DeviceName: Onboard - Video
Kernel driver in use: i915
Kernel modules: i915
UMD Version: Mesa 22.3.6
OpenGL Version: 4.6 (Core) / 4.6 (Compatibility)
Vulkan Version: 1.3.230 OpenCL Version: 3.0 NEO
Jellyfin log https://pastebin.com/pFywN03j
Transcode 1 https://pastebin.com/YkwMbmTz
Transcode 2 https://pastebin.com/JSVGGPYS
Transcode 3 https://pastebin.com/bs7dxP7m
RE: Docker container transcoding crash - Ranbato - 2025-08-08
Happened again last night. Any ideas?
As I look in the Jellyfin log, it looks like it is crashing regularly but I'm unclear how to fix it.
Transcode 1 https://pastebin.com/kU6t7ELs
Transcode 2 https://pastebin.com/bq7CcWZm
Transcode 3 https://pastebin.com/dni9fm0R
Jellyfin log https://pastebin.com/H0vCJFdD
RE: Docker container transcoding crash - bitmap - 2025-08-08
You have a lot of errors in there from improperly named subtitles that might be confusing ffprobe. Rename them to be the filename minus extension .srt or .en.srt with the two-digit language code. There's even one in there that uses the three-digit language code that passes muster. Dual extensions seem to be problematic.
Transcodes 1 and 3 look normal -- no early exit and the timing seems about right. Transcode 2 gets a q command from Jellyfin, meaning something may have gone wrong there. I see two fatal events related to HTTP client timeout and possibly websockets.
Code:
System.Threading.Tasks.TaskCanceledException: The request was canceled due to the configured HttpClient.Timeout of 5 seconds elapsing.
---> System.TimeoutException: The operation was canceled.
---> System.Threading.Tasks.TaskCanceledException: The operation was canceled.
---> System.IO.IOException: Unable to read data from the transport connection: Operation canceled.
---> System.Net.Sockets.SocketException (125): Operation canceled
--- End of inner exception stack trace ---
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Int32>.GetResult(Int16 token)
at System.Net.Http.HttpConnection.<EnsureReadAheadTaskHasStarted>g__ReadAheadWithZeroByteReadAsync|40_0()
at System.Net.Http.HttpConnection.SendAsync(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
--- End of inner exception stack trace ---I also took a look into the known issues on Linux and you'll want to check your kernel to see if it falls within the "incomplete support" category. This all depends on what you're running (e.g., Debian, Ubuntu) but details are in the list.
https://jellyfin.org/docs/general/post-install/transcoding/hardware-acceleration/known-issues#intel-on-linux
RE: Docker container transcoding crash - Ranbato - 2025-08-13
I'm running my NAS locally and this TV is hardwired. I have a reverse-proxy but this TV is hitting the container directly as I'm running the container in host mode.
Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.27
As far as I can tell, I believe everything is supported based on the Kernel version and what I can decipher from the page. Had to look up most of the acronyms.
I asked TMM to rename all of the subtitle files so we'll see how that goes.