What's new
PGBlitz.com

Register Now! Find useful tips, Interact /w Community Members and join the part the Best Community on the Internet!

Issue with Plex Deployment after using "PG Hetzner iGPU / GPU HW-Transcode" Tool

Assists Greatly with Development Costs

bordot

Junior Member
Donor
Hello,

This morning I used the PG Hetzner iGPU / GPU HW-Transcode tool and after it was completed and I rebooted, it was no longer able to properly start Plex. I keep receiving the following error:

Code:
fatal: [127.0.0.1]: FAILED! => {"changed": false, "msg": "Error starting container 0cad6fc85d15b1e4ed1639c44b359562afe558db42be8deca485868ac3a0237d: 500 Server Error: Internal Server Error (\"linux runtime spec devices: error gathering device information while adding custom device \"/dev/dri\": not a device node\")"}
The output of the GPU test is:
Code:
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 256M]
Any help would be appreciated!
 
M

MrDoob

Guest
Is this an hetzner server *?*

And what for an CPU inside *?*
 

bordot

Junior Member
Donor
That is correct, my docker image is "plexinc/pms-docker:plexpass".

Everything was working great until I used that tool. Is there just a way to revert it and go back to not using HW for trancoding?
 
M

MrDoob

Guest
ls -la /dev/dri
sudo chmod -R 777 /dev/dri
sudo apt update
sudo apt install vainfo

  • docker exec plex apt-get -y update
  • docker exec plex apt-get -y install i965-va-driver vainfo
  • docker restart plex
 

bordot

Junior Member
Donor
Plex still giving the same issue, but here's the full output of those commands:

Code:
[email protected] / # ls -la /dev/dri
total 0
drwxrwxrwx  2 root root   40 May 15 19:20 .
drwxr-xr-x 19 root root 3860 May 15 19:35 ..
[email protected] / #  sudo chmod -R 777 /dev/dri
[email protected] / #  sudo apt update
Hit:1 http://mirror.hetzner.de/ubuntu/packages xenial InRelease
Hit:2 http://mirror.hetzner.de/ubuntu/packages xenial-backports InRelease
Hit:3 http://mirror.hetzner.de/ubuntu/packages xenial-updates InRelease
Hit:4 http://mirror.hetzner.de/ubuntu/security xenial-security InRelease
Hit:5 http://security.ubuntu.com/ubuntu xenial-security InRelease
Hit:6 http://de.archive.ubuntu.com/ubuntu xenial InRelease
Hit:7 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:8 https://download.docker.com/linux/ubuntu xenial InRelease
Hit:9 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:10 http://packages.cloud.google.com/apt cloud-sdk-xenial InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
[email protected] / #  sudo apt install vainfo
Reading package lists... Done
Building dependency tree
Reading state information... Done
vainfo is already the newest version (1.7.0-1ubuntu0.1).
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
For the docker commands, I'm unable to get plex to start so it's not letting me run the commands:
Code:
[email protected] / # docker exec plex apt-get -y update
Error response from daemon: Container 0cad6fc85d15b1e4ed1639c44b359562afe558db42be8deca485868ac3a0237d is not running
[email protected] / # docker exec plex apt-get -y install i965-va-driver vainfo
Error response from daemon: Container 0cad6fc85d15b1e4ed1639c44b359562afe558db42be8deca485868ac3a0237d is not running
[email protected] / # docker restart plex
Error response from daemon: Cannot restart container plex: linux runtime spec devices: error gathering device information while adding custom device "/dev/dri": not a device node
 
M

MrDoob

Guest
Check this one >>

 

bordot

Junior Member
Donor
Check this one >>

I tried those steps, but for some reason it's not creating any files in /dev/dri. Here's the output of the commands and vainfo:

Code:
[email protected] ~ # nano /etc/default/grub.d/hetzner.cfg
[email protected] ~ # nano /etc/modprobe.d/blacklist-hetzner.conf
[email protected] ~ # sudo nano /etc/modprobe.d/blacklist-hetzner.conf
[email protected] ~ # nano /etc/default/grub.d/hetzner.cfg
[email protected] ~ # sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.0-50-generic
Found initrd image: /boot/initrd.img-4.15.0-50-generic
Found linux image: /boot/vmlinuz-4.15.0-47-generic
Found initrd image: /boot/initrd.img-4.15.0-47-generic
done
[email protected] ~ #
[email protected] ~ #     sudo usermod -a -G video root
[email protected] ~ # ls -la /dev/dri
total 0
drwxrwxrwx  2 root root   40 May 15 19:20 .
drwxr-xr-x 19 root root 3860 May 15 19:35 ..
[email protected] ~ # reboot
[email protected] ~ # ls -la /dev/dri
ls: cannot access '/dev/dri': No such file or directory
[email protected] ~ # vainfo
error: can't connect to X server!
error: failed to initialize display
Aborted

[email protected] /dev # sudo vainfo
error: XDG_RUNTIME_DIR not set in the environment.
error: can't connect to X server!
error: failed to initialize display
Aborted
 
M

MrDoob

Guest
Open portainer
> click local >
> click container >
> click plex >
> click duplicate/edit >
> volumes

And remove the line with /dev/dri
 
M

MrDoob

Guest
If this failed ..
Rollback to the original parts

Do all steps but all changes to normal
 

bordot

Junior Member
Donor
Is there a way I can just reset the plex/server settings to not attempt to use gpu trancoding and avoiding the issue of whatever my server is doing not creating the files in /dev/dri? I'd just like to go back to before I ran the tool that changed settings to prevent plex from running if possible
 
M

MrDoob

Guest
So first

You must do al steps .. again !!!

But now. If you read >>> add this you must >>> remove this ..
 

bordot

Junior Member
Donor
So first

You must do al steps .. again !!!

But now. If you read >>> add this you must >>> remove this ..
Derp. Got it working again by uncommenting the files, doing a update-grub, rebooting. Once it was rebooted, I removed the plex container completely and reinstalled it using plexguide box installer and everything is working now. Thanks for your help!
 
M

MrDoob

Guest
Here the steps >>>



if there is now:
comment out


you have to do it the other way around.

So all steps just wrong way around


if you add you have to delete it ..

except for the part with the grup reload
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads


Top NZB NewsGroups!

Members - Up To a 58% Discount!

Development Donations

 

Online statistics

Members online
3
Guests online
120
Total visitors
123
Top