Jump to content
binhex

[Support] binhex - Plex Pass

788 posts in this topic Last Reply

Recommended Posts

I got an issue after updating to the latest binhex-plexpass. NO metadata is no longer downloading and on top of this if I find a title to FIX the listing, no Agents are showing so something is broken here. It was working before the latest update.

Share this post


Link to post
3 hours ago, z0ki said:

I got an issue after updating to the latest binhex-plexpass. NO metadata is no longer downloading and on top of this if I find a title to FIX the listing, no Agents are showing so something is broken here. It was working before the latest update.

Update was released 4 hours ago.  I just updated and it fixed the issue.

Share this post


Link to post

I had to rollback yesterday because of the broken update...all was fine until a few hours ago.  My movie library shows up as "There are no items in this library" when I launch Plex from the docker image on unraid.  The files are there as the desktop app shows them, but not via the gui.  I updated to the just released fixed docker app.  Didn't fix the problem.  Anyone see this in the past and have a clue how to fix?  Thanks

Share this post


Link to post
Posted (edited)
19 hours ago, tmoran000 said:

this last binhex release has completely broke my plex. WTF

 

Edit. Looks like a new update released 9 MInutes ago.. Hope it corrects this. 

 

Edit. The update has seemed to correct the Settings issue*

Yup. Looks like it was a Plex specific issue and not a docker build issue. Remove the tag for the specific version and apply (if you rolled back to the previous version) and then check for updates (those who have not rolled back to the previous version just need to do this). Latest version fixes the issue. 

 

 

plexUpdateNotes.jpg

Edited by brianbrifri

Share this post


Link to post
On 8/27/2019 at 9:04 PM, Rudeboy42 said:

Just wondering, by "rolling back" you mean you uninstalled and reinstalled the binhex docker?  why did you have to rebuild the library?  Should a restore of the database do that?

Sorry for the delay.

 

I followed the tag process to roll back binhex.. I had already deleted the library in attempts to fix the issue, so had to rebuild as a consequence, and nothing to do with rolling back binhex

Share this post


Link to post

Crashing right out of the gate, fresh install, copied all of the config stuff over from my previous (limetech) now depreciated plex container.  I've tried priviledged and non-priviledged modes, seems to have file permissions issues?????  

 

--

 

2019-08-31 12:51:38,530 INFO exited: plexmediaserver (terminated by SIGABRT; not expected)
2019-08-31 12:51:38,531 DEBG received SIGCHLD indicating a child quit
2019-08-31 12:51:38,531 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly
2019-08-31 12:51:47,541 WARN received SIGTERM indicating exit request
Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ > <
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2019-08-31 12:51:48.182401 [info] System information Linux 10db7d69425f 4.19.56-Unraid #1 SMP Tue Jun 25 10:19:34 PDT 2019 x86_64 GNU/Linux
2019-08-31 12:51:48.215076 [info] PUID defined as '99'
2019-08-31 12:51:48.251595 [info] PGID defined as '100'
2019-08-31 12:51:48.309291 [info] UMASK defined as '000'
2019-08-31 12:51:48.342060 [info] Permissions already set for volume mappings
2019-08-31 12:51:48.372572 [info] TRANS_DIR defined as '/mnt/disks/ssd/appdata/PlexMediaServer'
2019-08-31 12:51:48.404666 [info] Starting Supervisor...
2019-08-31 12:51:48,568 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2019-08-31 12:51:48,568 INFO Set uid to user 0 succeeded
2019-08-31 12:51:48,571 INFO supervisord started with pid 6
2019-08-31 12:51:49,574 INFO spawned: 'plexmediaserver' with pid 48
2019-08-31 12:51:49,574 INFO reaped unknown pid 7
2019-08-31 12:51:49,588 DEBG 'plexmediaserver' stderr output:
mkdir: cannot create directory ‘/mnt/disks’: Permission denied

2019-08-31 12:51:49,605 DEBG 'plexmediaserver' stderr output:
terminate called after throwing an instance of 'std::runtime_error'
what(): Codecs: Initialize: 'boost::filesystem::temp_directory_path: Not a directory: "/mnt/disks/ssd/appdata/PlexMediaServer"'

2019-08-31 12:51:49,606 DEBG 'plexmediaserver' stderr output:
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Plex Media Server/Crash Reports/1.16.6.1592-b9d49bdb7/PLEX MEDIA SERVER/619f37cd-4edd-aa9f-5a619d85-6d0780ed.dmp

2019-08-31 12:51:49,617 DEBG 'plexmediaserver' stderr output:
Error in command line:the argument for option '--serverUuid' should follow immediately after the equal sign
Crash Uploader options (all are required):
--directory arg
2019-08-31 12:51:49,617 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22989104644840 for <Subprocess at 22989104644784 with name plexmediaserver in state STARTING> (stdout)>
2019-08-31 12:51:49,617 DEBG 'plexmediaserver' stderr output:
Directory to scan for crash reports
--serverUuid arg UUID of the server that crashed
--userId arg User that owns this product
--platform arg Platform string
--platformVersion arg Platform version string
--vendor arg Vendor string
--device arg Device string
--model arg Device model string
--sentryUrl arg Sentry URL to upload to
--

Share this post


Link to post
17 minutes ago, tucansam said:

mkdir: cannot create directory ‘/mnt/disks’: Permission denied

 

17 minutes ago, tucansam said:

terminate called after throwing an instance of 'std::runtime_error'
what(): Codecs: Initialize: 'boost::filesystem::temp_directory_path: Not a directory: "/mnt/disks/ssd/appdata/PlexMediaServer"'

so the issue is you are attempting to set the transcode directory to something that simply doesnt exist INSIDE the container, you need to keep in mind TRANS_DIR is a env var to allow you to define on the container side where you want transcodes to go, /mnt/disks/... wont exist, try the default or set it to a valid path on the container side,

Share this post


Link to post

> Yup. Looks like it was a Plex specific issue and not a docker build issue. Remove the tag for the specific version and apply (if you rolled back to the previous version) and then check for updates (those who have not rolled back to the previous version just need to do this). Latest version fixes the issue

 

 I'm running binhex-plexpass, I don't see any updates, but I have the symptoms listed above. Has a new release happened? Or is the fix still rolling back or removing tags? How do I remove tags?

 

Edit: trying a force update to start with

 

Edit edit: That seems to have worked.

Edited by paperblankets

Share this post


Link to post
On 8/28/2019 at 6:42 AM, tmoran000 said:

this last binhex release has completely broke my plex. WTF

 

Edit. Looks like a new update released 9 MInutes ago.. Hope it corrects this. 

 

Edit. The update has seemed to correct the Settings issue*

Just a bit of education here, please keep in mind guys Plex Pass gives you early access to features, but it also gives you lovely early access to bugs as you have all seen, if you want to minimise this happening in the future then run binhex/plex instead, you still get access to all the plex pass additional stuff with a reduced risk of stuff blowing up in your face, the option is of course yours, i know which version im running and it aint this one :-)

Edited by binhex

Share this post


Link to post
34 minutes ago, binhex said:

Just a bit of education here, please keep in mind guys Plex Pass gives you early access to features, but it also gives you lovely early access to bugs as you have all seen, if you want to minimise this happening in the future then run binhex/plex instead, you still get access to all the plex pass additional stuff with a reduced risk of stuff blowing up in your face, the option is of course yours, i know which version im running and it aint this one 🙂

@binhex, consider adding this information to the first post.  It will help new users decide which docker to use.

 

Share this post


Link to post
2 hours ago, binhex said:

Just a bit of education here, please keep in mind guys Plex Pass gives you early access to features, but it also gives you lovely early access to bugs as you have all seen, if you want to minimise this happening in the future then run binhex/plex instead, you still get access to all the plex pass additional stuff with a reduced risk of stuff blowing up in your face, the option is of course yours, i know which version im running and it aint this one 🙂

General feedback:

I'm happy with the (small) number of bugs, and the gottchas that come with releasing via docker tags/in lockstep with plex-pass releases. I could see this issue not happening if the binhex-* version was semver, and a patch release was made after the plex team rolled their update. That way all users of this container would have been sent a new version. I'm sure this way is very simple though, and allows you to maintain many containers at once without getting bogged down. But yeah, keep up the good work/thanks! 

This issue feedback:

This resolution was done over a beer from my phone, instead of by rebuilding my own docker container, or pulling the latest Plex version from a shell script in a VM and debugging everything that changed since the last time.

 

Tldr feedback: Thanks for making my life easier!

Share this post


Link to post

Hi, guys i have also problems with my PlexPass, since yesterday the Plex Service isn't available anymore. The Failure Code from Console is:

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

2019-09-06 12:56:04.177037 [info] System information Linux SUPERMICRO 4.19.56-Unraid #1 SMP Thu Jun 27 13:13:13 BST 2019 x86_64 GNU/Linux
2019-09-06 12:56:04.218725 [info] PUID defined as '99'
2019-09-06 12:56:04.370511 [info] PGID defined as '100'
2019-09-06 12:56:04.532994 [info] UMASK defined as '000'
2019-09-06 12:56:04.569674 [info] Permissions already set for volume mappings
2019-09-06 12:56:04.609570 [info] TRANS_DIR defined as '/config/transcode'
2019-09-06 12:56:04.726874 [info] Starting Supervisor...
2019-09-06 12:56:05,014 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2019-09-06 12:56:05,015 INFO Set uid to user 0 succeeded
2019-09-06 12:56:05,020 INFO supervisord started with pid 6
2019-09-06 12:56:06,023 INFO spawned: 'plexmediaserver' with pid 53
2019-09-06 12:56:06,024 INFO reaped unknown pid 7
2019-09-06 12:56:06,281 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23334498771632 for <Subprocess at 23334498771744 with name plexmediaserver in state STARTING> (stdout)>
2019-09-06 12:56:06,281 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23334498853160 for <Subprocess at 23334498771744 with name plexmediaserver in state STARTING> (stderr)>
2019-09-06 12:56:06,282 INFO exited: plexmediaserver (exit status 255; not expected)
2019-09-06 12:56:06,283 DEBG received SIGCHLD indicating a child quit
2019-09-06 12:56:07,285 INFO spawned: 'plexmediaserver' with pid 58
2019-09-06 12:56:07,459 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23334498852992 for <Subprocess at 23334498771744 with name plexmediaserver in state STARTING> (stdout)>
2019-09-06 12:56:07,460 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23334498247736 for <Subprocess at 23334498771744 with name plexmediaserver in state STARTING> (stderr)>
2019-09-06 12:56:07,460 INFO exited: plexmediaserver (exit status 255; not expected)
2019-09-06 12:56:07,461 DEBG received SIGCHLD indicating a child quit
2019-09-06 12:56:09,464 INFO spawned: 'plexmediaserver' with pid 63
2019-09-06 12:56:09,640 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23334498771632 for <Subprocess at 23334498771744 with name plexmediaserver in state STARTING> (stdout)>
2019-09-06 12:56:09,640 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23334498853888 for <Subprocess at 23334498771744 with name plexmediaserver in state STARTING> (stderr)>
2019-09-06 12:56:09,640 INFO exited: plexmediaserver (exit status 255; not expected)
2019-09-06 12:56:09,640 DEBG received SIGCHLD indicating a child quit
2019-09-06 12:56:12,646 INFO spawned: 'plexmediaserver' with pid 68
2019-09-06 12:56:12,823 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23334498852992 for <Subprocess at 23334498771744 with name plexmediaserver in state STARTING> (stdout)>
2019-09-06 12:56:12,823 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23334498247904 for <Subprocess at 23334498771744 with name plexmediaserver in state STARTING> (stderr)>
2019-09-06 12:56:12,823 INFO exited: plexmediaserver (exit status 255; not expected)
2019-09-06 12:56:12,824 DEBG received SIGCHLD indicating a child quit
2019-09-06 12:56:13,825 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly

 

The normal Plex without the Pass works fine ? You have any suggestions for me how to fix this problem?

Share this post


Link to post
18 minutes ago, cogliostro said:

Hi, guys i have also problems with my PlexPass, since yesterday the Plex Service isn't available anymore. The Failure Code from Console is:

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

2019-09-06 12:56:04.177037 [info] System information Linux SUPERMICRO 4.19.56-Unraid #1 SMP Thu Jun 27 13:13:13 BST 2019 x86_64 GNU/Linux
2019-09-06 12:56:04.218725 [info] PUID defined as '99'
2019-09-06 12:56:04.370511 [info] PGID defined as '100'
2019-09-06 12:56:04.532994 [info] UMASK defined as '000'
2019-09-06 12:56:04.569674 [info] Permissions already set for volume mappings
2019-09-06 12:56:04.609570 [info] TRANS_DIR defined as '/config/transcode'
2019-09-06 12:56:04.726874 [info] Starting Supervisor...
2019-09-06 12:56:05,014 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2019-09-06 12:56:05,015 INFO Set uid to user 0 succeeded
2019-09-06 12:56:05,020 INFO supervisord started with pid 6
2019-09-06 12:56:06,023 INFO spawned: 'plexmediaserver' with pid 53
2019-09-06 12:56:06,024 INFO reaped unknown pid 7
2019-09-06 12:56:06,281 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23334498771632 for <Subprocess at 23334498771744 with name plexmediaserver in state STARTING> (stdout)>
2019-09-06 12:56:06,281 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23334498853160 for <Subprocess at 23334498771744 with name plexmediaserver in state STARTING> (stderr)>
2019-09-06 12:56:06,282 INFO exited: plexmediaserver (exit status 255; not expected)
2019-09-06 12:56:06,283 DEBG received SIGCHLD indicating a child quit
2019-09-06 12:56:07,285 INFO spawned: 'plexmediaserver' with pid 58
2019-09-06 12:56:07,459 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23334498852992 for <Subprocess at 23334498771744 with name plexmediaserver in state STARTING> (stdout)>
2019-09-06 12:56:07,460 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23334498247736 for <Subprocess at 23334498771744 with name plexmediaserver in state STARTING> (stderr)>
2019-09-06 12:56:07,460 INFO exited: plexmediaserver (exit status 255; not expected)
2019-09-06 12:56:07,461 DEBG received SIGCHLD indicating a child quit
2019-09-06 12:56:09,464 INFO spawned: 'plexmediaserver' with pid 63
2019-09-06 12:56:09,640 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23334498771632 for <Subprocess at 23334498771744 with name plexmediaserver in state STARTING> (stdout)>
2019-09-06 12:56:09,640 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23334498853888 for <Subprocess at 23334498771744 with name plexmediaserver in state STARTING> (stderr)>
2019-09-06 12:56:09,640 INFO exited: plexmediaserver (exit status 255; not expected)
2019-09-06 12:56:09,640 DEBG received SIGCHLD indicating a child quit
2019-09-06 12:56:12,646 INFO spawned: 'plexmediaserver' with pid 68
2019-09-06 12:56:12,823 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23334498852992 for <Subprocess at 23334498771744 with name plexmediaserver in state STARTING> (stdout)>
2019-09-06 12:56:12,823 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23334498247904 for <Subprocess at 23334498771744 with name plexmediaserver in state STARTING> (stderr)>
2019-09-06 12:56:12,823 INFO exited: plexmediaserver (exit status 255; not expected)
2019-09-06 12:56:12,824 DEBG received SIGCHLD indicating a child quit
2019-09-06 12:56:13,825 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly

 

The normal Plex without the Pass works fine ? You have any suggestions for me how to fix this problem?

i would suspect this is database corruption, attach (dont paste) the '/config/Plex Media Server/Logs/Plex Media Server.log' file

Share this post


Link to post
4 minutes ago, cogliostro said:

Looks your right, in the log it says SQLITE3:(nil), 11, database corruption at line 65066 of [bf8c1b2b7a]

Plex Media Server.log 1.22 kB · 0 downloads

yep thought so, so this is caused by one or both of the following issues:-

 

1. /config located on fuse/shfs path - see q7 from the following link for details:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

2. running unraid 6.7.x - limetech are working on a fix so your choice is either roll back to 6.6.7 or wait for 6.8.x which should hopefully include the fix.

 

keep in mind once you think its stable you will then still need to restore your metadata from backup or re-index all your media again with a clean plex database before the issue is resolved.

Share this post


Link to post

Thanks for the answer, i'm just a little confused bcz it worked with no problem till yesterday. Then out of no where this happens

Share this post


Link to post
14 minutes ago, cogliostro said:

Thanks for the answer, i'm just a little confused bcz it worked with no problem till yesterday. Then out of no where this happens

yeah the corruption issue is pretty random and strangely only affects certain users (not myself luckily), no idea why, maybe limetech now know why :-).

Share this post


Link to post
10 minutes ago, binhex said:

yeah the corruption issue is pretty random and strangely only affects certain users (not myself luckily), no idea why, maybe limetech now know why :-).

Do you have appdata on cache? That seems to avoid the problem.

Share this post


Link to post
Do you have appdata on cache? That seems to avoid the problem.
Sadly this is not the fix, it's not related to cache drive as I've seen people posting saying it's still an issue even when using cache and targeting non fuse/shfs paths, so there is something else in play.

Sent from my CLT-L09 using Tapatalk

Share this post


Link to post

Limetech posted this yesterday, which implies that they're not sure whether it is fixed by cache drive, and that it's not fixed in 6.8:

Quote

The update is we are still working on this problem and we have looked at a lot of code.  But what we can't do at the present time is go back to the 6.6.7 build (which does not display this issue) and start adding stuff one-by-one on the path to 6.7.x until we hit something.  Then if we determine it's a kernel change, we face the task of bisecting the kernel.  The problem with this approach it that it's extremely time-consuming, especially when each 'run' might take several hours or even days to exhibit the problem.

 

I'm not trying to make excuses, just laying out where we are with this.  We have access to a server which seems to exhibit the problem readily (meaning it will happen eventually but not "on demand") and we are trying out some theories.

 

One thing that will be useful to know, and why I quoted this particular post from @BBLV is whether this issue only happens when some or all of sqlite database files exist on the array vs. the cache pool.  Put another way, if the entire appdata share, with all sqlite db files underneath all exist on a cache disk or cache pool only, does anyone see this problem?  When it was first reported I thought some were seeing the issue no matter what storage volumes were being utilized and independent of mapping through user shares or not.  This led us down the path of suspecting some common h/w whose driver might have had a change.  This still may end up being part of the issue but now I'm seeing more and more reports that having appdata entirely on cache the problem does not appear.

Here: 

 

Edited by Rick Gillyon

Share this post


Link to post

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.. 

Share this post


Link to post
7 minutes 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.. 

It's an intermittent problem, chances are if plexpass failed, plex will eventually fail too.

Share this post


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.