Not expecting a fix as I understand 5.0 is beta; but I’m actually getting the same issue as @DarrOlson . Tried the previous package (Attached above) and also latest through the web prompt with the same result. It’s not a huge deal for me as it still works with the older version but not sure the reason. I didn’t try to nuke it and reinstall Plex again as everything still works but might be an option for some.
The same scripting runs for each different binary (X86_64, ARMv7, ARMv8, etc) If it builds for one, it builds for all. That’s how we built the packaging system.
Actually got to like 46% then gave the same message; looking at the icon in the back it switches from “Updating” with a quarter pie then goes back to nothing then back again. Does this maybe 5 times before failing, going to keep messing around.
If I run it from SSH and turn on my admin account I get this:
If I do it with my user account I get “Permission Denied” on a bunch of folders; although I don’t recall which account I’ve used in the past to update as admin is disabled generally. Going to visit perms I guess.
For me I never got it to get right and ended up hosing my plex install eventually by poking too many things over SSH although most of my efforts were permission changes. I ended up downgrading to 4x then clean installing latest Plex and then upgrading back to 5 beta. When I did downgrade QTS (before I hosed the Plex install) it gave the same error in 4x.
I’ll be curious to see what the next Plex release does to see if I get the same issue upgrading. Fun of betas though.
Confirming on my end also. Updated out of beta on my 453be to 5.0.0.1808 and installed the latest prompted version from Plex 1.24.4.5081 and everything installed as expected. So I’m happy…still curious what the issue was since it seems some were good to go the whole time.
I had the Plex issue on my TS-253B and downgraded because of it. I cannot comment on the issue at the moment because I installed QTS 5.0.0.1808 with the latest Plex Version 1.24.4.5081 already installed. Everything seems to be running as it should though.
I just updated my TS-873 to QNAP5 (stable 5.0.0.1828 build 20211020)
I am running the latest PMS ( 1.24.5.5160)
Hardware transcoding does not work for me anymore. It worked before (using a 1050Ti), the settings are the same (I checked) and seem to be working. The card is in QTS mode, it is being detected and I can see it is not being used (0%).
I get these errors in the log:
Oct 23, 2021 20:26:40.279 [0x7f2b4e3c2b38] Verbose — [Transcode] [FFMPEG] - libva: VA-API version 1.9.0
Oct 23, 2021 20:26:40.279 [0x7f2b4e3c2b38] Error — [Transcode] [FFMPEG] - libva: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
Oct 23, 2021 20:26:40.279 [0x7f2b4e3c2b38] Error — [Transcode] [FFMPEG] - Failed to initialise VAAPI connection: -1 (unknown libva error).
Is there anything I can try to do, to get it working again?
I have just restarted the QNAP (again - fourth time), and it magically started working again!
I have NO idea what went wrong before, if it does go wrong again, I will try to get debugging information!
Yes, the machine is AMD and yes I am using a 1050Ti for hw transcoding, it is working again!
I have attached the logs if you are still interested in looking at them