Titan84

Hi @spants Im also having the same issues with MQTT and getting the following errors... 1664719186: Saving in-memory database to /config/data/mosquitto.db. 1664719186: Error saving in-memory database, unable to open /config/data/mosquitto.db.new for writing. 1664719186: Error: Permission denied. I know that you have provided us a workaround test MQTT but since this was suggested back in July i was wondering if a new updated container was coming out soon. If not and its still a long while away, please could you let me know and then ill continue down the path of the workaround solution. Im really hoping that the new version isnt too far away 🙂 Thanks again for all your containers and support that you give!

@ich777 thanks, yip I can buy that one here in Australia on Amazon too so all good. Just ordered one. Small price to pay for some piece of mind.

@ich777 do you have a dummy plug that you would recommend? I'm not using 1 either and currently i dont have any issues but reading this im thinking that adding one won't hurt 🙂

Yeah this is exactly what happened to me too 😞 Just broke after update and im getting the following, s6-supervise pihole-dot-doh (child): fatal: unable to exec run: Permission denied s6-supervise pihole-dot-doh: warning: unable to spawn ./run - waiting 10 seconds Im on Unraid version 6.11.0-rc4... not sure if that makes a difference.

Yeah, my GPU stat's plugin also maintains the power draw bar at full after I have finished the transcode. I think it's the plugin though that just needs updating.

Yeah @xXx I have everything installed just as you have there and I get the exact same errors.

So after reading all the different results people were getting I thought what the heck, ill try too... I have a 12900K Unraid 6.11-RC2 with GPU_TOP installed and plex pass with the normal public release channel and beta plex app. I also have the following applied in PLEX, "Enable HDR tone mapping" disabled "Use hardware acceleration when available" enabled "Use hardware-accelerated video encoding" enabled And just as some mentioned here, the 1st transcode plays just fine but as soon as I try the 2nd transcode BAM Plex crashes haha oh well I had some very, very low hopes 😀 PLEX is releasing a new update soon so might be lucky then. Also, not sure if it will make any difference but the new Kernel 5.19 is now released so maybe unraid 6.11-RC3 will have that. Cant hurt I guess, will hopefully increase our chances.

I have an i9-12900K and upgraded yesterday to 6.11-RC1 and so far no issues to report. I have enabled the iGPU in PLEX again but only did a very brief test and transcoding worked for me without crashing. I did have HDR Tone mapping set to off and did a basic test on a 1080p movie. I know its still hit and miss at the moment so have turned HW transcoding off for the moment until PLEX release their new version and some more fixes in PMS 1.28.1 or 1.28.2. At least we are moving forward and now we have the Linux Kernel updated to the version we need. Now we wait for PLEX to catch up 😞

Very interesting.... I recon it might be the modprobe that was appended. causing the issue Are you able to try the PLEX official docker but leave the modprobe removed? Thanks for the testing and sharing the results! 🙂

@flyize This is great progress! its giving me some hope now that 5.18.xx will get PLEX transcoding back up and running. I think we will get there with the 5.18 Kernels eventually. Please keep up your great work and reporting back as the new updated Kernels come out.

Upgraded from RC7 to 6.10 Stable and no issues at all. 🙂

woohoo, i cant wait Great work all!!

@flyize yeah im in the same boat as you are 😞 but at least there is light at the end of the tunnel haha 🙂 Im also following the Linux Kernel release schedule for 5.18 and it looks to be released by the end of May so im hopeful that @limetech will be able to update the 6.11 RC1 release with this latest Kernal 🙂