[Support] binhex - Plex Pass


Recommended Posts

1 minute ago, cogliostro said:

Okay, but when this is all true, why my plex works, but plex pass did not? When they both based on the same kind of problem.. 

its not specific to the version of plex, in time 'plex' database may well corrupt too, keep in mind it seems to happen randomly

Link to comment

Hi, I've been using binhex docker images for a while thanks to Spaceinvader's videos! I've been having issue with binhex-plexpass where the webui is never accessible so I've been managing my plex through app.plex.tv but its very annoying as I use OrganizrV2 and its not manageable from there. I've tried to remove the "perms.txt" file as I found on google that people facing similar issue have permission issue, but that didn't work. Please let me know if I need to provide more information!

Link to comment

I managed to get my plexpass up and running again. I logged in to the console with putty and delete the app while it was installed in my appdata folder. Then i removed the app manual in the dashboard. Then i checked my appdata/binhex-plexpass folder again to be sure everything is gone. Then i reinstalled the binhex-plexpass again. And everything worked again properly. You will have to recreate your plex index i mean the media inside the database. I hope this will maybe help others getting theyr plex up and running again. Thanks @binhex for his support.

 

You will have to login as root then rm -r /mnt/user/appdata/binhex-plexpass to delete the folder. After that you can try to install again.

For me this worked.

Edited by cogliostro
Link to comment
4 hours ago, cogliostro said:

I managed to get my plexpass up and running again. I logged in to the console with putty and delete the app while it was installed in my appdata folder. Then i removed the app manual in the dashboard. Then i checked my appdata/binhex-plexpass folder again to be sure everything is gone. Then i reinstalled the binhex-plexpass again. And everything worked again properly. You will have to recreate your plex index i mean the media inside the database. I hope this will maybe help others getting theyr plex up and running again. Thanks @binhex for his support.

Hey @cogliostro thanks for the response! Does your approach imply that I need to re-create the library inside plex and re-add the people who have access to the library? If so, is there a workaround?

Link to comment

Sorry if this isn't the place to post this. Let me know where I should post it if this is wrong.

 

Running into the FATAL error, but it doesn't seem to be permission based.

*** Start Log ***

 

2019-09-19 10:05:27.541841 [info] System information Linux MediaMonster 4.19.56-Unraid #1 SMP Tue Jun 25 10:19:34 PDT 2019 x86_64 GNU/Linux
2019-09-19 10:05:27.586466 [info] PUID defined as '99'
2019-09-19 10:05:27.795364 [info] PGID defined as '100'
2019-09-19 10:05:28.076972 [info] UMASK defined as '000'
2019-09-19 10:05:28.120205 [info] Permissions already set for volume mappings
2019-09-19 10:05:28.161932 [info] TRANS_DIR defined as '/config/transcode'
2019-09-19 10:05:28.383057 [info] Starting Supervisor...
2019-09-19 10:05:28,701 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2019-09-19 10:05:28,701 INFO Set uid to user 0 succeeded
2019-09-19 10:05:28,706 INFO supervisord started with pid 6
2019-09-19 10:05:29,708 INFO spawned: 'plexmediaserver' with pid 53
2019-09-19 10:05:29,709 INFO reaped unknown pid 7
2019-09-19 10:05:30,357 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22921431306928 for <Subprocess at 22921431307040 with name plexmediaserver in state STARTING> (stdout)>
2019-09-19 10:05:30,358 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22921431388344 for <Subprocess at 22921431307040 with name plexmediaserver in state STARTING> (stderr)>
2019-09-19 10:05:30,358 INFO exited: plexmediaserver (exit status 255; not expected)
2019-09-19 10:05:30,359 DEBG received SIGCHLD indicating a child quit
2019-09-19 10:05:31,362 INFO spawned: 'plexmediaserver' with pid 58
2019-09-19 10:05:31,482 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22921431389240 for <Subprocess at 22921431307040 with name plexmediaserver in state STARTING> (stdout)>
2019-09-19 10:05:31,482 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22921431307096 for <Subprocess at 22921431307040 with name plexmediaserver in state STARTING> (stderr)>
2019-09-19 10:05:31,482 INFO exited: plexmediaserver (exit status 255; not expected)
2019-09-19 10:05:31,483 DEBG received SIGCHLD indicating a child quit
2019-09-19 10:05:33,487 INFO spawned: 'plexmediaserver' with pid 63
2019-09-19 10:05:33,605 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22921431389240 for <Subprocess at 22921431307040 with name plexmediaserver in state STARTING> (stdout)>
2019-09-19 10:05:33,605 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22921431388456 for <Subprocess at 22921431307040 with name plexmediaserver in state STARTING> (stderr)>
2019-09-19 10:05:33,606 INFO exited: plexmediaserver (exit status 255; not expected)
2019-09-19 10:05:33,606 DEBG received SIGCHLD indicating a child quit
2019-09-19 10:05:36,611 INFO spawned: 'plexmediaserver' with pid 68
2019-09-19 10:05:36,734 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22921431388344 for <Subprocess at 22921431307040 with name plexmediaserver in state STARTING> (stdout)>
2019-09-19 10:05:36,735 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22921431306928 for <Subprocess at 22921431307040 with name plexmediaserver in state STARTING> (stderr)>
2019-09-19 10:05:36,735 INFO exited: plexmediaserver (exit status 255; not expected)
2019-09-19 10:05:36,735 DEBG received SIGCHLD indicating a child quit
2019-09-19 10:05:37,737 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly

 

*** End Log ***

 

Reading about others that have had this error, it seems it should be permission issues. I've used the console to check folder permissions and everything I can find is either "nobody" or "root" in both the "/mnt/user" (directory and sub directories) and "/mnt/cache" (directory and sub directories). 

 

Plex will not launch in the UI, and today is the first time I've had issues with it. Anyone have a suggestion other than "Delete the Docker and reinstall binhex-plexpass to see if that works?" 

 

Please let me know if you want any more information.

 

Thanks!

Link to comment
19 hours ago, PiMan314159265 said:

Sorry if this isn't the place to post this. Let me know where I should post it if this is wrong.

 

Running into the FATAL error, but it doesn't seem to be permission based.

*** Start Log ***

 

2019-09-19 10:05:27.541841 [info] System information Linux MediaMonster 4.19.56-Unraid #1 SMP Tue Jun 25 10:19:34 PDT 2019 x86_64 GNU/Linux
2019-09-19 10:05:27.586466 [info] PUID defined as '99'
2019-09-19 10:05:27.795364 [info] PGID defined as '100'
2019-09-19 10:05:28.076972 [info] UMASK defined as '000'
2019-09-19 10:05:28.120205 [info] Permissions already set for volume mappings
2019-09-19 10:05:28.161932 [info] TRANS_DIR defined as '/config/transcode'
2019-09-19 10:05:28.383057 [info] Starting Supervisor...
2019-09-19 10:05:28,701 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2019-09-19 10:05:28,701 INFO Set uid to user 0 succeeded
2019-09-19 10:05:28,706 INFO supervisord started with pid 6
2019-09-19 10:05:29,708 INFO spawned: 'plexmediaserver' with pid 53
2019-09-19 10:05:29,709 INFO reaped unknown pid 7
2019-09-19 10:05:30,357 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22921431306928 for <Subprocess at 22921431307040 with name plexmediaserver in state STARTING> (stdout)>
2019-09-19 10:05:30,358 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22921431388344 for <Subprocess at 22921431307040 with name plexmediaserver in state STARTING> (stderr)>
2019-09-19 10:05:30,358 INFO exited: plexmediaserver (exit status 255; not expected)
2019-09-19 10:05:30,359 DEBG received SIGCHLD indicating a child quit
2019-09-19 10:05:31,362 INFO spawned: 'plexmediaserver' with pid 58
2019-09-19 10:05:31,482 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22921431389240 for <Subprocess at 22921431307040 with name plexmediaserver in state STARTING> (stdout)>
2019-09-19 10:05:31,482 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22921431307096 for <Subprocess at 22921431307040 with name plexmediaserver in state STARTING> (stderr)>
2019-09-19 10:05:31,482 INFO exited: plexmediaserver (exit status 255; not expected)
2019-09-19 10:05:31,483 DEBG received SIGCHLD indicating a child quit
2019-09-19 10:05:33,487 INFO spawned: 'plexmediaserver' with pid 63
2019-09-19 10:05:33,605 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22921431389240 for <Subprocess at 22921431307040 with name plexmediaserver in state STARTING> (stdout)>
2019-09-19 10:05:33,605 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22921431388456 for <Subprocess at 22921431307040 with name plexmediaserver in state STARTING> (stderr)>
2019-09-19 10:05:33,606 INFO exited: plexmediaserver (exit status 255; not expected)
2019-09-19 10:05:33,606 DEBG received SIGCHLD indicating a child quit
2019-09-19 10:05:36,611 INFO spawned: 'plexmediaserver' with pid 68
2019-09-19 10:05:36,734 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22921431388344 for <Subprocess at 22921431307040 with name plexmediaserver in state STARTING> (stdout)>
2019-09-19 10:05:36,735 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22921431306928 for <Subprocess at 22921431307040 with name plexmediaserver in state STARTING> (stderr)>
2019-09-19 10:05:36,735 INFO exited: plexmediaserver (exit status 255; not expected)
2019-09-19 10:05:36,735 DEBG received SIGCHLD indicating a child quit
2019-09-19 10:05:37,737 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly

 

*** End Log ***

 

Reading about others that have had this error, it seems it should be permission issues. I've used the console to check folder permissions and everything I can find is either "nobody" or "root" in both the "/mnt/user" (directory and sub directories) and "/mnt/cache" (directory and sub directories). 

 

Plex will not launch in the UI, and today is the first time I've had issues with it. Anyone have a suggestion other than "Delete the Docker and reinstall binhex-plexpass to see if that works?" 

 

Please let me know if you want any more information.

 

Thanks!

can you attach (not post) the log '/config/Plex Media Server/Logs/Plex Media Server.log' i suspect another case of database corruption :-(

Link to comment
15 minutes ago, Scott Harkless said:

Not sure is this is where this should go if not let me know. 

 

I had some custom search plugins in my old server but unsure how to get them installed and working in this docker.  Can someone help me out with this?  I have the files downloaded but not sure where to put them and cant remember if they need to be zip or unzipped.

My super lazy way to do it, is add the appdata directory as a share for a moment:

 

image.png.bda0f7b8e41528fd7047c44754900406.png

 

Then I can just copy the files over from whatever machine is convenient (While the plex container is stopped). You could run into some permissions issues, but those can be resolved from a shell without to much difficulty.  

 

Edit: Just remember to remove the appdata share when you are done...you don't want that shared/public most likely.

Edited by paperblankets
More detail
Link to comment

Hi @binhex, I noticed plex has a new transcoder that supports NVIDIA transcoding on Linux with zero copy and all sorts of other nice stuff. Before I rush out and buy a supported card, I was just wondering is it possible to use this new feature and the card when running Plex from a docker? If it were a VM it's a pretty straight forward matter to just pass through the card, is that possible with a docker? Where does one load the drivers?

 

-- Edit

Disregard. Found a video from @SpaceInvaderOne that shows how to do it! 

 

Edited by dgwharrison
Link to comment

I'm having some big problems now. Running Unraid 6.7.0

Been running Binhex Plex for 6 months now without problem, and I usually update once there is an update. Haven't done any change now for a month.

2 Weeks ago this first problem began. Plex doesn't scan media folders anymore, I cant do it manually either, I have to restart the docker for it to rescan, then it works for maybe 2 days or less.

Second problem is that now when I update the docker, it doesn't update. I know the other well known error that some dockers reports having updates all the time even though they are already updated and such, and this is not that problem because I fixed it (found the fix here on the forum). No other docker has this problem.

 

This second problem began today. This does the update, downloads new files. Then when I press "Done" without any error in the "console" it doesn't reload the page and still says "Apply update", so I refresh the page, ctrl + f5 and even pressed "Check for updates" and let it finish, still says "Apply update" and Plex once logged in says "A Plex Media Server update is available"

Edited by kraowe
Link to comment
4 hours ago, kraowe said:

This second problem began today. This does the update, downloads new files. Then when I press "Done" without any error in the "console" it doesn't reload the page and still says "Apply update", so I refresh the page, ctrl + f5 and even pressed "Check for updates" and let it finish, still says "Apply update" and Plex once logged in says "A Plex Media Server update is available"

If you look at your unraid logs around that time, do you see any errors/failures reported?

Link to comment
9 minutes ago, scubieman said:

When copying this from server to server. Which folders/files need to be transferred? I want to be able to keep my watch history?

There is probably a better way, but I just copy my entire appdata/binhex-plexpass directory (I also back it up nightly in case something goes wrong)

 

I'm also interested to know if there is a better way. You can backup the plex database by itself, but that would not help you with your server configuration, thats what I don't want to setup again in my case.

Other thoughts: If your appdata directory is on a cache drive...make sure to stop the container, and invoke the mover before you copy the directory or you will end up in an old state/be missing the changes on the cache drive. I just don't keep my containers on the cache drive. It's more trouble than it's worth for me.

Link to comment
1 minute ago, paperblankets said:

There is probably a better way, but I just copy my entire appdata/binhex-plexpass directory (I also back it up nightly in case something goes wrong)

 

I'm also interested to know if there is a better way. You can backup the plex database by itself, but that would not help you with your server configuration, thats what I don't want to setup again in my case.

Other thoughts: If your appdata directory is on a cache drive...make sure to stop the container, and invoke the mover before you copy the directory or you will end up in an old state/be missing the changes on the cache drive. I just don't keep my containers on the cache drive. It's more trouble than it's worth for me.

I did copy word for word well file fore file however got the error "libusb_init failed"

Link to comment
3 hours ago, scubieman said:

I did copy word for word well file fore file however got the error "libusb_init failed"

Not sure what the error is all about, however it should be noted that depending upon how you copy the appdata folder for plex it can balloon exponentially in size due to Plex's very extensive use of hardlinks.

Link to comment
On 10/6/2019 at 10:56 AM, scubieman said:

I did copy word for word well file fore file however got the error "libusb_init failed"

Ha, by chance, I got the exact error you got last night.

 

In my case, one of two things occurred:

  1. A windows vm started that was allocating the same gpu as my plex container. This shut down the plex container. (Any attempts to start it result in `libusb_init failed` in the logs). 
  2. I did some cable management in my living room and disconnected and reconnected some usb hubs, somehow this caused issues with my plex container.

My assumption is #1 was the cause. You may not be on nvidia-unraid though, so maybe this was some other issue. Simply stopping my offending vm in my case allowed my plex container to start again. 

The solution to #1 was simply to stop the offending vm, no restart was required.

Hopefully part of that helps you debug your issue!

Edited by paperblankets
Grammar, more details.
Link to comment
11 hours ago, Can0nfan said:

Hi @binhex my binhex/plexpass been bugging me for the latest beta update for over 24hours (Version 1.18.0.1906), your automation usually has it compiled and pushed by now whats happening?

All of his updates run on auto scheduler. So as soon as it is available for his scripts, it will automaticly update. No need to ask for it :)

 

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.