September 9, 2025Sep 9 I'm having issues with transcoding on an Ultra 7 265K for Plex. I have Unraid 7.1.4 . /dev/dri/ is added I am able to see the card0 and renderd128I am not able to see the iGPU in the gpu plugIs there something I am missing? Plex hw selection is turned on. I was able to get it working with a NVIDIA GPU but not my intel iGPU.
September 9, 2025Sep 9 4 hours ago, ohmaxx said:Hello I have followed all theses steps, i can connect correctly in local like you in step 7, but in step 8 spanner icon > settings > general i cant see the warning to reclaim so i cant do the step 9 and my librairies stay emptyI even try to add a token claim variable in the docker settings (seen that from reddit post) but didnt change anything.If you can help me i will be glad to give all the needed information thank you !I just did the reset and I'm getting the same as you now. Have you found a solution yet? I don't have the claim variable like you do though. Either way, I'll keep digging and report back if I find something.
September 9, 2025Sep 9 15 minutes ago, RichJacot said:I just did the reset and I'm getting the same as you now. Have you found a solution yet? I don't have the claim variable like you do though. Either way, I'll keep digging and report back if I find something.Hey mate i have go the hard and and find a solution (probably not the optimize one but atleast i got my plex back), for the claime variable that's normal she's not include by default on the template but from what i read on plex docker she should so idk. For the solution : 1 - shutdown your binhex plex instance2 - Go to the unraid community app and install the Plex-Media-Server from the official source 3 - Complete the variable from the Docker template you will have a Claim variable by default so go to the plex.tv/claim and put the code you get4 - Start the new docker, connect through it by ur http://[localip]:32400 (so directly from your network and not from internet) 5 - Verify you have the correct access it should ask you too configure your library just bypass this step, go to settings and you should see that your server is available from internet (thats perfect it mean the claim woked)6 - Shutdown the plex-media-server too 8 - connect to your Unraid with a filesystem of your choice filezilla / ssh / other 9 - Go to your new plex docker folder > Plex-Media-server > Library > Application support > Plex media server 10 - Get the files LocalAdminToken and Preferences.xml 11 - Erase these 2 files in your Binhex Plex docker and replace them with the new one (backup them in case of)12 - Restart your Binhex Plex instance 13 - Connect from your lan in first instance to be sure that all work 14 - Maybe you will need to repin your library on the side so they can be visible / regive user the authorize to access library (but atleast it work)I hope this will help you and correct the problem like it did for me
September 9, 2025Sep 9 1 hour ago, ohmaxx said:Hey mate i have go the hard and and find a solution (probably not the optimize one but atleast i got my plex back), for the claime variable that's normal she's not include by default on the template but from what i read on plex docker she should so idk. For the solution :1 - shutdown your binhex plex instance2 - Go to the unraid community app and install the Plex-Media-Server from the official source3 - Complete the variable from the Docker template you will have a Claim variable by default so go to the plex.tv/claim and put the code you get4 - Start the new docker, connect through it by ur http://[localip]:32400 (so directly from your network and not from internet)5 - Verify you have the correct access it should ask you too configure your library just bypass this step, go to settings and you should see that your server is available from internet (thats perfect it mean the claim woked)6 - Shutdown the plex-media-server too8 - connect to your Unraid with a filesystem of your choice filezilla / ssh / other9 - Go to your new plex docker folder > Plex-Media-server > Library > Application support > Plex media server10 - Get the files LocalAdminToken and Preferences.xml11 - Erase these 2 files in your Binhex Plex docker and replace them with the new one (backup them in case of)12 - Restart your Binhex Plex instance13 - Connect from your lan in first instance to be sure that all work14 - Maybe you will need to repin your library on the side so they can be visible / regive user the authorize to access library (but atleast it work)I hope this will help you and correct the problem like it did for meThe way you suggested, Thank you for posting BTW, looked like the long way around so I kept look for a shorter path. ;-)I found "https://github.com/uglymagoo/plex-claim-server" in my hunt. I used this and it worked for me. I followed the minimal instructions posted and it worked in my case. I'd like to know why a simple password change causes so much work! Hopefully I'll remember this when it comes up again.Thanks ohmaxx
September 11, 2025Sep 11 On 9/9/2025 at 6:35 PM, RichJacot said:The way you suggested, Thank you for posting BTW, looked like the long way around so I kept look for a shorter path. ;-)I found "https://github.com/uglymagoo/plex-claim-server" in my hunt. I used this and it worked for me. I followed the minimal instructions posted and it worked in my case.I'd like to know why a simple password change causes so much work! Hopefully I'll remember this when it comes up again.Thanks ohmaxxHey RichJacot,Yes as i said it was the long way but i couldnt find another solution so when you dont have the choice you deal with it lol ! I have seen another script when i was looking for a solution it was this one (https://github.com/ChuckPa/UserCredentialReset/) but it didnt work on unraid cli. It's cool that you found another script i will keep it on the side if i need to reclaim another time (it will make me win some time!)For sur thats a real pain to do this password change (was the first time for me), and thanks for your share on solution !
September 20, 2025Sep 20 Just a quick heads up for those who reset their password - After resetting my password and getting my server up and running, found my son could no longer connect as a guest user (he has Library access and has been using my server for several years). We tried a bunch of troubleshooting fixes, and found out if you are using an older release of Plex Server that Plex is blocking remote users (server owner can still connect).Solution is to update to the latest server version - 1.42.1As a follow-up to the original report and in an abundance of caution due to a population of servers still on an affected Plex Media Server version (versions 1.41.7.x to 1.42.0.x), we have made adjustments for access to affected servers. Specifically, other users to which the server owner has granted access to the server will not be able to connect to it while the server is running an affected version. Once the server is updated to a fixed version, other users will be able to access again. Server owners will still be able to access the server as normal.Again, we strongly recommend that everyone have their Plex Media Server updated to the most recent version as soon as possible, if you have not already done so.Source: Plex Media Server - Security Update - Announcements - Plex Forum
October 15, 2025Oct 15 Hello, I recently lost my cache drive and plex db. I deleted the appdata folder and re-downloaded plex. I am now getting this error when I try to start plex server. '--serverUuid' should follow immediately after the equal sign
October 15, 2025Oct 15 52 minutes ago, PrisonMike said:Hello, I recently lost my cache drive and plex db. I deleted the appdata folder and re-downloaded plex. I am now getting this error when I try to start plex server. '--serverUuid' should follow immediately after the equal signNevermind, I cleared my cookies and it worked.
November 7, 2025Nov 7 Hey all,Just wanted to share a fix for a bug that was driving me crazy, in case anyone else is running into it.Any remote 4K HDR stream (like on a Fire Stick) would fail to play, giving a generic error. My 1080p files were fine (and I didn't have any dramas as I run an NVIDIA shield).Logs showed the transcode speed was speed=0.6 (or similar), meaning it was falling back to CPU and choking.Hardware: Unraid server, Nvidia GTX 1080 Ti (Pascal), binhex/arch-plex container.The problem I think is the HDR Tone Mapping feature. The latest Plex version (1.42.2.10156-1-01) seems to have a bug where tone mapping on Pascal cards fails. This causes the entire hardware transcode to crash and fall back to the CPU, which can't handle a 4K transcode.(Disabling tone mapping "worked" but gave washed-out, gray video, which isn't a real fix.)The solution (workaround) was to roll back the container to the previous version.I rolled back from:ghcr.io/binhex/arch-plex:1.42.2.10156-1-01To this stable version:ghcr.io/binhex/arch-plex:1.42.1.10060-1-01After rolling back and re-enabling HDR Tone Mapping, all my 4K HDR transcodes are working perfectly with full hardware acceleration.If you're having 4K transcodes fail on a 10-series card, check your Plex version!Hope this saves someone else the headache
February 10Feb 10 It looks like plex will be supporting battlemage soon do we know when the arch plex distro will be getting this support?
February 11Feb 11 Author 12 hours ago, T_Matz said:It looks like plex will be supporting battlemage soon do we know when the arch plex distro will be getting this support?Arch repo is pretty good at keeping up to date, so as soon as plex release support for it then it will be build and available, do keep in mind though you will need all your ducks in a row for this to work, so you will need to have kernel support for battlemage (unraid issue), driver support (community issue), and finally the plex support (as mentioned).
February 15Feb 15 Thank you for the response and assistance! From my understanding unraid past 7.1 has the Linux kernal to support battlemage and I can see the driver on my system. I'm using it for my immich docker now (Intel top still doesn't show utilization but can confirm ML and transcoding are using the GPU). I appreciate everything you do! It looks like it's not to far away this is the release the Plex team stated it would be released Plex Media Server 1.43.1.10495-10cfae054. Edited February 15Feb 15 by T_Matz
March 13Mar 13 I received an email from Plex stating they are making changes to the repository for updates. The email links to this article.Plex SupportEnable repository updating for supported Linux server dis...We recently migrated to a new repository for distributing Plex Media Server releases that impacts how certain Linux distributions receive...I assume this will be wrapped up in the CA and require no changes on my end?
March 13Mar 13 Author 6 minutes ago, Virtech said:I received an email from Plex stating they are making changes to the repository for updates. The email links to this article.Plex SupportEnable repository updating for supported Linux server dis...We recently migrated to a new repository for distributing Plex Media Server releases that impacts how certain Linux distributions receive...I assume this will be wrapped up in the CA and require no changes on my end?As the email states, if you are using Docker then it's a No-Op, the problem is mine, and possibly it's even a No-Op for me too as i use AUR upstream, so as long as AUR fix any packing issues then we are all good :-)
April 2Apr 2 Getting <Response code="503" title="Maintenance" status="Plex Media Server is currently running database migrations."/>. So Im guessing my Db is corrupted. I cant figure out how to repair it. I tried stopping the container, renaming com.plexapp.plugins.library.db to com.plexapp.plugins.library.db. , starting the container, but still got the same error. The only thing Im really interested in keeping, is my users list. Everything else can be resync'd. Any ideas on how to get this working again?
April 2Apr 2 Author 6 hours ago, Armed Ferret said:Getting <Response code="503" title="Maintenance" status="Plex Media Server is currently running database migrations."/>. So Im guessing my Db is corrupted. I cant figure out how to repair it. I tried stopping the container, renaming com.plexapp.plugins.library.db to com.plexapp.plugins.library.db. , starting the container, but still got the same error. The only thing Im really interested in keeping, is my users list. Everything else can be resync'd. Any ideas on how to get this working again?That doesnt look like corruption to me, that sounds like it's running a database migration, if however you interrupted that by restrting the container then you may well now have a corrupt database, follow Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md
April 11Apr 11 Since the latest update, I've been experiencing codec issues with many movies. They play on Apple devices, but there seem to be problems, especially on Android devices."2026-04-11 10:45:38,090 DEBG 'start-script' stderr output:Jobs: Exec of /config/Plex Media Server/Codecs/EasyAudioEncoder-0dd4de86f2b9bb8b9b397a90-linux-x86_64/EasyAudioEncoder/EasyAudioEncoder failed. (13)"Last edit: Never mind. It worked after I deleted the entire codec folder. I think so Edited April 11Apr 11 by Lethe
April 11Apr 11 5 hours ago, Lethe said:ever mind. It worked after I deleted the entire codec folder. I think soYep. That's the fix. EasyAudioEncoder is the common issue for many of the transcoding issues.
April 11Apr 11 Author 5 hours ago, Lethe said:Last edit: Never mind. It worked after I deleted the entire codec folder. I think sogoing to add this to the faq, as ive seen this issue waaay too many times.
May 2May 2 Updated Unraid to v7.2.5 but noticed my Plex server wasn't running. Tried to start it but got an 'Execution error Server error' message.Here's the log output:text error warn system array login 2026-04-30 03:03:21,435 DEBG 'start-script' stderr output:Plex Media Server is already running. Will not start...2026-04-30 03:03:21,686 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23174436740368 for <Subprocess at 23174436734288 with name start-script in state STARTING> (stdout)>2026-04-30 03:03:21,686 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 23174436463904 for <Subprocess at 23174436734288 with name start-script in state STARTING> (stderr)>2026-04-30 03:03:21,686 WARN exited: start-script (exit status 1; not expected)2026-04-30 03:03:21,687 DEBG received SIGCHLD indicating a child quit2026-04-30 03:03:22,688 INFO spawned: 'start-script' with pid 902026-04-30 03:03:22,699 DEBG 'start-script' stdout output:[info] Env var 'PLEX_CLAIM' value not set and/or 'CLAIM_SERVER' not set to 'yes', skipping edit of Preferences.xml for claim process.2026-04-30 03:03:23,700 INFO success: start-script entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2026-04-30 03:03:35,501 DEBG 'start-script' stdout output:Critical: libusb_init failed2026-05-01 03:02:26,152 WARN received SIGTERM indicating exit request2026-05-01 03:02:26,156 DEBG killing start-script (pid 90) with signal SIGTERM2026-05-01 03:02:26,156 INFO waiting for start-script to die2026-05-01 03:02:29,159 INFO waiting for start-script to die2026-05-01 03:02:32,162 INFO waiting for start-script to die2026-05-01 03:02:35,166 INFO waiting for start-script to die2026-05-01 03:02:36,167 WARN killing 'start-script' (90) with SIGKILL2026-05-01 03:02:36,168 DEBG killing start-script (pid 90) with signal SIGKILL2026-05-01 03:02:37,169 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23174436463904 for <Subprocess at 23174436734288 with name start-script in state STOPPING> (stdout)>2026-05-01 03:02:37,169 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23174436415120 for <Subprocess at 23174436734288 with name start-script in state STOPPING> (stderr)>2026-05-01 03:02:37,170 WARN stopped: start-script (terminated by SIGKILL)2026-05-01 03:02:37,170 DEBG received SIGCHLD indicating a child quitCreated by...___. .__ .__\_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/2026-05-01 03:03:28.511685 [info] Host is running unRAID2026-05-01 03:03:28.545910 [info] System information: Linux Tower 6.12.54-Unraid #1 SMP PREEMPT_DYNAMIC Tue Oct 21 15:58:46 PDT 2025 x86_64 GNU/Linux2026-05-01 03:03:28.581108 [info] Image architecture: 'amd64'2026-05-01 03:03:28.614307 [info] Application name: 'plex'2026-05-01 03:03:28.643253 [info] Base image release tag: '2026032801'2026-05-01 03:03:28.677279 [info] Application image release tag: '1.43.1.10611-1-01'2026-05-01 03:03:28.716213 [info] PUID defined as '99'2026-05-01 03:03:28.749967 [info] User 'nobody' already has UID '99', skipping usermod2026-05-01 03:03:28.799058 [info] PGID defined as '100'2026-05-01 03:03:28.840007 [info] Group 'users' already has GID '100', skipping groupmod2026-05-01 03:03:28.871783 [info] UMASK defined as '000'2026-05-01 03:03:28.922758 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data'2026-05-01 03:03:28.965014 [info] Deleting files in /tmp (non recursive)...2026-05-01 03:03:29.006845 [warn] TRANS_DIR not defined,(via -e TRANS_DIR), defaulting to '/config/tmp'2026-05-01 03:03:29.052007 [info] Starting Supervisor...2026-05-01 03:03:29,231 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing2026-05-01 03:03:29,232 INFO Set uid to user 0 succeeded2026-05-01 03:03:29,236 INFO RPC interface 'supervisor' initialized2026-05-01 03:03:29,237 INFO supervisord started with pid 192026-05-01 03:03:30,240 INFO spawned: 'claim-script' with pid 812026-05-01 03:03:30,242 INFO spawned: 'start-script' with pid 822026-05-01 03:03:30,242 INFO reaped unknown pid 20 (exit status 0)2026-05-01 03:03:30,249 DEBG 'claim-script' stdout output:[info] Env var 'PLEX_CLAIM' value not set and/or 'CLAIM_SERVER' not set to 'yes', skipping claim process.2026-05-01 03:03:30,249 INFO success: claim-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)2026-05-01 03:03:30,249 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 22495311827968 for <Subprocess at 22495313132048 with name claim-script in state RUNNING> (stdout)>2026-05-01 03:03:30,249 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22495311747408 for <Subprocess at 22495313132048 with name claim-script in state RUNNING> (stderr)>2026-05-01 03:03:30,249 INFO exited: claim-script (exit status 0; expected)2026-05-01 03:03:30,250 DEBG received SIGCHLD indicating a child quit2026-05-01 03:03:30,258 DEBG 'start-script' stdout output:[info] Env var 'PLEX_CLAIM' value not set and/or 'CLAIM_SERVER' not set to 'yes', skipping edit of Preferences.xml for claim process.2026-05-01 03:03:31,258 INFO success: start-script entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2026-05-01 03:03:43,238 DEBG 'start-script' stdout output:Critical: libusb_init failed2026-05-01 23:38:05,452 WARN received SIGTERM indicating exit request2026-05-01 23:38:05,469 DEBG killing start-script (pid 82) with signal SIGTERM2026-05-01 23:38:05,469 INFO waiting for start-script to die2026-05-01 23:38:06,129 DEBG 'start-script' stdout output:[info] Waiting for child processes to exit...2026-05-01 23:38:06,130 DEBG 'start-script' stdout output:[info] All child processes exited, exiting while loop...2026-05-01 23:38:06,130 DEBG 'start-script' stdout output:[info] All child processes exited, exiting 'start.sh' script...2026-05-01 23:38:06,130 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 22495311748368 for <Subprocess at 22495311742288 with name start-script in state STOPPING> (stdout)>2026-05-01 23:38:06,131 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 22495311455520 for <Subprocess at 22495311742288 with name start-script in state STOPPING> (stderr)>2026-05-01 23:38:06,131 INFO stopped: start-script (exit status 0)2026-05-01 23:38:06,131 DEBG received SIGCHLD indicating a child quit Press ANY KEY to close this window
May 6May 6 On 5/2/2026 at 11:14 AM, Hitcher said:Updated Unraid to v7.2.5 but noticed my Plex server wasn't running. Tried to start it but got an 'Execution error Server error' message.Here's the log output:text error warn system array login2026-04-30 03:03:21,435 DEBG 'start-script' stderr output:Plex Media Server is already running. Will not start...2026-04-30 03:03:21,686 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23174436740368 for <Subprocess at 23174436734288 with name start-script in state STARTING> (stdout)>2026-04-30 03:03:21,686 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 23174436463904 for <Subprocess at 23174436734288 with name start-script in state STARTING> (stderr)>2026-04-30 03:03:21,686 WARN exited: start-script (exit status 1; not expected)2026-04-30 03:03:21,687 DEBG received SIGCHLD indicating a child quit2026-04-30 03:03:22,688 INFO spawned: 'start-script' with pid 902026-04-30 03:03:22,699 DEBG 'start-script' stdout output:[info] Env var 'PLEX_CLAIM' value not set and/or 'CLAIM_SERVER' not set to 'yes', skipping edit of Preferences.xml for claim process.2026-04-30 03:03:23,700 INFO success: start-script entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2026-04-30 03:03:35,501 DEBG 'start-script' stdout output:Critical: libusb_init failed2026-05-01 03:02:26,152 WARN received SIGTERM indicating exit request2026-05-01 03:02:26,156 DEBG killing start-script (pid 90) with signal SIGTERM2026-05-01 03:02:26,156 INFO waiting for start-script to die2026-05-01 03:02:29,159 INFO waiting for start-script to die2026-05-01 03:02:32,162 INFO waiting for start-script to die2026-05-01 03:02:35,166 INFO waiting for start-script to die2026-05-01 03:02:36,167 WARN killing 'start-script' (90) with SIGKILL2026-05-01 03:02:36,168 DEBG killing start-script (pid 90) with signal SIGKILL2026-05-01 03:02:37,169 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 23174436463904 for <Subprocess at 23174436734288 with name start-script in state STOPPING> (stdout)>2026-05-01 03:02:37,169 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23174436415120 for <Subprocess at 23174436734288 with name start-script in state STOPPING> (stderr)>2026-05-01 03:02:37,170 WARN stopped: start-script (terminated by SIGKILL)2026-05-01 03:02:37,170 DEBG received SIGCHLD indicating a child quitCreated by...___. .__ .__\_ |__ |__| ____ | |__ ____ ___ ___| __ \| |/ \| | \_/ __ \\ \/ /| \_\ \ | | \ Y \ ___/ > <|___ /__|___| /___| /\___ >__/\_ \\/ \/ \/ \/ \/https://hub.docker.com/u/binhex/2026-05-01 03:03:28.511685 [info] Host is running unRAID2026-05-01 03:03:28.545910 [info] System information: Linux Tower 6.12.54-Unraid #1 SMP PREEMPT_DYNAMIC Tue Oct 21 15:58:46 PDT 2025 x86_64 GNU/Linux2026-05-01 03:03:28.581108 [info] Image architecture: 'amd64'2026-05-01 03:03:28.614307 [info] Application name: 'plex'2026-05-01 03:03:28.643253 [info] Base image release tag: '2026032801'2026-05-01 03:03:28.677279 [info] Application image release tag: '1.43.1.10611-1-01'2026-05-01 03:03:28.716213 [info] PUID defined as '99'2026-05-01 03:03:28.749967 [info] User 'nobody' already has UID '99', skipping usermod2026-05-01 03:03:28.799058 [info] PGID defined as '100'2026-05-01 03:03:28.840007 [info] Group 'users' already has GID '100', skipping groupmod2026-05-01 03:03:28.871783 [info] UMASK defined as '000'2026-05-01 03:03:28.922758 [info] Permissions file '/config/perms.txt' exists, skipping setting ownership and permissions on '/config' and '/data'2026-05-01 03:03:28.965014 [info] Deleting files in /tmp (non recursive)...2026-05-01 03:03:29.006845 [warn] TRANS_DIR not defined,(via -e TRANS_DIR), defaulting to '/config/tmp'2026-05-01 03:03:29.052007 [info] Starting Supervisor...2026-05-01 03:03:29,231 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing2026-05-01 03:03:29,232 INFO Set uid to user 0 succeeded2026-05-01 03:03:29,236 INFO RPC interface 'supervisor' initialized2026-05-01 03:03:29,237 INFO supervisord started with pid 192026-05-01 03:03:30,240 INFO spawned: 'claim-script' with pid 812026-05-01 03:03:30,242 INFO spawned: 'start-script' with pid 822026-05-01 03:03:30,242 INFO reaped unknown pid 20 (exit status 0)2026-05-01 03:03:30,249 DEBG 'claim-script' stdout output:[info] Env var 'PLEX_CLAIM' value not set and/or 'CLAIM_SERVER' not set to 'yes', skipping claim process.2026-05-01 03:03:30,249 INFO success: claim-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)2026-05-01 03:03:30,249 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 22495311827968 for <Subprocess at 22495313132048 with name claim-script in state RUNNING> (stdout)>2026-05-01 03:03:30,249 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22495311747408 for <Subprocess at 22495313132048 with name claim-script in state RUNNING> (stderr)>2026-05-01 03:03:30,249 INFO exited: claim-script (exit status 0; expected)2026-05-01 03:03:30,250 DEBG received SIGCHLD indicating a child quit2026-05-01 03:03:30,258 DEBG 'start-script' stdout output:[info] Env var 'PLEX_CLAIM' value not set and/or 'CLAIM_SERVER' not set to 'yes', skipping edit of Preferences.xml for claim process.2026-05-01 03:03:31,258 INFO success: start-script entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2026-05-01 03:03:43,238 DEBG 'start-script' stdout output:Critical: libusb_init failed2026-05-01 23:38:05,452 WARN received SIGTERM indicating exit request2026-05-01 23:38:05,469 DEBG killing start-script (pid 82) with signal SIGTERM2026-05-01 23:38:05,469 INFO waiting for start-script to die2026-05-01 23:38:06,129 DEBG 'start-script' stdout output:[info] Waiting for child processes to exit...2026-05-01 23:38:06,130 DEBG 'start-script' stdout output:[info] All child processes exited, exiting while loop...2026-05-01 23:38:06,130 DEBG 'start-script' stdout output:[info] All child processes exited, exiting 'start.sh' script...2026-05-01 23:38:06,130 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 22495311748368 for <Subprocess at 22495311742288 with name start-script in state STOPPING> (stdout)>2026-05-01 23:38:06,131 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 22495311455520 for <Subprocess at 22495311742288 with name start-script in state STOPPING> (stderr)>2026-05-01 23:38:06,131 INFO stopped: start-script (exit status 0)2026-05-01 23:38:06,131 DEBG received SIGCHLD indicating a child quitPress ANY KEY to close this windowSame issue here. I looked and the only other Docker that wasn't starting was Tdarr. Both of those services relied on my GPU for transcoding, so I checked & those drivers weren't working. Updated the drivers, rebooted, & everything is back up and running.
May 10May 10 I just noticed that recently Plex is no longer showing user data. Any suggestions as to where to start?
May 17May 17 it seems i have lost my port for my plex server i cannot acess the web ui from the docker tab , it is running there are people inside and outside my network on the server currently , but what is the deal ?
May 18May 18 I just updated to Unraid 7.3.0, and I now get the following error when trying to start Plex. The rest of my containers are working.docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error jailing process inside rootfs: open /proc/self/mountinfo: no such file or directoryAny ideas?Thanks!
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.