On 8/16/2019 at 10:14 AM, binhex said:

hmm so custom bridge seems to have a limitation/bug, if you choose custom bridge then it looks like you cannot define both host and container port, so yor only option is default bridge (or host of course).

thanks for your looking into it im at a loss im ok with not having the gui option as i tend to just type in the URL to bring it

On 8/16/2019 at 12:14 PM, binhex said:

f you choose custom bridge then it looks like you cannot define both host and container port,

Because when using a custom bridge there is no port mapping at all.

 

Stupid question though:

 

Can you just set the web UI instead of

 

http://[IP]:[PORT32400]

 

to instead be

 

http://192.168.x.x:32400 

Hey, my container is listed as up-to-date, but I'm still showing PMS version 1.16.2.1297. Is there a method to force the update without uninstalling/reinstalling?

On 8/16/2019 at 12:14 PM, binhex said:

hmm so custom bridge seems to have a limitation/bug, if you choose custom bridge then it looks like you cannot define both host and container port, so yor only option is default bridge (or host of course).

For experimentation, I'm running two Plex dockers (one LinuxServer and one Binhex), using different appdata folders.  Since you can't change the port that Plex listens on (38400), I needed to assign a different  IP address to one of the dockers.  So the Binhex docker is running on Custom:br0, and a fixed IP address.  br0 is a Linux bridge, not a Docker bridge, so port mappings are not required. Its like Host mode.

 

I'm still on 6.6.7, but that shouldn't matter.

Edited August 18, 20196 yr by aim60
Additional clarification

19 hours ago, SicSemper said:

Hey, my container is listed as up-to-date, but I'm still showing PMS version 1.16.2.1297. Is there a method to force the update without uninstalling/reinstalling?

click on the 'check for updates' button in the unraid web ui, if update is available then click on 'update all' or or the 'force update' link (shown only in advanced view)

Edited August 18, 20196 yr by binhex

Ok this is driving me crazy. My flash drive died yesterday which was the root a few other problems I've been having.

 

Anyways, rebuilt a flash drive, pointed everything to the proper locations. Re-added all my dockers and mapped to my previous cache appdata folders and looked like everything worked perfectly. I'm now noticing a few little oddities with plex. 

 

1. Network graph in the plex dashboard/status page doesn't work yet cpu, mem etc does.
2.  Plex Notifications now send me dupes. Once a movie is added, it will notify me as it should but also notify me of all the movies that have been added since I've had to rebuild the USB. Each time the notifications gets incremented by +1. I'm now up to 12 notifications when a single movie is added. Next time will be 13 and so on.

 

Everything use to work fine before. 

 

Things I've tried

• Forced update,
• plex optimize db
• plex clean ups
• signing out of all devices and back in

 

Any thoughts on how to solve this?

 

Edited August 19, 20196 yr by Fiala06

10 hours ago, Fiala06 said:

Ok this is driving me crazy. My flash drive died yesterday which was the root a few other problems I've been having.

 

Anyways, rebuilt a flash drive, pointed everything to the proper locations. Re-added all my dockers and mapped to my previous cache appdata folders and looked like everything worked perfectly. I'm now noticing a few little oddities with plex. 

 

1. Network graph in the plex dashboard/status page doesn't work yet cpu, mem etc does.
2.  Plex Notifications now send me dupes. Once a movie is added, it will notify me as it should but also notify me of all the movies that have been added since I've had to rebuild the USB. Each time the notifications gets incremented by +1. I'm now up to 12 notifications when a single movie is added. Next time will be 13 and so on.

 

Everything use to work fine before. 

 

Things I've tried

• Forced update,
• plex optimize db
• plex clean ups
• signing out of all devices and back in

 

Any thoughts on how to solve this?

 

both sound like new plex bugs to me, found one ref to the dup notifications:-

 

https://www.reddit.com/r/PleX/comments/cpcyso/duplicate_notifications/

 

Hello, I selected the upgrade option from the docker container version column and my plex docker cannot be contacted via the WebUI. Below is the log feedback.

 

What is the next step to diagnose this problem? Thank you. Noobie Alert.

 

 

https://hub.docker.com/u/binhex/

2019-08-20 21:31:39.998245 [info] System information Linux TheSun 4.19.56-Unraid #1 SMP Tue Jun 25 10:19:34 PDT 2019 x86_64 GNU/Linux
2019-08-20 21:31:40.053575 [info] PUID defined as '99'
2019-08-20 21:31:40.153762 [info] PGID defined as '100'
2019-08-20 21:31:40.990113 [info] UMASK defined as '000'
2019-08-20 21:31:41.009039 [info] Permissions already set for volume mappings
2019-08-20 21:31:41.028365 [info] TRANS_DIR defined as '/config/transcode'
2019-08-20 21:31:41.085946 [info] Starting Supervisor...
2019-08-20 21:31:42,256 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2019-08-20 21:31:42,256 INFO Set uid to user 0 succeeded
2019-08-20 21:31:42,258 INFO supervisord started with pid 6
2019-08-20 21:31:43,261 INFO spawned: 'plexmediaserver' with pid 48
2019-08-20 21:31:43,261 INFO reaped unknown pid 7
2019-08-20 21:31:44,262 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2019-08-20 21:31:44,370 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22867581526816 for <Subprocess at 22867581526928 with name plexmediaserver in state RUNNING> (stdout)>
2019-08-20 21:31:44,370 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22867581604136 for <Subprocess at 22867581526928 with name plexmediaserver in state RUNNING> (stderr)>
2019-08-20 21:31:44,370 INFO exited: plexmediaserver (exit status 255; not expected)
2019-08-20 21:31:44,371 DEBG received SIGCHLD indicating a child quit
2019-08-20 21:31:45,373 INFO spawned: 'plexmediaserver' with pid 53
2019-08-20 21:31:45,443 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22867581605032 for <Subprocess at 22867581526928 with name plexmediaserver in state STARTING> (stdout)>
2019-08-20 21:31:45,443 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22867581526984 for <Subprocess at 22867581526928 with name plexmediaserver in state STARTING> (stderr)>
2019-08-20 21:31:45,443 INFO exited: plexmediaserver (exit status 255; not expected)
2019-08-20 21:31:45,443 DEBG received SIGCHLD indicating a child quit
2019-08-20 21:31:46,445 INFO spawned: 'plexmediaserver' with pid 58
2019-08-20 21:31:46,513 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22867581605032 for <Subprocess at 22867581526928 with name plexmediaserver in state STARTING> (stdout)>
2019-08-20 21:31:46,513 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22867581604248 for <Subprocess at 22867581526928 with name plexmediaserver in state STARTING> (stderr)>
2019-08-20 21:31:46,513 INFO exited: plexmediaserver (exit status 255; not expected)
2019-08-20 21:31:46,513 DEBG received SIGCHLD indicating a child quit
2019-08-20 21:31:48,517 INFO spawned: 'plexmediaserver' with pid 63
2019-08-20 21:31:48,583 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22867581604136 for <Subprocess at 22867581526928 with name plexmediaserver in state STARTING> (stdout)>
2019-08-20 21:31:48,583 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22867581526816 for <Subprocess at 22867581526928 with name plexmediaserver in state STARTING> (stderr)>
2019-08-20 21:31:48,583 INFO exited: plexmediaserver (exit status 255; not expected)
2019-08-20 21:31:48,583 DEBG received SIGCHLD indicating a child quit
2019-08-20 21:31:51,588 INFO spawned: 'plexmediaserver' with pid 68
2019-08-20 21:31:51,657 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22867581464304 for <Subprocess at 22867581526928 with name plexmediaserver in state STARTING> (stdout)>
2019-08-20 21:31:51,657 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22867581604248 for <Subprocess at 22867581526928 with name plexmediaserver in state STARTING> (stderr)>
2019-08-20 21:31:51,657 INFO exited: plexmediaserver (exit status 255; not expected)
2019-08-20 21:31:51,657 DEBG received SIGCHLD indicating a child quit
2019-08-20 21:31:52,659 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly

 

4 hours ago, binhex said:

both sound like new plex bugs to me, found one ref to the dup notifications:-

 

https://www.reddit.com/r/PleX/comments/cpcyso/duplicate_notifications/

 

Thanks, that's what I thought as well. Turns out I also inherited a corrupt database. Appreciate it! 

Hello, 

I just updated to the most recent docker version: Container ID 04de605cabe4 and am getting errors: 

Plex Plug-in [com.plexapp.system]: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory


2019-08-26 11:15:29,351 DEBG 'plexmediaserver' stderr output:
Plex Plug-in [com.plexapp.system]: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory


2019-08-26 11:15:29,357 DEBG 'plexmediaserver' stderr output:
Plex Plug-in [com.plexapp.agents.htbackdrops]: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory

I've researched the error online and most common fix was to export LD_LIBRARY_PATH=/usr/lib/plexmediaserver. I added that to the docker config but the errors still persist. Any thoughts on what might be the issue?

2 minutes ago, brianbrifri said:

Hello, 

I just updated to the most recent docker version: Container ID 04de605cabe4 and am getting errors: 

Plex Plug-in [com.plexapp.system]: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory


2019-08-26 11:15:29,351 DEBG 'plexmediaserver' stderr output:
Plex Plug-in [com.plexapp.system]: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory


2019-08-26 11:15:29,357 DEBG 'plexmediaserver' stderr output:
Plex Plug-in [com.plexapp.agents.htbackdrops]: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory

I've researched the error online and most common fix was to export LD_LIBRARY_PATH=/usr/lib/plexmediaserver. I added that to the docker config but the errors still persist. Any thoughts on what might be the issue?

me to, i have my dockers auto update on plex and now it will not restart, rolling back to old verion until this is fixed a option ?

Edited August 26, 20196 yr by idmanager

1 minute ago, idmanager said:

me to, i have my doockers auto update on plex and now it will not restart, rolling back to old verion until this is fixed a option ?

Are you able to roll back to a previous version?

1 minute ago, brianbrifri said:

Are you able to roll back to a previous version?

edit the docker and put binhex/arch-plexpass:1.16.5.1554-1-01 in the Repository:

2 minutes ago, idmanager said:

edit the docker and put binhex/arch-plexpass:1.16.5.1554-1-01 in the Repository:

That worked. Weirdly it seems that version is actually the same as the latest version, which I assume is having issues.

I think something is just broken with that build

1.16.6.1559 is the build with the issue

I have the same error. Had to roll back.


Sent from my iPhone using Tapatalk

Hello, 
I just updated to the most recent docker version: Container ID 04de605cabe4 and am getting errors: 

Plex Plug-in [com.plexapp.system]: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory2019-08-26 11:15:29,351 DEBG 'plexmediaserver' stderr output:Plex Plug-in [com.plexapp.system]: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory2019-08-26 11:15:29,357 DEBG 'plexmediaserver' stderr output:Plex Plug-in [com.plexapp.agents.htbackdrops]: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory

I've researched the error online and most common fix was to export LD_LIBRARY_PATH=/usr/lib/plexmediaserver. I added that to the docker config but the errors still persist. Any thoughts on what might be the issue?

I am currently away on holiday so this will have to wait until I'm back on Sunday, for now please roll back to the previous working tagged version.

Sent from my CLT-L09 using Tapatalk

i am having a very frustrating issue, which is now beyond my limited knowledge of Unraid and Plex..

 

So yesterday I decided to update Unraid (from 6.5 to 6.7.2), and Plex (linuxserver version) to the newest version.

After that have had a whole host of issues, mainly with Plex which seemed to have corrupted the libraries for Movies & TV shows, making them unavailable and not possible to view via Plex GUI, or a respective player. 

 

After hours of trying to get it to work (and searching online), I decided to delete the docker, and rename the Appdata folder, installing the binhex version (all new).

 

I thought it was strange on loading binhex that it gave my user details straight away (as not sure where it pulled it from), and on loading it, its saying that the server is not accessible and wont let me add any meedia to the library.

 

Is there somewhere else I need to delete old plex data, as its doing my head in

 

**UPDATE**

OK looks like its the current plex version thats broken (both Linuxserver & binhex), and rolling back the binhex version is working..

 

Time to rebuild the library....

Edited August 27, 20196 yr by djglenn

Looks like the latest Plex update broke the settings page.  

Plex Plug-in [com.plexapp.system]: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory

Running Binhex/arch-plexpass 1.16.6.1559-1-01.  All settings pages display "Server settings are unavailable."  However, the server itself works. Plex.tv is aware.

7 hours ago, djglenn said:

**UPDATE**

OK looks like its the current plex version thats broken (both Linuxserver & binhex), and rolling back the binhex version is working..

 

Time to rebuild the library....

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?

9 hours ago, binhex said:

I am currently away on holiday so this will have to wait until I'm back on Sunday, for now please roll back to the previous working tagged version.

Could someone please link a walk-through or provide the steps to do this roll back function mentioned above?

36 minutes ago, VernGraner said:

Could someone please link a walk-through or provide the steps to do this roll back function mentioned above?

Check Q5 in the following Github link: 

https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

Just checked the Plex forum and a new build has been posted:

Quote

Build 1.16.6.1559 has been corrected and is now being superseded with the corrected build.

The root cause was an RPATH regression.

The new build is 1.16.6.1592

How long before we see "binhex/arch-pass" update?

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*

Edited August 28, 20196 yr by tmoran000