[Support] binhex - Plex Pass


1107 posts in this topic Last Reply

Recommended Posts

Separate question to the above.  I have now realized there are 5 different docker containers for Plex and I don't see much explanation of why one would be different over the others, except for who maintains the docker.  

 

Very simply, is there any real difference between them?  If I was going to migrate (to Binhex) Can I install the new docker and will it point to the same Plex database?  IE can I keep both set up and just change which one "auto-starts" with unRAID until I confirm it's all up and running correctly?   If not what would the process be?  I have a rather large media collection with quite a bit of custom tweaking of the database, IE how movies are organized.  Starting over would be extraordinarily painful.

 

Thanks again.

Link to post
  • Replies 1.1k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

its currently queued to build, you should see a new image available in the next hour or two that should get things back on track.  

just change your repository to "binhex/arch-plexpass:1.12.0.4829-1-01" without the quotes. you can do this with any repositories, just add a colon and then the specific tag you want to use. 

Be patient young Jedi everything comes to those who wait, it's automated, as soon as it can be built it will be built. Sent from my EML-L29 using Tapatalk

Posted Images

On 6/19/2019 at 8:53 AM, ProZac said:

Nothing silly at all what you did, the database bug is new to most people in this latest Unraid update, just be aware, some people have had their database wiped by changing the mapping, but as it's just to rebuild and wait (and ur's don't work anyway), I would still try to change it :)

 

I am not running the appdata in /cache, I'm still using /user on all with no issues. From the looks of all the other posts around the forum there is some incompatibility either with specific hardware or some weird sw bug nobody have been able to find so far that creates the issue.

Circling back on this thread:
Changing the path for plex to /mnt/cache/appdata/binhex-plexpass helped me not have the errors from Plex that I was encountering. The issue now is that if the server is restarted, or the cache is cleared for whatever reason, then there will be a fresh setup of plex every time. Is there a way to get around this? Maybe changing it back to /mnt/user/appdata/Plex but have it set to a specific disk (Ex: /mnt/disk1/appdata/binhex-plexpass/)?
I am not sure if this will result me in having the same issue or if this will fix it

Thank you in advance!

Link to post
30 minutes ago, Marimuria said:

Changing the path for plex to /mnt/cache/appdata/binhex-plexpass helped me not have the errors from Plex that I was encountering. The issue now is that if the server is restarted, or the cache is cleared for whatever reason

/mnt/cache is your cache drive or pool. If you don't have one assigned, then that location is in RAM. You must actually HAVE a cache drive assigned for that to work properly.

Link to post
36 minutes ago, jonathanm said:

You must actually HAVE a cache drive assigned for that to work properly.

 

43 minutes ago, Rick Gillyon said:

Just set your appdata share to use cache, then mover will move it.

It looks like the only option that I have to use the binhex plex docker is to have it in the cache. I do not currently have a cache drive (I am currently trying to free one up to use to get plex running as its primarily what I use the server for). But, is having a dedicated cache drive going to present me with the same issues as using ram? Do I need to use some mover function shenanigans to have the Plex server not be re-created each time I cycle the server or if the server decides to randomly clear the cache or is this something that does not happen with a dedicated drive?

Link to post
14 hours ago, Rick Gillyon said:

Just set your appdata share to use cache, then mover will move it.

There are 4 different possible settings for use cache, only 2 of those settings will invoke mover, and only one of them will result in moving files TO cache. Also, mover can't move open files so just setting something to cache-prefer (the one that will move TO cache) may not be enough to get it done. Disable docker service, or at least stop the particular container, then run mover after setting it to cache-prefer.

 

13 hours ago, Rick Gillyon said:

It does not happen with a cache drive, mover will just do the initial move then it's there for good.

And only 2 of the 4 settings for use cache will result in files staying on cache.

 

See this FAQ for more details about the use cache settings:

 

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#comment-537383

 

Link to post
2 hours ago, djgizmo said:

I'm having an odd issue wi th this specific docker where the WebUI menu option doesn't show un Unraid.  All the other BinHex dockers show it just fine.  Any suggestions?

Some log files would be needed to investigate this. Fresh supervisor log file as minimum, maybe run command? :)
Where to find the supervisor log file is located on the first post of the thread, and the run command can be described in the first link 

https://forums.unraid.net/topic/57181-real-docker-faq/

 

Link to post
8 hours ago, trurl said:

And only 2 of the 4 settings for use cache will result in files staying on cache.

If I am reading the forum correctly. Cache only and Cache prefer are the cache options to keep the data on the cache drive. I think having the added ability to 'overflow' cached data on a drive with Cache prefer, I think this would be a better option for my use case. Thank you for the help

Link to post
18 hours ago, Marimuria said:

Some log files would be needed to investigate this. Fresh supervisor log file as minimum, maybe run command? :)
Where to find the supervisor log file is located on the first post of the thread, and the run command can be described in the first link 

https://forums.unraid.net/topic/57181-real-docker-faq/

 

 

I'm unsure if I'm being clear.... attached is a screen shot what I mean.  Plex works just fine and I can login to it just fine with the IP address... however the menu for this is missing in Unraid. 

 

plexwebuimissing001.png

Edited by djgizmo
Link to post
2 minutes ago, djgizmo said:

 

I'm unsure if I'm being clear.... attached is a screen shot what I mean.  Plex works just fine and I can login to it just fine with the IP address... however the menu for this is missing in Unraid. 

 

plexwebuimissing001.png

That comes from the template too. Click Edit then post a screenshot of the Update Container page on Advanced View.

Link to post
2 hours ago, trurl said:

That looks OK. Don't know. Is it having that problem on both the Docker page and the Dashboard?

yep.   It's odd.   I have 3 dockers that do this.  out of 25.   No error in logs.  Feels like a configuration issue... but no clue what. 

Edited by djgizmo
spelling
Link to post

Hey my Plex was running just fine for a few days, I was watching a TV show, then when it went to the next TV show it wouldn't connect. I restarted and I haven't been able to get it since. Here's the log:

 

Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2019-06-22 14:09:36.317454 [info] System information Linux Dataserver2 4.19.41-Unraid #1 SMP Wed May 8 14:23:25 PDT 2019 x86_64 GNU/Linux
2019-06-22 14:09:36.352690 [info] PUID defined as '99'
2019-06-22 14:09:36.391451 [info] PGID defined as '100'
2019-06-22 14:09:37.293855 [info] UMASK defined as '000'
2019-06-22 14:09:37.330049 [info] Permissions already set for volume mappings
2019-06-22 14:09:37.365713 [info] TRANS_DIR defined as '/config/transcode'
2019-06-22 14:09:37.402208 [info] Starting Supervisor...
2019-06-22 14:09:37,650 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2019-06-22 14:09:37,650 INFO Set uid to user 0 succeeded
2019-06-22 14:09:37,653 INFO supervisord started with pid 6
2019-06-22 14:09:38,657 INFO spawned: 'plexmediaserver' with pid 47
2019-06-22 14:09:38,657 INFO reaped unknown pid 7
2019-06-22 14:09:38,828 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23026837312120 for <Subprocess at 23026837312232 with name plexmediaserver in state STARTING> (stdout)>
2019-06-22 14:09:38,828 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23026837389384 for <Subprocess at 23026837312232 with name plexmediaserver in state STARTING> (stderr)>
2019-06-22 14:09:38,828 INFO exited: plexmediaserver (exit status 255; not expected)
2019-06-22 14:09:38,828 DEBG received SIGCHLD indicating a child quit
2019-06-22 14:09:39,831 INFO spawned: 'plexmediaserver' with pid 52
2019-06-22 14:09:40,115 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23026837253704 for <Subprocess at 23026837312232 with name plexmediaserver in state STARTING> (stdout)>
2019-06-22 14:09:40,115 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23026837390280 for <Subprocess at 23026837312232 with name plexmediaserver in state STARTING> (stderr)>
2019-06-22 14:09:40,115 INFO exited: plexmediaserver (exit status 255; not expected)
2019-06-22 14:09:40,115 DEBG received SIGCHLD indicating a child quit
2019-06-22 14:09:42,119 INFO spawned: 'plexmediaserver' with pid 57
2019-06-22 14:09:42,385 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23026837389384 for <Subprocess at 23026837312232 with name plexmediaserver in state STARTING> (stdout)>
2019-06-22 14:09:42,385 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23026837312288 for <Subprocess at 23026837312232 with name plexmediaserver in state STARTING> (stderr)>
2019-06-22 14:09:42,385 INFO exited: plexmediaserver (exit status 255; not expected)
2019-06-22 14:09:42,385 DEBG received SIGCHLD indicating a child quit
2019-06-22 14:09:45,391 INFO spawned: 'plexmediaserver' with pid 62
2019-06-22 14:09:45,658 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23026837389552 for <Subprocess at 23026837312232 with name plexmediaserver in state STARTING> (stdout)>
2019-06-22 14:09:45,658 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23026837390336 for <Subprocess at 23026837312232 with name plexmediaserver in state STARTING> (stderr)>
2019-06-22 14:09:45,658 INFO exited: plexmediaserver (exit status 255; not expected)
2019-06-22 14:09:45,659 DEBG received SIGCHLD indicating a child quit
2019-06-22 14:09:46,660 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly

Here are my settings:

 

image.thumb.png.25c3c49feb0aad4e5f6e16aac97b7b87.png

 

 

And here is the command:

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-plexpass' --net='host' --log-opt max-size='50m' --log-opt max-file='1' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'TRANS_DIR'='/config/transcode' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/':'/media':'rw' -v '/mnt/user/Media/Movies':'/Movies/':'rw' -v '/mnt/user/Media/TV Shows':'/TV Shows/':'rw' -v '/mnt/user/Media/Music':'/Music/':'rw' -v '/mnt/user/appdata/binhex-plexpass':'/config':'rw' 'binhex/arch-plexpass' 

96c0c216355dedaed1c10782643d6c17709de24562a69681a48d371a61320c8f

The command finished successfully!

 

Thanks for any help in advance!

 

Link to post
On 6/21/2019 at 7:28 AM, djgizmo said:

I'm having an odd issue wi th this specific docker where the WebUI menu option doesn't show un Unraid.  All the other BinHex dockers show it just fine.  Any suggestions?

I'm working through the same problem.  This started after the upgrade to 6.7.0 for me.  I have 35 Docker containers on my list and about 5 of them no longer show the WebUI link in the drop down where they did before.  Their Webui field in advance settings is defined and I've tried setting it to the actual link as well as using the http://[IP]:[PORT:8083]/  to no avail.  Can't see anything in syslog or the Docker log that is complaining.

Link to post
11 hours ago, socono said:

I'm working through the same problem.  This started after the upgrade to 6.7.0 for me.  I have 35 Docker containers on my list and about 5 of them no longer show the WebUI link in the drop down where they did before.  Their Webui field in advance settings is defined and I've tried setting it to the actual link as well as using the http://[IP]:[PORT:8083]/  to no avail.  Can't see anything in syslog or the Docker log that is complaining.

misery loves company.   glad its not just me. 

Edited by djgizmo
Link to post

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.