[Support] binhex - Plex Pass


Recommended Posts

For anyone stuck; tried basically all suggested solutions to no avail. Ended up just doing a CURL from the docker's console:

image.png.bd7f009d094c5c41b5e4bb7bed2b709b.png

 

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 by iD4NG3R
  • Like 2
Link to comment
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:

image.png.bd7f009d094c5c41b5e4bb7bed2b709b.png

 

 

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!

Link to comment
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:

image.png.bd7f009d094c5c41b5e4bb7bed2b709b.png

 

 

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!

Link to comment
  • 2 weeks later...

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 by Herbiewalker
Link to comment

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 by Mizerka
Link to comment

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

Link to comment
  • 2 weeks later...

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.

image.thumb.png.56b572831f03f260af82dc6f077076a5.png

 

I have everything for the driver set up.

image.thumb.png.27828f86197d8ebb4bcb0003b90f08a0.png

 

Any help is greatly appreciated.

Link to comment
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.

Link to comment
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 by Zach_peterson4
Link to comment

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 by mgadbois
Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.