I just removed Nvidia and reinstalled.
Same issue. Why it works with previous Plex Version?
Going to check things again:
-
when you look in /dev/dri. you see renderD128 and renderD129 ?
-
PMS wants to lean to renderD129
Mar 10, 2023 13:12:42.302 [0x7f499e8efb38] DEBUG - [GPU] Got device: TU102GL [Quadro RTX 6000/8000], nvidia@unknown, default true, best true, ID /dev/dri/renderD129, DevID [10de:1e30:103c:129e], flags 0x7
Mar 10, 2023 13:12:42.302 [0x7f499e8efb38] DEBUG - [GPU] Got device: TU102GL [Quadro RTX 6000/8000], nvidia@unknown, default false, best false, ID /dev/dri/renderD128, DevID [10de:1e30:103c:129e], flags 0x7
-
You’ve tried both ?
-
The host is Ubuntu 22.04 ?
The interesting part is I don’t have any problem with previous plex version 1.29.2.6364-6d72b0cf6.
Also running the latest plex version on bare metal works fine as well.
I current have two Plex running at the same Server. One is on Bare metal and other running on docker Ipvlan.
The reason is due to the way Plex setup Live Channels in the same location making unbearable to locate channels.
When I try running channels on Plex Bare metal, I see the error, but it does not fail. This happens on Plex Ipvlan docker.
@ChuckPa so is it safe to update now ? (from Version 1.29.2.6364 to newest 1.31.2.6783-9209b39b4 without losing transcoding ?) my server is on dedicated bare metal
Hold up just a bit. There might be a ‘hotfix’ applies to Public & PlexPass.
We’re digging into it now and will know definitively as soon as the new binary is built.
Thank you Chuck!
OK, that was a false alarm.
Thought there was a problem.
Turns out to be a site-specific problem.
Engage at will
What does that mean?
What does it mean?
-
Just as I wrote – "There might be a ‘hotfix’.
-
It was serious enough to make 100% certain what the status was and if it impacted PMS releases.
-
Worked through the problem and found the root cause.
-
The root cause came down to be permissions in /var/lib/plexmediaserver making PMS fail.
-
When the permissions problem was corrected, PMS returned to normal.
Can confirm that after updating from 1.29.2.6364 to newest 1.31.2.6783…(yes I know there is a 1.31.3.6819 release, but my server do not see that version yet ???) all are STILL working…thanks 
@enjoyiptv what version of Nvidia drivers are you using?
Also is this on docker or Bare metal?
my card uses Nvidia 470 drivers…and it shows i’m using version CUDA 10 as max… Card are GT 710…and yes bare metal server
My issues are with docker.
The bare metal version works like a charm using CUDA 12 and 525.85.05 with plex version 1.31.3.6819
Docker passes through to the drivers on the host.
There should be nothing installed in the container.
You can upgrade the DEB inside the container if you wish.
Pardon my lack of knowledge. Do you have details how to do so?
When I try it does not work
Correction:
I was able to figured out a way to upgrade to latest version
But I am still having the same issue.. I am actually REALLY confused here why I can’t make it work on docker post 1.29 plex version and it works fine on bare metal..
Same PC, same hardware..
Just to confirm –
To do the install / upgrade inside the container –
- Download the DEB file
- Copy the DEB file to wherever
/configfor that container maps in the filesystem - sudo docker exec -it container_name bash
- dpkg -i /config/filename.DEB
- exit
- Restart the container
I need your DEBUG logs ZIP file please.
Can you also show me the nvidia-smi output?
Upgrade was successful. Please find logs and screenshot inside of the container. I am using portainer for that.
