HellraiserOSU Posted May 18, 2022 Share Posted May 18, 2022 After upgrading to 6.10 I'm getting this error when trying to start: docker: Error response from daemon: error gathering device information while adding custom device "/dev/dri": no such file or directory. Does anyone have a solution? 2 Quote Link to comment
veri745 Posted June 1, 2022 Share Posted June 1, 2022 I am getting an looping error after upgrading to Unraid 6.10.2 from 6.9.3 2022-06-01 12:31:09,328 INFO spawned: 'plexmediaserver' with pid 70 2022-06-01 12:31:09,350 DEBG 'plexmediaserver' stderr output: PMS: failure detected. Read/write access is required for path: /config/Plex Media Server 2022-06-01 12:31:09,351 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22716828494304 for <Subprocess at 22716828488832 with name plexmediaserver in state STARTING> (stdout)> 2022-06-01 12:31:09,351 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 22716828494352 for <Subprocess at 22716828488832 with name plexmediaserver in state STARTING> (stderr)> 2022-06-01 12:31:09,351 INFO exited: plexmediaserver (exit status 1; not expected) 2022-06-01 12:31:09,351 DEBG received SIGCHLD indicating a child quit Anyone seen this or have an idea how to address it? I've tried restarting the docker image several times Quote Link to comment
veri745 Posted June 1, 2022 Share Posted June 1, 2022 (edited) 8 hours ago, veri745 said: I am getting an looping error after upgrading to Unraid 6.10.2 from 6.9.3 2022-06-01 12:31:09,328 INFO spawned: 'plexmediaserver' with pid 70 2022-06-01 12:31:09,350 DEBG 'plexmediaserver' stderr output: PMS: failure detected. Read/write access is required for path: /config/Plex Media Server 2022-06-01 12:31:09,351 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22716828494304 for <Subprocess at 22716828488832 with name plexmediaserver in state STARTING> (stdout)> 2022-06-01 12:31:09,351 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 22716828494352 for <Subprocess at 22716828488832 with name plexmediaserver in state STARTING> (stderr)> 2022-06-01 12:31:09,351 INFO exited: plexmediaserver (exit status 1; not expected) 2022-06-01 12:31:09,351 DEBG received SIGCHLD indicating a child quit Anyone seen this or have an idea how to address it? I've tried restarting the docker image several times So "Fix Common Problems" didn't report anything after an extended scan, but upon further investigation I noticed that /mnt/user/appdata/binhex-plex/ was showing the owner as `UNKNOWN` I recursively set the owner to `nobody`, and that resolved the issue. Edited June 2, 2022 by veri745 typo Quote Link to comment
akaNorman Posted June 7, 2022 Share Posted June 7, 2022 I can't seem to upgrade past a certain point without my entire Plex breaking. I am currently on: :1.25.9.5721-1-01 Whenever I go past this point my library just says "home page broken check back in a few minutes" and nothing is available. I've read online there was some database migration in the background of this that could take some time for larger libraries and I assume I'm on the ~larger~ side with a 213TB library (76,000 episodes, 5600 movies) but after upgrading and leaving it to sit overnight I assume something is broken. I can downgrade back to the above version and it's fine. I've tried a fresh install as per spadeinvaderone's suggestions of copying the Library DB over but I assume whatever is broken is carrying over. Would rather fix my issue while I still have a working Plex instance than let it sit too long Happy to provide any logs that would help I just don't know how or what to supply Quote Link to comment
jeffro Posted June 7, 2022 Share Posted June 7, 2022 On 6/1/2022 at 10:53 AM, veri745 said: So "Fix Common Problems" didn't report anything after an extended scan, but upon further investigation I noticed that /mnt/user/appdata/binhex-plex/ was showing the owner as `UNKNOWN` I recursively set the owner to `nobody`, and that resolved the issue. I can confirm that I had the same issue as @veri745 and their recommended fix above corrected the issue with Plex starting up. This happened right after upgrading Unraid from 6.9.3 to 6.10.2 for me. Thank you @veri745! Full command for anyone interested user@host: /mnt/user/appdata/plex# chown -R nobody:root Plex\ Media\ Server/ 1 Quote Link to comment
Adiventure Posted June 14, 2022 Share Posted June 14, 2022 Struggling a bit with setup and hoping someone might be able to help. I'm pretty new to Plex, having used Emby for a long time, and picking up a license on sale. I've had Emby set-up with SWAG for a while, and figured I'd try setting up Plex that way as well. It's working insofar as my url is hitting Plex and I'm able to login to my user, but I'm not able to actually setup the server at all. If I go to webui I get about:blank#blocked in the address bar. I'm not quite sure what to make of that, clearly the swag side is working, but something is presumably wrong in my Plex setup. Plex is running on my swag network. No other settings have been fudged with. I do note that Plex isn't showing any port mappings on the docker page, I'm not sure if that's right or not. Quote Link to comment
Liqwid_Kirk Posted June 23, 2022 Share Posted June 23, 2022 Hello everyone, A little while ago I started getting this error Quote 2022-06-23 08:52:25,560 DEBG 'plexmediaserver' stdout output: Critical: libusb_init failed Pretty sure it started right after I updated to 6.10.2. Anyone else have this issue? Quote Link to comment
binhex Posted June 23, 2022 Author Share Posted June 23, 2022 11 minutes ago, Liqwid_Kirk said: Hello everyone, A little while ago I started getting this error Pretty sure it started right after I updated to 6.10.2. Anyone else have this issue? https://forums.plex.tv/t/critical-libusb-init-failed/722159 Quote Link to comment
Liqwid_Kirk Posted June 23, 2022 Share Posted June 23, 2022 1 hour ago, binhex said: https://forums.plex.tv/t/critical-libusb-init-failed/722159 I guess I should have said that I can no longer access the webUI as well and none of my clients can access the servewr anymore either. That was my bad, sorry about that. Quote Link to comment
binhex Posted June 23, 2022 Author Share Posted June 23, 2022 16 minutes ago, Liqwid_Kirk said: I guess I should have said that I can no longer access the webUI as well and none of my clients can access the servewr anymore either. That was my bad, sorry about that. have a look at Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md Quote Link to comment
likesboc Posted June 25, 2022 Share Posted June 25, 2022 what do i need to do to make use of the new "unraid built in wireguard"? i have been running your plex server in host mode for a long time, it answers on my unraid's ip adress at port 32400. when i switch from host mode to the wg0 tunnel the plex website becomes unresponsive. i have a "vpn tunneled access for docker" tunnel active to hide the plex server behind it. i guess i have to use a different ip locally? but how do i set it? i tried figuring out the ip it receives per console, but the adress it gets (a private 172 adress) isn't responsive either. i'm thankful for any hints! Quote Link to comment
JustOverride Posted June 28, 2022 Share Posted June 28, 2022 On 3/23/2020 at 5:31 AM, binhex said: that is a volume mapping NOT an environment variable, you need to define the volume mapping AND set the value for TRANS_DIR to the volume mapping you defined, see Q1 from the link below for explanation:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md On 3/23/2020 at 8:57 AM, djgizmo said: Thank you for the link.... However the FAQ (and when I searched for the question in this thread) says to set the value for TRANS_DIR but does not say how to set this value. Is this just a custom variable (key/value) in the container configuration in Unraid? I'm not trying to be difficult, just want some clarification as it's not described anywhere in the thread or the FAQ. Wow same here. Thanks for everything, but please add that link to the top post. Quote Link to comment
raf7913 Posted July 8, 2022 Share Posted July 8, 2022 getting a message "Error response from daemon: Unknown runtime specified nvidia." after upgrading to the latest plexpass release. Anyone know whats up? Quote Link to comment
mc_handler Posted July 23, 2022 Share Posted July 23, 2022 Sorry to bother the community but after many attempts to find the solution online I am seriously struggling to get access to Plex again. I did an update tonight of the docker and now I can't gain access locally or remotely. When I try to access the WebGUI it tells me the site can't be reached. I have deleted and reinstalled the docker. I got rid of the perms.txt but UnRAID is not rebuilding it after a reboot. I've also tried numerous older builds of the docker and none of those seem to work. I'm on UnRAID 6.8.3. Any help would be appreciated. I'm happy to upload Logs but there seem to be so many and I'm not sure exactly which one to post here. Quote Link to comment
CMGSV Posted July 23, 2022 Share Posted July 23, 2022 Every time I try to setup this docker for - -runtime=Nvidia it fails. Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-plexpass' --net='host' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="CMGSV001" -e HOST_CONTAINERNAME="binhex-plexpass" -e 'TRANS_DIR'='/config/transcode' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-4ea5d6ac-1f77-4a47-fdba-58a577198f60' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:32400]/web/index.html' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/plex-icon.png' -v '/mnt/user/CMGSV_001_Plex/Media/':'/media':'rw' -v '/mnt/user/appdata/binhex-plexpass':'/config':'rw' --runtime=nvidia 'binhex/arch-plexpass' docker: Error response from daemon: Unknown runtime specified nvidia. See 'docker run --help'. The command failed. everything is updated….it use to work Quote Link to comment
amateur_wizard Posted July 24, 2022 Share Posted July 24, 2022 [Solved] Missing X-Plex-container-Size header. This will fail with status code 400 in the future. Found an issue may not have been the only issue that was causing problems. Network sharing the appdata share messes with the permissions of the files for the sake of SMB & NFS. Turning it off has removed 90% of this log jam. Quote Link to comment
Yimm Posted July 24, 2022 Share Posted July 24, 2022 (edited) On 5/18/2022 at 9:57 PM, HellraiserOSU said: After upgrading to 6.10 I'm getting this error when trying to start: docker: Error response from daemon: error gathering device information while adding custom device "/dev/dri": no such file or directory. Does anyone have a solution? Hey @HellraiserOSU not sure if you're still having this issue but I also upgraded to 6.10 and had this issue. I found out that I was using --device=/dev/dri instead of --device=/dev/dri:/dev/dri in the extra parameters. Once I changed this it started working again. Edited July 24, 2022 by Yimm Quote Link to comment
knightrider15 Posted July 27, 2022 Share Posted July 27, 2022 On 7/23/2022 at 12:19 AM, CMGSV said: Every time I try to setup this docker for - -runtime=Nvidia it fails. Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-plexpass' --net='host' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e HOST_HOSTNAME="CMGSV001" -e HOST_CONTAINERNAME="binhex-plexpass" -e 'TRANS_DIR'='/config/transcode' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'NVIDIA_VISIBLE_DEVICES'='GPU-4ea5d6ac-1f77-4a47-fdba-58a577198f60' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:32400]/web/index.html' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/plex-icon.png' -v '/mnt/user/CMGSV_001_Plex/Media/':'/media':'rw' -v '/mnt/user/appdata/binhex-plexpass':'/config':'rw' --runtime=nvidia 'binhex/arch-plexpass' docker: Error response from daemon: Unknown runtime specified nvidia. See 'docker run --help'. The command failed. everything is updated….it use to work did you ever figure this out? im in the same boat Quote Link to comment
TrueImpulse Posted July 28, 2022 Share Posted July 28, 2022 (edited) On 7/27/2022 at 1:58 PM, knightrider15 said: did you ever figure this out? im in the same boat I'm also having the same issue. Edit: Updating Unraid to 6.10 solved the issue Edited July 31, 2022 by TrueImpulse Quote Link to comment
Rweng009 Posted August 3, 2022 Share Posted August 3, 2022 Plex working fine this morning - Just updated to the latest version and now dont have a media server. Plex opens - the library list is there but no content (apart from Plex online stuff) "Something went wrong An unexpected error occurred" Had the same error when updating my Synology last week to 1.28 which never got resolved - now both it and my unraid plex dont work. Any ideas?? Server logs attached. Plex Media Server Logs_2022-08-03_19-38-11.zip Quote Link to comment
binhex Posted August 3, 2022 Author Share Posted August 3, 2022 1 hour ago, Rweng009 said: Plex working fine this morning - Just updated to the latest version and now dont have a media server. Plex opens - the library list is there but no content (apart from Plex online stuff) "Something went wrong An unexpected error occurred" Had the same error when updating my Synology last week to 1.28 which never got resolved - now both it and my unraid plex dont work. Any ideas?? Server logs attached. Plex Media Server Logs_2022-08-03_19-38-11.zip 3.33 MB · 0 downloads from your logs:- Aug 03, 2022 15:34:25.816 [0x14bb95686380] INFO - Analyzing database. Aug 03, 2022 15:34:26.860 [0x14bb95686380] ERROR - SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5] Aug 03, 2022 15:34:26.860 [0x14bb95686380] ERROR - SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5] Aug 03, 2022 15:34:26.860 [0x14bb95686380] ERROR - SQLITE3:0x80000001, 11, statement aborts at 3072: [ANALYZE] database disk image is malformed Aug 03, 2022 15:34:26.864 [0x14bb95686380] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::loadOne: database disk image is malformed see q5:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md Quote Link to comment
Jacon Posted August 3, 2022 Share Posted August 3, 2022 @binhex@SloppyG@thatsthefrickenlightning any updates on iGPU Intel transcoding? i recently moved to a Haswell Xeon with quicksync. Drivers are installed but would really like to keep Binhex container instead of moving to linux container Quote Link to comment
SloppyG Posted August 4, 2022 Share Posted August 4, 2022 57 minutes ago, Jacon said: @binhex@SloppyG@thatsthefrickenlightning any updates on iGPU Intel transcoding? i recently moved to a Haswell Xeon with quicksync. Drivers are installed but would really like to keep Binhex container instead of moving to linux container I haven't used the BH plex container in a while but I still see occasional posts on Reddit with people reporting issues with intel gpu offloading. Gpu offloading does work on the binhex container but if you need 4K/hdr tone remapping and are using an intel igpu you'll probably still need to swap to the linuxserver container to fully take advantage of it. You can always just install it alongside and compare. 1 Quote Link to comment
paperblankets Posted August 16, 2022 Share Posted August 16, 2022 (edited) Hey @binhex (or anyone else), do you have a recommended way to stop the plex service inside the container for maintenance? According to this thread linuxio containers have some shell scripts baked in to handle it. MiB Mem : 32016.9 total, 3851.5 free, 7303.9 used, 20861.4 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 22613.4 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 81 nobody 35 15 64504 44196 9884 S 0.3 0.1 0:03.03 Plex Script Host 64 nobody 20 0 224 4 0 S 0.0 0.0 0:00.00 start.sh 65 nobody 20 0 112784 63856 37464 S 0.0 0.2 0:02.55 Plex Media Server 123 nobody 20 0 40176 11508 10096 S 0.0 0.0 0:00.19 Plex Tuner Server 180 nobody 20 0 109852 89760 10712 S 0.0 0.3 0:06.29 Plex Script Host 182 nobody 20 0 86324 62296 11448 S 0.0 0.2 0:03.14 Plex Script Host 185 nobody 20 0 66720 46852 10096 S 0.0 0.1 0:03.66 Plex Script Host 290 nobody 20 0 4316 3364 2848 S 0.0 0.0 0:00.01 Plex Relay 331 nobody 20 0 63192 43300 9908 S 0.0 0.1 0:01.87 Plex Script Host ... I'm sure I could just pkill -9 all these pids, but there is likely a better way than that right? Edit: For anyone following along `kill <pid of start.sh>` seems to have taken down the other plex services, the script may have an exit hook that takes those things down. I may check later. I'm a little worried supervisord might bring it all back up mid maintenance of database... Edited August 16, 2022 by paperblankets Quote Link to comment
Keith Ellis Posted August 24, 2022 Share Posted August 24, 2022 On 10/10/2021 at 8:54 AM, binhex said: Ignore that message it is not critical and is caused by a bug in plex, check your Plex log, probably database corruption would be my first thought as this is quite common Sent from my CLT-L09 using Tapatalk EDIT - just to expand on this now im not on my phone, see Q4 and Q5:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md Hello, I’m also getting the following message Critial: libusb_init failed I have checked question 4 and 5 linked above. the only error messages I can see are: root@Tower:/mnt/user/appdata/binhex-plex/Plex Media Server/Logs# cat Plex\ Media\ Server.log |grep error Aug 24, 2022 16:18:30.111 [0x1481f4dbeb00] WARN - NAT: PMP, got an error: Not Supported by gateway. ‘fatal’ and ‘corruption’ do not appear in the log. my Plex server is not starting. It was been working for a couple of years, but stopped about a week ago. Any idea how I ca; fix this? 1 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.