Server Version#: 1.40.5.8897
I am running Plex in a Debian 12 LXC.
It seems like every time I stream and transcode the server hangs after some time, and I have to restart it in order to be able to access it again, it becomes totally unavailable, cannot access via web or apps. I have attached the logs I pulled after restarting the server after one such event.
I don’t see CPU usage spike above 40% and the container has 4GB of memory and doesn’t go near that.
Plex Media Server Logs_2024-08-31_12-26-14.zip (4.1 MB)
ChuckPa
September 1, 2024, 2:23am
2
How long does it run before hanging?
I have both AlderLake-S (i9-12900) in a LXC container (Ubuntu 22.04)
Neither hang.
Simple annoying things:
You have an IPv4 lan but IPv6 enabled
Aug 31, 2024 11:20:49.095 [135782566210360] DEBUG - Request: [192.168.1.50:44720 (Subnet)] GET /media/providers (9 live) #2bcc1 GZIP Signed-in Token (mat.mur) (Chrome)
Settings - Server - Network - Show Advanced – Disable the IPv6. It’ll make networking / life easier.
mat_mur
September 3, 2024, 6:40pm
3
Thanks, I’ve updated my settings. Not sure how long it takes before hanging. It’s been pretty stable the last few days. I will continue to monitor and pull the logs again when it hangs.
mat_mur
September 13, 2024, 4:36pm
4
Issue happened again last night. I was watching from my PC for a while, took a break, then attempted to connect to Plex from my phone and it was unavailable. I needed to restart the server to fix the issue. I believe I was using transcoding the entire time, since I was using subtitles. Additional logs attached.
Plex Media Server Logs_2024-09-13_09-31-58.zip (4.3 MB)
ChuckPa
September 15, 2024, 4:51pm
5
@mat_mur
According to your logs, it’s not hanging.
It’s not getting a GPU.
Sep 12, 2024 22:39:52.384 [127977348148024] DEBUG - Starting a transcode session p0y3n3c6rji655r8yu5zsayc at offset 542.0 (state=3)
Sep 12, 2024 22:39:52.384 [127977348148024] DEBUG - TPU: hardware transcoding: enabled, but no hardware decode accelerator found
Sep 12, 2024 22:39:52.384 [127977348148024] DEBUG - [Universal] Using local file path instead of URL: /media/organized/TV Shows/Solo Leveling {tvdb-389597}/Season 01/Solo Leveling - S01E06 - The Real Hunt Begins.mkv
Sep 12, 2024 22:39:52.385 [127977348148024] INFO - CodecManager: obtaining encoder 'libx264'
and
Sep 12, 2024 20:53:11.346 [127977278942008] DEBUG - [Req#de8e1/Transcode] Starting a transcode session h9w0pin4ews4igk3trb5tq0r at offset -1.0 (state=3)
Sep 12, 2024 20:53:11.346 [127977278942008] DEBUG - [Req#de8e1/Transcode] TPU: hardware transcoding: enabled, but no hardware decode accelerator found
Sep 12, 2024 20:53:11.346 [127977278942008] DEBUG - [Req#de8e1/Transcode] [Universal] Using local file path instead of URL: /media/organized/TV Shows/Solo Leveling {tvdb-389597}/Season 01/Solo Leveling - S01E06 - The Real Hunt Begins.mkv
Sep 12, 2024 20:53:11.346 [127977278942008] DEBUG - [Req#de8e1/Transcode] TPU: hardware transcoding: final decoder: , final encoder:
Sep 12, 2024 20:53:11.346 [127977278942008] DEBUG - [Req#de8e1/Transcode/JobRunner] Job running: FFMPEG_EXTERNAL_LIBS='/var/lib/plexmediaserver/Library/Application\ Support/Plex\ Media\ Server/Codecs/b8ae7ab-cd9c26e1cae8f48631565a53-linux-x86_64/' X_PLEX_TOKEN=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx "/usr/lib/plexmediaserver/Plex Transcoder" -codec:0 h264 -noaccurate_seek -analyzeduration 20000000 -probesize 20000000 -i "/media/organized/TV Shows/Solo Leveling {tvdb-389597}/Season 01/Solo Leveling - S01E06 - The Real Hunt Begins.mkv" -map 0:0 -codec:0 copy -map 0:1 -metadata:s:1 language=jpn -codec:1 copy -f dash -seg_duration 5 -dash_segment_type mp4 -init_seg_name 'init-stream$RepresentationID$.m4s' -media_seg_name 'chunk-stream$RepresentationID$-$Number%05d$.m4s' -window_size 5 -delete_removed false -skip_to_segment 1 -time_delta 0.0625 -manifest_name "http://127.0.0.1:32400/video/:/transcode/session/h9w0pin4ews4igk3trb5tq0r/f92a9ca1-ba00-4176-bf68-ac7d712363af/manifest?X-Plex-Http-Pipeline=infinite" -avoid_negative_ts disabled -map_metadata -1 -map_chapters -1 dash -start_at_zero -copyts -vsync cfr -y -nostats -loglevel quiet -loglevel_plex error -progressurl http://127.0.0.1:32400/video/:/transcode/session/h9w0pin4ews4igk3trb5tq0r/f92a9ca1-ba00-4176-bf68-ac7d712363af/progress
Sep 12, 2024 20:53:11.346 [127977278942008] DEBUG - [Req#de8e1/Transcode/JobRunner] In directory: "/dev/shm/Transcode/Sessions/plex-transcode-h9w0pin4ews4igk3trb5tq0r-f92a9ca1-ba00-4176-bf68-ac7d712363af"
Would like to ask more about Hardware and where you’re at with the PMS versions?
Reason is: I’m slow
You say Debian, the logs show Ubuntu
You say AlderLake, the logs show MeteorLake
Would like clarification and resync please .
Since this thread was opened,
22.04.5 LTS has been fully released (contains lot of fixes for transcoding)
PMS 1.41.0 Public also has fixes for transcoding.
There are others who have successfully transcoded with the MeteorLake CPU (-14xxx) . [[ AlderLake is the -12xxx CPU family ]]
mat_mur
September 15, 2024, 8:40pm
6
You say Debian, the logs show Ubuntu
You’re right, I was thinking of a different container.
You say AlderLake, the logs show MeteorLake
Right again, >.< I was going to get a 12500 because I heard there might be transcoding problems on AlderLake, but ended up getting a good deal on a 14500.
I will upgrade software versions and continue to observe. Will look for this error next time I see problems. Very odd that the GPU would go away, not like the device mounting is changing or something.
ChuckPa
September 15, 2024, 9:07pm
7
I have AlderLake. No problems whatsoever
root@lizum:/home/chuck# cat /proc/cpuinfo | grep 'model name' | uniq
model name : 12th Gen Intel(R) Core(TM) i9-12900
root@lizum:/home/chuck#
mat_mur
September 15, 2024, 9:35pm
8
I’ve updated to the latest PMS and Ubuntu.
root@plex:~# lsb_release -d
PMS: Version 4.136.1
One thing to note. In the transcoder menu Plex sees my MeteorLake hardware transcoding device as “AlderLake-S GT1”. Could that be causing an issue?
I will bring another set of logs if I encounter the issue again. Thanks for all your help so far!
ChuckPa
September 15, 2024, 9:54pm
9
No. that won’t cause an issue.
We need to get the GPU Device ID codes from both Intel and Nvidia for display purposes:
Here’s my RTX 2000 (ada generation) – which works perfectly.
system
December 14, 2024, 9:54pm
10
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
