iD4NG3R Posted August 25, 2022 Share Posted August 25, 2022 (edited) For anyone stuck; tried basically all suggested solutions to no avail. Ended up just doing a CURL from the docker's console: Quote curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=PLEX_CLAIM_TOKEN_GOES_HERE` You can grab the token over @ https://www.plex.tv/claim Unsure if removing the PlexOnlineName, PlexOnlineToken, PlexOnlineEmail and PlexOnlineHome key/value pairs from Preferences.xml is required beforehand, but I had those removed from a previous attempt so. After like 10 seconds a big 'ol wall of text will appear in your console and it should be claimed again. Edited August 25, 2022 by iD4NG3R 2 Quote Link to comment
kzibert Posted August 25, 2022 Share Posted August 25, 2022 1 hour ago, iD4NG3R said: For anyone stuck; tried basically all suggested solutions to no avail. Ended up just doing a CURL from the docker's console: You can grab the token over @ https://www.plex.tv/claim Unsure if removing the PlexOnlineName, PlexOnlineToken, PlexOnlineEmail and PlexOnlineHome key/value pairs from Preferences.xml is required beforehand, but I had those removed from a previous attempt so. After like 10 seconds a big 'ol wall of text will appear in your console and it should be claimed again. Running the curl command worked for me. I did not change anything in the preferences.xml prior to running the curl. Thanks for posting this! Quote Link to comment
SirCadian Posted August 26, 2022 Share Posted August 26, 2022 On 8/25/2022 at 6:30 PM, iD4NG3R said: For anyone stuck; tried basically all suggested solutions to no avail. Ended up just doing a CURL from the docker's console: You can grab the token over @ https://www.plex.tv/claim Unsure if removing the PlexOnlineName, PlexOnlineToken, PlexOnlineEmail and PlexOnlineHome key/value pairs from Preferences.xml is required beforehand, but I had those removed from a previous attempt so. After like 10 seconds a big 'ol wall of text will appear in your console and it should be claimed again. You, Sir, are a god amongst men. Thanks! Quote Link to comment
Jürgen Strobel Posted August 27, 2022 Share Posted August 27, 2022 I have the problem that existing episodes of a series are still recorded with LiveTV DVR. These are then created in the same folder with the same file name and (copy) behind it. Actually, existing episodes should no longer be recorded. Quote Link to comment
enigma27 Posted September 5, 2022 Share Posted September 5, 2022 Hi All. Is there a tutorial on how to repair a corrupt database for this container. Mine randomly started playing up tonight even after watching a movie. really would rather not reinstall the whole thing. Quote Link to comment
SweetChinMusic Posted September 9, 2022 Share Posted September 9, 2022 My Plex setup is getting stuck on scanning my libraries. Any idea how to fix it? Quote Link to comment
Herbiewalker Posted September 10, 2022 Share Posted September 10, 2022 (edited) I was unable to start my plex container (I got an bad parameter error which I think was the nvidia card not being seen by the system so the nvidia setting wasn't allowing it to start). I took those options out and now can start the container. I cannot open the webpage though, so seeing that I am getting an error in my plex logs I restored my appdata from backup but that did not fix the issue. Any ideas on how to fix this issue?? Here is the plex log error which mentions a database but I don't know how to fix that or would the binhex FAQ (Q5. So i see from Q4 that i do have Plex database corruption, how can i attempt to fix this?.) work to fix a malformed disk image? Error: Unable to set up server: sqlite3_statement_backend::loadOne: database disk image is malformed (N4soci10soci_errorE) 2022-09-10 16:36:49,527 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23168105593008 for <Subprocess at 23168106022176 with name plexmediaserver in state RUNNING> (stdout)> 2022-09-10 16:36:49,527 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23168106027696 for <Subprocess at 23168106022176 with name plexmediaserver in state RUNNING> (stderr)> 2022-09-10 16:36:49,528 INFO exited: plexmediaserver (exit status 255; not expected) 2022-09-10 16:36:49,528 DEBG received SIGCHLD indicating a child quit 2022-09-10 16:36:50,532 INFO spawned: 'plexmediaserver' with pid 1597 2022-09-10 16:36:51,535 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-09-10 16:36:53,478 DEBG 'plexmediaserver' stdout output: Error: Unable to set up server: sqlite3_statement_backend::loadOne: database disk image is malformed (N4soci10soci_errorE) 2022-09-10 16:36:53,485 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23168105594112 for <Subprocess at 23168106022176 with name plexmediaserver in state RUNNING> (stdout)> 2022-09-10 16:36:53,486 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23168106027408 for <Subprocess at 23168106022176 with name plexmediaserver in state RUNNING> (stderr)> 2022-09-10 16:36:53,486 INFO exited: plexmediaserver (exit status 255; not expected) 2022-09-10 16:36:53,487 DEBG received SIGCHLD indicating a child quit 2022-09-10 16:36:54,490 INFO spawned: 'plexmediaserver' with pid 1609 2022-09-10 16:36:55,493 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-09-10 16:36:57,426 DEBG 'plexmediaserver' stdout output: Error: Unable to set up server: sqlite3_statement_backend::loadOne: database disk image is malformed (N4soci10soci_errorE) Edited September 10, 2022 by Herbiewalker Quote Link to comment
S3v3nD34dly51ns Posted September 16, 2022 Share Posted September 16, 2022 recently updated my docker container and now it's not able to boot. Getting the following error. Haven't changed anything other than updating it. Is there a way to roll back the update to the prior? Quote Link to comment
gmccall13 Posted September 16, 2022 Share Posted September 16, 2022 I'm also experiencing the same 503 error after my docker container auto-updated. Quote Link to comment
phneutral Posted September 16, 2022 Share Posted September 16, 2022 (edited) 4 hours ago, gmccall13 said: I'm also experiencing the same 503 error after my docker container auto-updated. same here 😞 Ran the CURL mentioned above and eventually got server back Edited September 16, 2022 by phneutral Quote Link to comment
Herbiewalker Posted September 19, 2022 Share Posted September 19, 2022 Hello, I am looking to do a fresh build on unraid and dont want to lose my poster art, collections, and config settings. I would like the Plex container to be as new as possible so what databases should I save to keep those few things? Thanks Quote Link to comment
lockrob2000 Posted September 20, 2022 Share Posted September 20, 2022 On 9/16/2022 at 4:35 AM, phneutral said: same here 😞 Ran the CURL mentioned above and eventually got server back I'm now having the same issue after updating. Is there a way to rollback, or is the "curl" the only way? Quote Link to comment
lockrob2000 Posted September 20, 2022 Share Posted September 20, 2022 Here's the log of the update. I removed the IP from the last line and even though it says login was successful, it was to a the error that was mentioned in previous posts. logs.txt Quote Link to comment
lockrob2000 Posted September 20, 2022 Share Posted September 20, 2022 OK...weird. I shut everything down and came back later and it started up. Sorry- Quote Link to comment
Mizerka Posted September 21, 2022 Share Posted September 21, 2022 had same issue on :latest as well, killed the container, forced update again and it started up fine, it was throwing this before. Critical: libusb_init failed Quote Link to comment
binhex Posted September 21, 2022 Author Share Posted September 21, 2022 19 minutes ago, Mizerka said: Critical: libusb_init failed that can be ignored and is not related:- https://forums.plex.tv/t/critical-libusb-init-failed/722159 Quote Link to comment
Mizerka Posted September 21, 2022 Share Posted September 21, 2022 (edited) cool, and actually spoke too soon, server practically hangs and logs are spamming; 2022-09-21 23:24:54,316 DEBG 'plexmediaserver' stdout output: busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. Sqlite3: Sleeping for 200ms to retry busy DB. enabling verbose on server itself gives off these errors; Held transaction for too long (/data/jenkins/server/3534229725/Library/MetadataItemClustering.cpp:114): 15.620000 seconds CLEAR FILTERS AND JUMP TO CONTEXT and it's spamming those every 10s or so. gonna disable scheduled jobs and restart for now and see if that does anything, maybe do the cleanup jobs from server itself edit; well I let it run for a bit but seems to have hung again, this time with no logs, it's eating up about 0.5cpu and 120mb ram so it's doing something but... not sure, might just leave it overnight. nevermind finished mid sentence, so far... looks okay, will enable scans again and clean up bundles, just doing library scan of a massive one I have, so far it looks okay. Edited September 22, 2022 by Mizerka Quote Link to comment
dallus Posted September 25, 2022 Share Posted September 25, 2022 Thanks for the curl command for claiming the server. I did notice that there are no IPs showing up in the table. Is this ok? I noticed this on the binhex and linuxserver containers. I want to reverse proxy to it like I had before all this got fubarred. Quote Link to comment
Herbiewalker Posted September 27, 2022 Share Posted September 27, 2022 Anyone know what these warnings mean?? Should I be worried about them? 2022-09-27 14:20:07.807171 [info] Host is running unRAID 2022-09-27 14:20:07.891166 [info] System information Linux TwoRivers 5.15.46-Unraid #1 SMP Fri Jun 10 11:08:41 PDT 2022 x86_64 GNU/Linux 2022-09-27 14:20:07.971460 [info] OS_ARCH defined as 'x86-64' 2022-09-27 14:20:08.052278 [info] PUID defined as '99' 2022-09-27 14:20:11.346467 [info] PGID defined as '100' 2022-09-27 14:20:14.628101 [info] UMASK defined as '000' 2022-09-27 14:20:14.683779 [info] Permissions already set for '/config' 2022-09-27 14:20:14.761082 [info] Deleting files in /tmp (non recursive)... 2022-09-27 14:20:14.848771 [info] TRANS_DIR defined as '/transcode' 2022-09-27 14:20:14.985667 [info] Starting Supervisor... 2022-09-27 14:20:19,309 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing 2022-09-27 14:20:19,310 INFO Set uid to user 0 succeeded 2022-09-27 14:20:19,325 INFO supervisord started with pid 7 2022-09-27 14:20:20,329 INFO spawned: 'plexmediaserver' with pid 71 2022-09-27 14:20:20,330 INFO reaped unknown pid 8 (exit status 0) 2022-09-27 14:20:21,331 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-09-27 14:25:16,625 WARN received SIGTERM indicating exit request 2022-09-27 14:25:16,625 DEBG killing plexmediaserver (pid 71) with signal SIGTERM 2022-09-27 14:25:16,626 INFO waiting for plexmediaserver to die 2022-09-27 14:25:19,629 INFO waiting for plexmediaserver to die 2022-09-27 14:25:22,632 INFO waiting for plexmediaserver to die 2022-09-27 14:25:25,635 INFO waiting for plexmediaserver to die 2022-09-27 14:25:26,636 WARN killing 'plexmediaserver' (71) with SIGKILL 2022-09-27 14:25:26,636 DEBG killing plexmediaserver (pid 71) with signal SIGKILL Created by... supervisord.log Quote Link to comment
binhex Posted September 28, 2022 Author Share Posted September 28, 2022 14 hours ago, Herbiewalker said: WARN received SIGTERM indicating exit request this indicates something requested that the process exits, probably due to you shutting down the container, if so there is nothing to worry about. 1 Quote Link to comment
UNcitizenRAID Posted September 29, 2022 Share Posted September 29, 2022 On 9/4/2022 at 8:23 PM, enigma27 said: Hi All. Is there a tutorial on how to repair a corrupt database for this container. Mine randomly started playing up tonight even after watching a movie. really would rather not reinstall the whole thing. same issue with mine , wont start up Quote Link to comment
Zach_peterson4 Posted October 13, 2022 Share Posted October 13, 2022 Hello. I recently got a nvidia gpu to do hardware encode and decode for plex. I saw online that I should switch from the regular binhex docker to the plex pass docker. I set up all the right settings according to what the nvidia driver pluggin says on their page. I have also enabled HW in the plex settings. When testing I noticed that it does not have the "hw" next to the transcode in the dashboard like I have noticed others have when researching online. I can see the transcode folder have been created too. Strangly enough, my CPU gets pinned at 100 percent. Which never happens with anything I do with it. I can guess that plex is using my CPU to do all the lifting when this is happening. I have the text entered in the extra parameters. I have everything for the driver set up. Any help is greatly appreciated. Quote Link to comment
binhex Posted October 13, 2022 Author Share Posted October 13, 2022 9 hours ago, Zach_peterson4 said: I saw online that I should switch from the regular binhex docker to the plex pass docker. not necessary, see here for an explanation of the differences between plex and plex pass:- https://forums.unraid.net/topic/44142-support-binhex-plex-pass/?do=findComment&comment=433841 now onto your issue, you are missing another env var named:- NVIDIA_DRIVER_CAPABILITIES with a value of:- all that should hopefully get it working for you. Quote Link to comment
Zach_peterson4 Posted October 13, 2022 Share Posted October 13, 2022 (edited) 13 hours ago, binhex said: now onto your issue, you are missing another env var named:- NVIDIA_DRIVER_CAPABILITIES with a value of:- all that should hopefully get it working for you. I think I have that. It's right above where I put the gpu ID in my screenshot. I may also be misunderstanding. Edited October 13, 2022 by Zach_peterson4 Quote Link to comment
mgadbois Posted October 18, 2022 Share Posted October 18, 2022 (edited) Plex no longer accessible. Sometime after an upgrade I was told by my family that Plex is no longer accessible. I am not exactly sure when it happened. All I get is a refused error connection when launching from the UnRaid WebUI. Any thoughts? Diagnostics attached. Thanks in advance. Seeing this in logs for the docker. Docker has room.. root@Astro-Server:/lib# df -h /var/lib/docker/ Filesystem Size Used Avail Use% Mounted on /dev/loop2 155G 9.7G 144G 7% /var/lib/docker +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2022-10-18 11:12:55,219 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22871109508048 for <Subprocess at 22871109023440 with name plexmediaserver in state STARTING> (stderr)> Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 109, in emit self.flush() File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 68, in flush self.stream.flush() OSError: [Errno 28] No space left on device 2022-10-18 11:12:55,220 INFO exited: plexmediaserver (exit status 255; not expected) Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 109, in emit self.flush() File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 68, in flush self.stream.flush() OSError: [Errno 28] No space left on device 2022-10-18 11:12:55,220 DEBG received SIGCHLD indicating a child quit Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 109, in emit self.flush() File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 68, in flush self.stream.flush() OSError: [Errno 28] No space left on device 2022-10-18 11:12:56,221 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 109, in emit self.flush() File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 68, in flush self.stream.flush() OSError: [Errno 28] No space left on device astro-server-diagnostics-20221018-1010.zip Edited October 18, 2022 by mgadbois 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.