128bytes Posted October 25, 2022 Share Posted October 25, 2022 (edited) I've had quicksync working fine for several months, its suddenly not working. Have tried rebooting container (linuxserver) and system. I'm now on 6.11.1, recently upgraded from 6.10.3 (not sure if has worked at all under 6.11.1, (Tautulli history suggests Transcoding was working until yesterday). Any attempt to transcode resorts in the client reporting that the transcoder crashed (or in iOS app case, completely crashing) I can consistently test this, Direct Play works, I force a lower resolution and it crashes. dev output: root@$:/# ls -la /dev/dri total 0 drwxrwxrwx 3 root root 140 Oct 24 18:00 ./ drwxr-xr-x 16 root root 3660 Oct 24 18:02 ../ drwxrwxrwx 2 root root 120 Oct 24 18:00 by-path/ crwxrwxrwx 1 root video 226, 0 Oct 24 18:00 card0 crwxrwxrwx 1 root video 226, 1 Oct 24 18:00 card1 crwxrwxrwx 1 root video 226, 128 Oct 24 18:00 renderD128 crwxrwxrwx 1 root video 226, 129 Oct 24 18:00 renderD129 container settings: repo - lscr.io/linuxserver/plex version - public (tried setting to 18.07.22) quicksync - /dev/dri (tried settings to /dev/dri:/dev/dri) com.plex.system.log 2022-10-24 20:47:13,746 (147fc6811b38) : ERROR (networking:196) - Error opening URL 'http://resources-cdn.plexapp.com/hashes.json' 2022-10-24 20:47:13,747 (147fc6811b38) : CRITICAL (runtime:1299) - Exception getting hosted resource hashes (most recent call last): File "/usr/lib/plexmediaserver/Resources/Plug-ins-f4cdfea9c/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/components/runtime.py", line 1291, in get_resource_hashes json = self._core.networking.http_request("http://resources-cdn.plexapp.com/hashes.json", timeout=5).content File "/usr/lib/plexmediaserver/Resources/Plug-ins-f4cdfea9c/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/components/networking.py", line 242, in content return self.__str__() File "/usr/lib/plexmediaserver/Resources/Plug-ins-f4cdfea9c/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/components/networking.py", line 220, in __str__ self.load() File "/usr/lib/plexmediaserver/Resources/Plug-ins-f4cdfea9c/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/components/networking.py", line 158, in load f = self._opener.open(req, timeout=self._timeout) File "/usr/lib/plexmediaserver/Resources/Python/python27.zip/urllib2.py", line 435, in open response = meth(req, response) File "/usr/lib/plexmediaserver/Resources/Python/python27.zip/urllib2.py", line 548, in http_response 'http', request, response, code, msg, hdrs) File "/usr/lib/plexmediaserver/Resources/Python/python27.zip/urllib2.py", line 473, in error return self._call_chain(*args) File "/usr/lib/plexmediaserver/Resources/Python/python27.zip/urllib2.py", line 407, in _call_chain result = func(*args) File "/usr/lib/plexmediaserver/Resources/Python/python27.zip/urllib2.py", line 556, in http_error_default raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) HTTPError: HTTP Error 403: Forbidden Plex Media Server.log Full log below but Im guessing highlight is Oct 24, 2022 20:48:57.543 [0x147757d68b38] ERROR - [Req#3f8/Transcode/4gfp1x9ahodb86bcb4ogtbv4/55c3b60e-f6c3-4d74-a336-3e39505395b5] [AVHWDeviceContext @ 0x145afb275780] Failed to initialise VAAPI connection: -1 (unknown libva error). Oct 24, 2022 20:48:57.543 [0x147751edeb38] ERROR - [Req#3f9/Transcode/4gfp1x9ahodb86bcb4ogtbv4/55c3b60e-f6c3-4d74-a336-3e39505395b5] Device creation failed: -5. Oct 24, 2022 20:48:57.543 [0x147756252b38] ERROR - [Req#3fa/Transcode/4gfp1x9ahodb86bcb4ogtbv4/55c3b60e-f6c3-4d74-a336-3e39505395b5] Failed to set value 'vaapi=vaapi:/dev/dri/renderD129' for option 'init_hw_device': I/O error Oct 24, 2022 20:48:57.543 [0x1477576d7b38] ERROR - [Req#3fb/Transcode/4gfp1x9ahodb86bcb4ogtbv4/55c3b60e-f6c3-4d74-a336-3e39505395b5] Error parsing global options: I/O error Intel® Core™ i7-3770K CPU @ 3.50GHz 32GB RAM GTX 1650 Hardware Profile and full log attached to clean up post... hardwareProfile And plexLog.txt Edited October 25, 2022 by 128bytes Quote Link to comment
PCR Posted October 25, 2022 Share Posted October 25, 2022 Same here. Suddenly quicksync stopped I7 6700 Quote Link to comment
PCR Posted October 25, 2022 Share Posted October 25, 2022 Oct 25, 2022 19:41:22.924 [0x14f0e004db38] ERROR - [Req#21d/Transcode/tl13mb5trqc5luc4bb7xljtd/f9226da9-28cf-4f6f-a354-88be8af6d664] [AVHWDeviceContext @ 0x1498a4a64680] Failed to initialise VAAPI connection: -1 (unknown libva error). Oct 25, 2022 19:41:22.924 [0x14f0e0acfb38] ERROR - [Req#21e/Transcode/tl13mb5trqc5luc4bb7xljtd/f9226da9-28cf-4f6f-a354-88be8af6d664] Device creation failed: -5. Oct 25, 2022 19:41:22.924 [0x14f0dea9fb38] ERROR - [Req#21f/Transcode/tl13mb5trqc5luc4bb7xljtd/f9226da9-28cf-4f6f-a354-88be8af6d664] Failed to set value 'vaapi=vaapi:/dev/dri/renderD129' for option 'init_hw_device': I/O error Oct 25, 2022 19:41:22.924 [0x14f0de699b38] ERROR - [Req#220/Transcode/tl13mb5trqc5luc4bb7xljtd/f9226da9-28cf-4f6f-a354-88be8af6d664] Error parsing global options: I/O error Oct 25, 2022 19:41:22.926 [0x14f0e513ab38] DEBUG - Jobs: '/usr/lib/plexmediaserver/Plex Transcoder' exit code for process 438 is 1 (failure) Oct 25, 2022 19:41:22.926 [0x14f0e252fb38] DEBUG - Streaming Resource: Terminating session 0x14f0e2e856a8:xpb76s3udjc0xzv8lp6mhmsq which is using transcoder slot. Used slots is now 0 Oct 25, 2022 19:41:22.926 [0x14f0e1314b38] DEBUG - Killing job. Oct 25, 2022 19:41:22.926 [0x14f0e1314b38] DEBUG - Signalling job ID 438 with 9 Oct 25, 2022 19:41:22.926 [0x14f0e1314b38] DEBUG - Job was already killed, not killing again. Oct 25, 2022 19:41:22.926 [0x14f0e1314b38] DEBUG - Stopping transcode session tl13mb5trqc5luc4bb7xljtd Oct 25, 2022 19:41:22.926 [0x14f0e252fb38] DEBUG - Streaming Resource: Terminated session 0x14f0e2e856a8:xpb76s3udjc0xzv8lp6mhmsq with reason Conversion failed. The transcoder exited due to an error. Oct 25, 2022 19:41:22.926 [0x14f0e1d23b38] DEBUG - Cleaning directory for session tl13mb5trqc5luc4bb7xljtd (/config/Library/Application Support/Plex Media Server/Cache/Transcode/Sessions/plex-transcode-tl13mb5trqc5luc4bb7xljtd-f9226da9-28cf-4f6f-a354-88be8af6d664) Quote Link to comment
PCR Posted October 25, 2022 Share Posted October 25, 2022 seems liek the PMS Update has a bug? Quote Link to comment
128bytes Posted October 25, 2022 Author Share Posted October 25, 2022 1 hour ago, PCR said: seems liek the PMS Update has a bug? I've downgraded to 1.29.0.6244-819d3678c and its working again. (In linuxserver container, you can set this in VERSION) Quote Link to comment
PCR Posted October 25, 2022 Share Posted October 25, 2022 @128bytesc Will you file the bug report to Linux-Server? Quote Link to comment
128bytes Posted October 25, 2022 Author Share Posted October 25, 2022 LinusServer is suggesting this is not their problem, plex is so far suggesting it should be using i965 not iHD so everyone is just pointing fingers... Quote Link to comment
NewDisplayName Posted October 26, 2022 Share Posted October 26, 2022 (edited) very annoying i downgraded from plex version to public and now public has the same problem, trying 1.29.0.6244-819d3678c as suggested they really good test their stuff edit: yes its working again... THANKS lets hope they fix it in the next 5 years its crazy how many things they add to plex, but the core is so buggy (?) edit2: btw i also have i7 6700k, and 1050 edit3: "it should be using i965 not iHD" What does that mean? Plex decides itself which hardware it uses Edited October 26, 2022 by nuhll Quote Link to comment
128bytes Posted October 27, 2022 Author Share Posted October 27, 2022 @nuhll this is thread on Plex forums maybe you can make more sense of it. By working again you mean on 1.29.0, right? Quote Link to comment
PCR Posted November 4, 2022 Share Posted November 4, 2022 On 10/26/2022 at 11:42 PM, nuhll said: very annoying i downgraded from plex version to public and now public has the same problem, trying 1.29.0.6244-819d3678c as suggested they really good test their stuff edit: yes its working again... THANKS lets hope they fix it in the next 5 years its crazy how many things they add to plex, but the core is so buggy (?) edit2: btw i also have i7 6700k, and 1050 edit3: "it should be using i965 not iHD" What does that mean? Plex decides itself which hardware it uses still not working with 1:29:1 Quote Link to comment
NewDisplayName Posted November 15, 2022 Share Posted November 15, 2022 (edited) yea today i also tried latest version again, not working... crazy i could change something inside the docker, but if im not mistaken, that should be done from the linuxserver crew, because it could be overwritten the next update...??! edit: i rechecked everything and forgot when you remove -e version then it wont update, so i didnt test with latest. NVIDIA I upgraded to 525.53 PLEX (PLEXPASS) "latest", which is currently 1.30.0.6359-1185e28d9 UNRAID 6.11.3 Everything working again! Edited November 15, 2022 by nuhll Quote Link to comment
Solution 128bytes Posted January 3, 2023 Author Solution Share Posted January 3, 2023 So what worked for me @PCR is adding HardwareDevicePath="/dev/dri/renderD129" to the preferences.xml https://forums.plex.tv/t/preferred-hw-transcoder-linux/593507 Quote Link to comment
NewDisplayName Posted June 5, 2023 Share Posted June 5, 2023 (edited) plex is tryin to convert h265 with igpu (which doesnt support it), even if i have in pref my gpu. So i dont know what the hell the problem is. Edited June 5, 2023 by nuhll Quote Link to comment
xZero Posted June 9, 2023 Share Posted June 9, 2023 (edited) I can confirm this issue on the latest Plex version (1.32.3.7162-b0a36929b). Issue occurs on both official docker and linuxserver images. Setting VERSION to 1.29.0.6244-819d3678c in linuxserver image works. Haven't tested with official image. It (seems?) to work better with this option in Preferences.xml UPDATE: Versions up to 1.31.3.6868-28fc46b27 seem to be working too. To speedup the startup with custom version, use docker tags instead. lscr.io/linuxserver/plex:version-1.31.3.6868-28fc46b27 Edited June 9, 2023 by xZero Quote Link to comment
cordswires Posted Wednesday at 07:45 PM Share Posted Wednesday at 07:45 PM (edited) QSV hardware transcoding broke again with 1.40.1.8227-c0dd5a73e-ls211. It's working on 1.40.0.7998-c29d4c0c8-ls208 (100% sure), and I think it's still working on ls209 and ls210 as people started reporting issues with playback last week. --edit: Did some more testing. QSV transcode works on ls210, is broken on ls211. Edited 23 hours ago by sngrstr71 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.