Jump to content
binhex

[Support] binhex - Plex Pass

937 posts in this topic Last Reply

Recommended Posts

ok, I changed the ownership of the Plex Media Server folder to nobody and all up and running if it helps someone else! ?

Share this post


Link to post

Just a quick questions as I see there is an option to select the transcode directory on this docker so I would prefer RAM to my SSD so I typed /config/tmp in the location is this all I have to do? also I read somewhere there were issues using RAM to transcode especially with Live TV is that still the case as I prefer a rock solid Plex to one that may crash if to many transcodes ?

 

Many Thanks

Share this post


Link to post
22 hours ago, mbc0 said:

Just a quick questions as I see there is an option to select the transcode directory on this docker so I would prefer RAM to my SSD so I typed /config/tmp in the location is this all I have to do? also I read somewhere there were issues using RAM to transcode especially with Live TV is that still the case as I prefer a rock solid Plex to one that may crash if to many transcodes ?

 

Many Thanks

 

thats not correct, see here scroll down to Plex FAQ Q1:-

 

https://lime-technology.com/forums/topic/44108-support-binhex-general/?do=findComment&comment=433612

 

Edited by binhex

Share this post


Link to post
1 hour ago, binhex said:

 

ah thanks for the pointer binhex, I see that I have to create a ramdrive? (Transcode to RAM - create a new volume mapping, host path /tmp container path /transcode then define TRANS_DIR so that it points at ram drive e.g.:-

 

is this the best solution to creating a ram drive?

 

http://docs.observium.org/persistent_ramdisk/

 

Thanks for your help!

Share this post


Link to post
1 minute ago, mbc0 said:

s this the best solution to creating a ram drive?

 

The best solution (as in the most stable and supported) is to use a cache drive for transcoding and forget about using ram, but ram is a (unsupported) option.

Share this post


Link to post

Hello,

I just updated my plex docker, and now i can't connect to plex server.

i've tried pulling it down and restarting it and even removed and reinstalled it.

any ideas?

 

Thank you

Capture.PNG

Edited by aaw
include log

Share this post


Link to post

Hi, 

 

Check your permissions on the plex directory in appdata

Share this post


Link to post

whats the best way to do that?

 

why would they change just from updating the docker?

 

i did try deleting the perm.txt file and restarting and it didn't help.

 

thank you

Capture.PNG

Share this post


Link to post

i just tried the non plexpass version and it fires right up and starts to load my media, is there at least anyway i can get it to use the meta data from the unworking server until this gets fixed?

 

 

edit:

no idea what the issue was, but it must've been with my cache drive. i pulled it from the array and restarted and now it works again.  lost all my watch statistics since i reinstalled the docker but oh well, at least it'll work.

Edited by aaw
no longer an issue

Share this post


Link to post

Hello fine people.  I'm having one hell of a problem with my server as of late.  Been using unraid for about a year without issues, until I installed the unifi video docker container.  I think I had it was misconfigured upon installation, and somehow used the docker image as data storage.  That locked up my whole system, and I was forced to hard shut down the server.  Luckily everything appears to have come back.  I then had to delete the docker image, and reinstall the containers.  Thought life was great again, but alas I have been unable to play any of my plex media.  The latest message I get from plex is "couldn't retrieve the play queue for this item".  I have spent the last few days trying everything I can think of: installing just the (binhex-plexpass) plex container, try other plex containers, etc.  To no avail.  Anyone have any ideas?  I created a diagnostics file to attach it here.  I would like to get the binhex one working again, as that's been the best behaving one.  

 

Here's what I see over and over in the docker.log file:

time="2018-06-23T21:15:16.787863181-04:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/bbf2c38464cfe96c007d8ba87e2d146d9e803e30c37effe63c3a4aa0d4e2c686/bbf2c38464cfe96c007d8ba87e2d146d9e803e30c37effe63c3a4aa0d4e2c686-json.log: read-only file system" 

 

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

2018-06-28 21:20:11.799736 [info] Host is running unRAID
2018-06-28 21:20:11.830986 [info] System information Linux Tower 4.14.13-unRAID #1 SMP PREEMPT Wed Jan 10 10:27:09 PST 2018 x86_64 GNU/Linux
2018-06-28 21:20:11.869858 [info] PUID defined as '99'
2018-06-28 21:20:11.948700 [info] PGID defined as '100'
2018-06-28 21:20:12.007213 [info] UMASK defined as '000'
2018-06-28 21:20:12.042004 [info] Permissions already set for volume mappings
2018-06-28 21:20:12.079929 [info] TRANS_DIR defined as '/config/transcode'
2018-06-28 21:20:12.176819 [info] Starting Supervisor...
2018-06-28 21:20:12,398 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2018-06-28 21:20:12,399 INFO Set uid to user 0 succeeded
2018-06-28 21:20:12,401 INFO supervisord started with pid 7
2018-06-28 21:20:13,405 INFO spawned: 'plexmediaserver' with pid 55
2018-06-28 21:20:13,405 INFO reaped unknown pid 8
2018-06-28 21:20:14,407 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-06-29 01:00:35,629 DEBG 'plexmediaserver' stderr output:
Connection to 45.56.96.162 closed by remote host.

2018-06-29 04:52:54,065 DEBG 'plexmediaserver' stderr output:
Connection to 45.56.96.162 closed by remote host.

2018-06-29 05:39:55,252 DEBG 'plexmediaserver' stderr output:
Connection to 45.56.103.116 closed by remote host.

2018-06-29 06:15:14,353 DEBG 'plexmediaserver' stderr output:
Connection to 45.56.96.162 closed by remote host.

2018-06-29 08:04:53,046 DEBG 'plexmediaserver' stderr output:
Connection to 45.56.96.162 closed by remote host.

2018-06-29 08:31:34,530 DEBG 'plexmediaserver' stderr output:
Connection to 45.79.184.41 closed by remote host.

 

 

Edited by Thiels851
Adding plex container logs

Share this post


Link to post
Hello fine people.  I'm having one hell of a problem with my server as of late.  Been using unraid for about a year without issues, until I installed the unifi video docker container.  I think I had it was misconfigured upon installation, and somehow used the docker image as data storage.  That locked up my whole system, and I was forced to hard shut down the server.  Luckily everything appears to have come back.  I then had to delete the docker image, and reinstall the containers.  Thought life was great again, but alas I have been unable to play any of my plex media.  The latest message I get from plex is "couldn't retrieve the play queue for this item".  I have spent the last few days trying everything I can think of: installing just the (binhex-plexpass) plex container, try other plex containers, etc.  To no avail.  Anyone have any ideas?  I created a diagnostics file to attach it here.  I would like to get the binhex one working again, as that's been the best behaving one.  
 
Here's what I see over and over in the docker.log file:
time="2018-06-23T21:15:16.787863181-04:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/bbf2c38464cfe96c007d8ba87e2d146d9e803e30c37effe63c3a4aa0d4e2c686/bbf2c38464cfe96c007d8ba87e2d146d9e803e30c37effe63c3a4aa0d4e2c686-json.log: read-only file system" 
 
Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ >
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2018-06-28 21:20:11.799736 [info] Host is running unRAID
2018-06-28 21:20:11.830986 [info] System information Linux Tower 4.14.13-unRAID #1 SMP PREEMPT Wed Jan 10 10:27:09 PST 2018 x86_64 GNU/Linux
2018-06-28 21:20:11.869858 [info] PUID defined as '99'
2018-06-28 21:20:11.948700 [info] PGID defined as '100'
2018-06-28 21:20:12.007213 [info] UMASK defined as '000'
2018-06-28 21:20:12.042004 [info] Permissions already set for volume mappings
2018-06-28 21:20:12.079929 [info] TRANS_DIR defined as '/config/transcode'
2018-06-28 21:20:12.176819 [info] Starting Supervisor...
2018-06-28 21:20:12,398 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2018-06-28 21:20:12,399 INFO Set uid to user 0 succeeded
2018-06-28 21:20:12,401 INFO supervisord started with pid 7
2018-06-28 21:20:13,405 INFO spawned: 'plexmediaserver' with pid 55
2018-06-28 21:20:13,405 INFO reaped unknown pid 8
2018-06-28 21:20:14,407 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-06-29 01:00:35,629 DEBG 'plexmediaserver' stderr output:
Connection to 45.56.96.162 closed by remote host.

2018-06-29 04:52:54,065 DEBG 'plexmediaserver' stderr output:
Connection to 45.56.96.162 closed by remote host.

2018-06-29 05:39:55,252 DEBG 'plexmediaserver' stderr output:
Connection to 45.56.103.116 closed by remote host.

2018-06-29 06:15:14,353 DEBG 'plexmediaserver' stderr output:
Connection to 45.56.96.162 closed by remote host.

2018-06-29 08:04:53,046 DEBG 'plexmediaserver' stderr output:
Connection to 45.56.96.162 closed by remote host.

2018-06-29 08:31:34,530 DEBG 'plexmediaserver' stderr output:
Connection to 45.79.184.41 closed by remote host.
 
 
With that read only file system message I would suspect a corrupt docker IMG file, delete the existing and re-create then simply restore the docker container configs.

Sent from my SM-G935F using Tapatalk

Share this post


Link to post
On 6/22/2018 at 2:47 PM, Random.Name said:

you can just move the whole Plex Library folder from /appdata/binhex-plex to /appdata/binhex-plexpass
Works for migrating to other plex dockers too

 

I tried this, but none of my libraries are there when I shut down the ordinary binhex-plex-docker and start the binhex-plexpass-docker. I only get an empty dashboard saying "the dashboard is empty. Add libraries with your media to make the most of Plex Media Server".

I copied everything from "appdata/binhex-plex/plex media server" to "appdata/binhex-plexpass/plex media server". 

 

Anyone who knows what I'm doing wrong?

Share this post


Link to post

Im not sure if its Plex or unRAID related, so ill try here at first.

 

My Plex server keeps getting warnings in my log. Could anyone tell me what they mean and how to fix them?

I think this is why my server has trouble playing media files smoothly

 

Thank you

Jul 12, 2018 12:12:09.522 [0x1528511fe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (5a8a0b75-e3b7-40a4-baa5-56a71ed00f68, expected )
Jul 12, 2018 12:12:09.542 [0x1528513ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (5a8a0b75-e3b7-40a4-baa5-56a71ed00f68, expected )
Jul 12, 2018 12:13:10.272 [0x1528513ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (bcfdd7ab-1750-44d5-a1d6-7db8acfbcbbe, expected )
Jul 12, 2018 12:13:10.272 [0x1528511fe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (bcfdd7ab-1750-44d5-a1d6-7db8acfbcbbe, expected )
Jul 12, 2018 12:14:09.528 [0x1528513ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (27c17a1a-ff48-42fa-99be-ced9ae38be70, expected )
Jul 12, 2018 12:14:09.528 [0x1528511fe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (27c17a1a-ff48-42fa-99be-ced9ae38be70, expected )
Jul 12, 2018 12:15:09.556 [0x1528513ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (3e79a271-8196-4bec-bc51-e8559e0cfca5, expected )
Jul 12, 2018 12:15:09.556 [0x1528511fe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (3e79a271-8196-4bec-bc51-e8559e0cfca5, expected )
Jul 12, 2018 12:16:09.809 [0x1528513ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (d2971543-2fc1-447c-928c-1f53ce0f851e, expected )
Jul 12, 2018 12:16:09.809 [0x1528511fe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (d2971543-2fc1-447c-928c-1f53ce0f851e, expected )
Jul 12, 2018 12:17:09.988 [0x1528513ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (aeac3032-304c-4957-b2ff-e8685dc033ad, expected )
Jul 12, 2018 12:17:09.988 [0x1528511fe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (aeac3032-304c-4957-b2ff-e8685dc033ad, expected )
Jul 12, 2018 12:18:09.926 [0x1528511fe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (96b0ad63-d673-44f0-a2f9-9ed3ca7431e0, expected )
Jul 12, 2018 12:18:09.926 [0x1528513ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (96b0ad63-d673-44f0-a2f9-9ed3ca7431e0, expected )
Jul 12, 2018 12:19:09.497 [0x1528513ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (ea0babb1-fcb4-4e65-b28d-39ee92956998, expected )
Jul 12, 2018 12:19:09.497 [0x1528511fe700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (ea0babb1-fcb4-4e65-b28d-39ee92956998, expected )
Jul 12, 2018 12:20:09.581 [0x1528513ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (8351d38b-ab8e-4b27-8b93-81ba4a742d88, expected )
Jul 12, 2018 12:20:09.596 [0x1528513ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (8351d38b-ab8e-4b27-8b93-81ba4a742d88, expected )
Jul 12, 2018 12:21:09.566 [0x1528513ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (4a187a86-8db8-4de9-97c9-cb0e6d053eda, expected )
Jul 12, 2018 12:21:09.568 [0x1528513ff700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (4a187a86-8db8-4de9-97c9-cb0e6d053eda, expected )

Share this post


Link to post

Running binhex-PlexPass docker (BTW thank you for all your work)

 

I just got my plex server running tonight.

 

I need to mark a few tv series played. As soon as I did this this is what I see

 

CONTAINER           CPU %               MEM USAGE / LIMIT     MEM %               NET I/O             BLOCK I/O           PIDS
binhex-plexpass     388.64%             429.4MiB / 15.73GiB   2.67%               0B / 0B             190MB / 24.8MB      87
 

I will get to over 650% CPU and just stay there.

When loading plex on my apple tv it will peg the docker cpu to 200% and it just stays there.

Apple TV plex app will time out

 

Here is a screenshot and a diagnostics zip

 

2018-07-31_18-26-12.jpg

tower2-diagnostics-20180731-1903.zip

Edited by Blade

Share this post


Link to post

hello @binhex I recently started locking down my network a little tighter and started with IDS (Intrusion Detection Service)

 

I had this enabled for about a week when i noticed an alert last night they docker container was calling "home" to a French IP in France. it was polling the docker contain on port 51094 and  was trying to relay on port 80 to 94.23.9.xxx

 

the attack was labeled as a Network Trojan, my vendor is Ubiquiti and there is a lot of people saying that Network Trojan could be a false positive

 

I am wondering if you know of any part of your docker contain that would call home to that IP?

 

it only happened once so far if you PM me I could give you screenshot of the detailed attack and offending IP

Share this post


Link to post

Hi, hoping someone can help. I am getting the error "ERR_CONNECTION_REFUSED" when I try to access Plex. I haven't encountered this before and Plex has been stable since I set up my server more than a week ago.

 

A couple of things changed at the same time as this error, and I am not sure if they are related.... 1) changed from unraid free trial to unraid pro, 2) I physically moved my server to a different ethernet point (but same static IP on my router), 3) I created a couple of users in Plex, whereas previously I just had one (now requiring a password for the super user).

 

On my dockers page, under "Port Mappings (App to Host)" there is nothing listed for binhex-plexpass, whereas all my other (working) dockers have the port mappings listed. EDIT: I now realize this is normal behaviour.

 

Any help would be appreciated...

 

EDIT: turned out the problem was being caused by a faulty powerline ethernet adapter. Some troubleshooting and switching out of the adapter led to Plex working normally again. The weird part was that other dockers worked normally throughout.

 

For anyone else with a similar problem, I had tried:

  • Ensuring ownership of directories was set correctly with chown.
  • Reinstalling docker.
  • Ensuring IPV4 network settings were correct.

 

Edited by exoexo
Issue resolved

Share this post


Link to post

Hi All,

 

I restarted my Plex Server this morning as I could not tune any channel with TVHeadend (IPTV working fine with xteve) but I cannot access my Plex Server any more?  I have tried restarting a few times and even rebooted the entire unRAID server.

 

The docker shows as running but I cannot connect to Plex at all locally or remotely.

 

I have uninstalled and re-installed the docker  and here is the log which does not tell me alot!

 

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

2018-08-25 08:31:39.498326 [info] Host is running unRAID
2018-08-25 08:31:39.525157 [info] System information Linux UNRAIDSERVER 4.14.49-unRAID #1 SMP Wed Jun 13 23:15:13 BST 2018 x86_64 GNU/Linux
2018-08-25 08:31:39.555699 [info] PUID defined as '99'
2018-08-25 08:31:39.599022 [info] PGID defined as '100'
2018-08-25 08:31:39.640371 [info] UMASK defined as '000'
2018-08-25 08:31:39.669277 [info] Permissions already set for volume mappings
2018-08-25 08:31:39.702121 [info] TRANS_DIR defined as '/config/tmp'
2018-08-25 08:31:39.775811 [info] Starting Supervisor...
2018-08-25 08:31:40,076 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2018-08-25 08:31:40,076 INFO Set uid to user 0 succeeded
2018-08-25 08:31:40,078 INFO supervisord started with pid 7
2018-08-25 08:31:41,081 INFO spawned: 'plexmediaserver' with pid 55
2018-08-25 08:31:41,081 INFO reaped unknown pid 8
2018-08-25 08:31:41,288 DEBG 'plexmediaserver' stderr output:
Plex Media Server is already running. Will not start...

2018-08-25 08:31:41,289 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23312923628536 for <Subprocess at 23312923629904 with name plexmediaserver in state STARTING> (stdout)>
2018-08-25 08:31:41,289 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23312923325432 for <Subprocess at 23312923629904 with name plexmediaserver in state STARTING> (stderr)>
2018-08-25 08:31:41,289 INFO exited: plexmediaserver (exit status 1; not expected)
2018-08-25 08:31:41,289 DEBG received SIGCLD indicating a child quit
2018-08-25 08:31:42,292 INFO spawned: 'plexmediaserver' with pid 59
2018-08-25 08:31:43,292 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-25 08:34:02,029 DEBG 'plexmediaserver' stderr output:
connect: Connection timed out

2018-08-25 08:36:29,484 DEBG 'plexmediaserver' stderr output:
connect: Connection timed out

 

 

Edited by mbc0

Share this post


Link to post

OK, up and running again... Changed from Host to Bridge and then back to Host! Very Strange!

Share this post


Link to post

Hi,

 

I have the same problem back again but this time cannot get Plex up & running again... I notice that the port mapping section is blank on the binhex version but not on others I have temporarily installed as a test? can Anyone help me out here?

 

 

1.JPG

2.JPG

Share this post


Link to post

since uninstalling the docker and reinstalling I get more errors in the log...

 

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

2018-08-26 13:57:25.490278 [info] Host is running unRAID
2018-08-26 13:57:25.517291 [info] System information Linux UNRAIDSERVER 4.14.49-unRAID #1 SMP Wed Jun 13 23:15:13 BST 2018 x86_64 GNU/Linux
2018-08-26 13:57:25.542969 [info] PUID defined as '99'
2018-08-26 13:57:25.571170 [info] PGID defined as '100'
2018-08-26 13:57:25.608258 [info] UMASK defined as '000'
2018-08-26 13:57:25.638236 [info] Permissions already set for volume mappings
2018-08-26 13:57:25.664089 [info] TRANS_DIR defined as '/config/tmp'
2018-08-26 13:57:25.696058 [info] Starting Supervisor...
2018-08-26 13:57:25,868 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2018-08-26 13:57:25,868 INFO Set uid to user 0 succeeded
2018-08-26 13:57:25,870 INFO supervisord started with pid 7
2018-08-26 13:57:26,872 INFO spawned: 'plexmediaserver' with pid 50
2018-08-26 13:57:26,872 INFO reaped unknown pid 8
2018-08-26 13:57:27,498 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22714652484816 for <Subprocess at 22714652484600 with name plexmediaserver in state STARTING> (stdout)>
2018-08-26 13:57:27,499 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22714652462760 for <Subprocess at 22714652484600 with name plexmediaserver in state STARTING> (stderr)>
2018-08-26 13:57:27,499 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 13:57:27,499 DEBG received SIGCLD indicating a child quit
2018-08-26 13:57:27,498 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22714652484816 for <Subprocess at 22714652484600 with name plexmediaserver in state STARTING> (stdout)>
2018-08-26 13:57:27,499 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22714652462760 for <Subprocess at 22714652484600 with name plexmediaserver in state STARTING> (stderr)>
2018-08-26 13:57:27,499 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 13:57:27,499 DEBG received SIGCLD indicating a child quit
2018-08-26 13:57:28,502 INFO spawned: 'plexmediaserver' with pid 57
2018-08-26 13:57:28,880 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22714652544464 for <Subprocess at 22714652484600 with name plexmediaserver in state STARTING> (stdout)>
2018-08-26 13:57:28,880 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22714649984392 for <Subprocess at 22714652484600 with name plexmediaserver in state STARTING> (stderr)>
2018-08-26 13:57:28,880 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 13:57:28,880 DEBG received SIGCLD indicating a child quit
2018-08-26 13:57:30,884 INFO spawned: 'plexmediaserver' with pid 64
2018-08-26 13:57:31,249 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22714652544464 for <Subprocess at 22714652484600 with name plexmediaserver in state STARTING> (stdout)>
2018-08-26 13:57:31,249 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22714652462904 for <Subprocess at 22714652484600 with name plexmediaserver in state STARTING> (stderr)>
2018-08-26 13:57:31,249 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 13:57:31,249 DEBG received SIGCLD indicating a child quit
2018-08-26 13:57:31,249 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22714652544464 for <Subprocess at 22714652484600 with name plexmediaserver in state STARTING> (stdout)>
2018-08-26 13:57:31,249 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22714652462904 for <Subprocess at 22714652484600 with name plexmediaserver in state STARTING> (stderr)>
2018-08-26 13:57:31,249 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 13:57:31,249 DEBG received SIGCLD indicating a child quit
2018-08-26 13:57:34,253 INFO spawned: 'plexmediaserver' with pid 71
2018-08-26 13:57:34,620 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22714652544464 for <Subprocess at 22714652484600 with name plexmediaserver in state STARTING> (stdout)>
2018-08-26 13:57:34,620 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22714649984392 for <Subprocess at 22714652484600 with name plexmediaserver in state STARTING> (stderr)>
2018-08-26 13:57:34,620 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 13:57:34,620 DEBG received SIGCLD indicating a child quit
2018-08-26 13:57:35,621 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly
2018-08-26 13:59:05,033 WARN received SIGTERM indicating exit request

Share this post


Link to post

I have deleted the perms file after googling and this is where I am at, I would really appreciate any suggestions ?

 

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

2018-08-26 15:51:39.064197 [info] Host is running unRAID
2018-08-26 15:51:39.090493 [info] System information Linux UNRAIDSERVER 4.14.49-unRAID #1 SMP Wed Jun 13 23:15:13 BST 2018 x86_64 GNU/Linux
2018-08-26 15:51:39.125238 [info] PUID defined as '99'
2018-08-26 15:51:39.156287 [info] PGID defined as '100'
2018-08-26 15:51:39.201981 [info] UMASK defined as '000'
2018-08-26 15:51:39.231774 [info] Setting permissions recursively on volume mappings...
2018-08-26 15:54:11.444091 [info] TRANS_DIR defined as '/config/tmp'
2018-08-26 15:54:11.474865 [info] Starting Supervisor...
2018-08-26 15:54:11,648 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2018-08-26 15:54:11,648 INFO Set uid to user 0 succeeded
2018-08-26 15:54:11,652 INFO supervisord started with pid 7
2018-08-26 15:54:12,654 INFO spawned: 'plexmediaserver' with pid 52
2018-08-26 15:54:12,654 INFO reaped unknown pid 8
2018-08-26 15:54:13,288 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23293853467856 for <Subprocess at 23293853467640 with name plexmediaserver in state STARTING> (stdout)>
2018-08-26 15:54:13,288 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23293853445800 for <Subprocess at 23293853467640 with name plexmediaserver in state STARTING> (stderr)>
2018-08-26 15:54:13,288 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 15:54:13,289 DEBG received SIGCLD indicating a child quit
2018-08-26 15:54:14,291 INFO spawned: 'plexmediaserver' with pid 59
2018-08-26 15:54:14,291 INFO spawned: 'plexmediaserver' with pid 59
2018-08-26 15:54:14,674 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23293853527504 for <Subprocess at 23293853467640 with name plexmediaserver in state STARTING> (stdout)>
2018-08-26 15:54:14,675 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23293850967432 for <Subprocess at 23293853467640 with name plexmediaserver in state STARTING> (stderr)>
2018-08-26 15:54:14,675 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 15:54:14,675 DEBG received SIGCLD indicating a child quit
2018-08-26 15:54:16,678 INFO spawned: 'plexmediaserver' with pid 66
2018-08-26 15:54:17,062 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23293853527504 for <Subprocess at 23293853467640 with name plexmediaserver in state STARTING> (stdout)>
2018-08-26 15:54:17,062 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23293853445944 for <Subprocess at 23293853467640 with name plexmediaserver in state STARTING> (stderr)>
2018-08-26 15:54:17,062 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 15:54:17,063 DEBG received SIGCLD indicating a child quit
2018-08-26 15:54:20,067 INFO spawned: 'plexmediaserver' with pid 73
2018-08-26 15:54:20,442 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23293853527504 for <Subprocess at 23293853467640 with name plexmediaserver in state STARTING> (stdout)>
2018-08-26 15:54:20,442 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23293850967432 for <Subprocess at 23293853467640 with name plexmediaserver in state STARTING> (stderr)>
2018-08-26 15:54:20,442 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 15:54:20,442 DEBG received SIGCLD indicating a child quit
2018-08-26 15:54:20,067 INFO spawned: 'plexmediaserver' with pid 73
2018-08-26 15:54:20,442 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23293853527504 for <Subprocess at 23293853467640 with name plexmediaserver in state STARTING> (stdout)>
2018-08-26 15:54:20,442 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23293850967432 for <Subprocess at 23293853467640 with name plexmediaserver in state STARTING> (stderr)>
2018-08-26 15:54:20,442 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 15:54:20,442 DEBG received SIGCLD indicating a child quit
2018-08-26 15:54:21,443 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly

Share this post


Link to post

I am presuming there is an issue with this docker as I have renamed my /mnt/cache/appdata/binhex-plexpass directory to /mnt/cache/appdata/binhex-plexpassold and removed the docker & image & reinstalled, so effectively this is a fresh install and I still have the errors.. surely someone else would be having issues if it was the docker?

 

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

2018-08-26 16:26:19.337263 [info] Host is running unRAID
2018-08-26 16:26:19.366682 [info] System information Linux UNRAIDSERVER 4.14.49-unRAID #1 SMP Wed Jun 13 23:15:13 BST 2018 x86_64 GNU/Linux
2018-08-26 16:26:19.395915 [info] PUID defined as '99'
2018-08-26 16:26:19.438146 [info] PGID defined as '100'
2018-08-26 16:26:19.475080 [info] UMASK defined as '000'
2018-08-26 16:26:19.507320 [info] Setting permissions recursively on volume mappings...
2018-08-26 16:26:19.543004 [info] TRANS_DIR defined as '/config/tmp'
2018-08-26 16:26:19.625282 [info] Starting Supervisor...
2018-08-26 16:26:20,020 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2018-08-26 16:26:20,020 INFO Set uid to user 0 succeeded
2018-08-26 16:26:20,022 INFO supervisord started with pid 7
2018-08-26 16:26:21,026 INFO spawned: 'plexmediaserver' with pid 57
2018-08-26 16:26:21,026 INFO reaped unknown pid 8
2018-08-26 16:26:22,027 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-26 16:26:23,267 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 Directory to scan for crash reports
--serverUuid arg UUID of the server that crashed
--userId arg
2018-08-26 16:26:23,267 DEBG 'plexmediaserver' stderr output:
User that owns this product
--platform arg Platform string
--url arg URL to upload to
--help show help message
--version arg Version of the product

2018-08-26 16:26:23,538 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22428397642528 for <Subprocess at 22428397643176 with name plexmediaserver in state RUNNING> (stdout)>
2018-08-26 16:26:23,538 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22428397643608 for <Subprocess at 22428397643176 with name plexmediaserver in state RUNNING> (stderr)>
2018-08-26 16:26:23,538 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 16:26:23,539 DEBG received SIGCLD indicating a child quit
2018-08-26 16:26:24,541 INFO spawned: 'plexmediaserver' with pid 67
2018-08-26 16:26:24,772 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22428397642528 for <Subprocess at 22428397643176 with name plexmediaserver in state STARTING> (stdout)>
2018-08-26 16:26:24,772 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22428397882688 for <Subprocess at 22428397643176 with name plexmediaserver in state STARTING> (stderr)>
2018-08-26 16:26:24,772 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 16:26:24,772 DEBG received SIGCLD indicating a child quit
2018-08-26 16:26:25,775 INFO spawned: 'plexmediaserver' with pid 74
2018-08-26 16:26:25,990 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22428397880744 for <Subprocess at 22428397643176 with name plexmediaserver in state STARTING> (stdout)>
2018-08-26 16:26:25,990 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22428397643608 for <Subprocess at 22428397643176 with name plexmediaserver in state STARTING> (stderr)>
2018-08-26 16:26:25,990 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 16:26:25,990 DEBG received SIGCLD indicating a child quit
2018-08-26 16:26:27,993 INFO spawned: 'plexmediaserver' with pid 81
2018-08-26 16:26:28,207 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22428397574192 for <Subprocess at 22428397643176 with name plexmediaserver in state STARTING> (stdout)>
2018-08-26 16:26:28,207 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22428397880744 for <Subprocess at 22428397643176 with name plexmediaserver in state STARTING> (stderr)>
2018-08-26 16:26:28,207 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 16:26:28,207 DEBG received SIGCLD indicating a child quit
2018-08-26 16:26:31,211 INFO spawned: 'plexmediaserver' with pid 88
2018-08-26 16:26:31,418 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22428397574192 for <Subprocess at 22428397643176 with name plexmediaserver in state STARTING> (stdout)>
2018-08-26 16:26:31,418 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22428397641808 for <Subprocess at 22428397643176 with name plexmediaserver in state STARTING> (stderr)>
2018-08-26 16:26:31,418 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 16:26:31,418 DEBG received SIGCLD indicating a child quit
2018-08-26 16:26:32,418 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly

Share this post


Link to post
I am presuming there is an issue with this docker as I have renamed my /mnt/cache/appdata/binhex-plexpass directory to /mnt/cache/appdata/binhex-plexpassold and removed the docker & image & reinstalled, so effectively this is a fresh install and I still have the errors.. surely someone else would be having issues if it was the docker?
 
Created by...
___. .__ .__
\_ |__ |__| ____ | |__ ____ ___ ___
| __ \| |/ \| | \_/ __ \\ \/ /
| \_\ \ | | \ Y \ ___/ >
|___ /__|___| /___| /\___ >__/\_ \
\/ \/ \/ \/ \/
https://hub.docker.com/u/binhex/

2018-08-26 16:26:19.337263 [info] Host is running unRAID
2018-08-26 16:26:19.366682 [info] System information Linux UNRAIDSERVER 4.14.49-unRAID #1 SMP Wed Jun 13 23:15:13 BST 2018 x86_64 GNU/Linux
2018-08-26 16:26:19.395915 [info] PUID defined as '99'
2018-08-26 16:26:19.438146 [info] PGID defined as '100'
2018-08-26 16:26:19.475080 [info] UMASK defined as '000'
2018-08-26 16:26:19.507320 [info] Setting permissions recursively on volume mappings...
2018-08-26 16:26:19.543004 [info] TRANS_DIR defined as '/config/tmp'
2018-08-26 16:26:19.625282 [info] Starting Supervisor...
2018-08-26 16:26:20,020 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2018-08-26 16:26:20,020 INFO Set uid to user 0 succeeded
2018-08-26 16:26:20,022 INFO supervisord started with pid 7
2018-08-26 16:26:21,026 INFO spawned: 'plexmediaserver' with pid 57
2018-08-26 16:26:21,026 INFO reaped unknown pid 8
2018-08-26 16:26:22,027 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2018-08-26 16:26:23,267 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 Directory to scan for crash reports
--serverUuid arg UUID of the server that crashed
--userId arg
2018-08-26 16:26:23,267 DEBG 'plexmediaserver' stderr output:
User that owns this product
--platform arg Platform string
--url arg URL to upload to
--help show help message
--version arg Version of the product

2018-08-26 16:26:23,538 DEBG fd 8 closed, stopped monitoring (stdout)>
2018-08-26 16:26:23,538 DEBG fd 10 closed, stopped monitoring (stderr)>
2018-08-26 16:26:23,538 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 16:26:23,539 DEBG received SIGCLD indicating a child quit
2018-08-26 16:26:24,541 INFO spawned: 'plexmediaserver' with pid 67
2018-08-26 16:26:24,772 DEBG fd 8 closed, stopped monitoring (stdout)>
2018-08-26 16:26:24,772 DEBG fd 10 closed, stopped monitoring (stderr)>
2018-08-26 16:26:24,772 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 16:26:24,772 DEBG received SIGCLD indicating a child quit
2018-08-26 16:26:25,775 INFO spawned: 'plexmediaserver' with pid 74
2018-08-26 16:26:25,990 DEBG fd 8 closed, stopped monitoring (stdout)>
2018-08-26 16:26:25,990 DEBG fd 10 closed, stopped monitoring (stderr)>
2018-08-26 16:26:25,990 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 16:26:25,990 DEBG received SIGCLD indicating a child quit
2018-08-26 16:26:27,993 INFO spawned: 'plexmediaserver' with pid 81
2018-08-26 16:26:28,207 DEBG fd 8 closed, stopped monitoring (stdout)>
2018-08-26 16:26:28,207 DEBG fd 10 closed, stopped monitoring (stderr)>
2018-08-26 16:26:28,207 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 16:26:28,207 DEBG received SIGCLD indicating a child quit
2018-08-26 16:26:31,211 INFO spawned: 'plexmediaserver' with pid 88
2018-08-26 16:26:31,418 DEBG fd 8 closed, stopped monitoring (stdout)>
2018-08-26 16:26:31,418 DEBG fd 10 closed, stopped monitoring (stderr)>
2018-08-26 16:26:31,418 INFO exited: plexmediaserver (exit status 255; not expected)
2018-08-26 16:26:31,418 DEBG received SIGCLD indicating a child quit
2018-08-26 16:26:32,418 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly
I would love to try and help you out but I'm currently about 2000 miles away from my laptop and server and I'm currently enjoying a large glass of sangria so I won't be able to help debug this until I'm back on the 3rd sept, hopefully somebody else on the forum can help out, you could always try rolling back to a previously tagged version, see my faq for help if you don't know how to do this.

Sent from my SM-G935F using Tapatalk

Share this post


Link to post

Aha! 

 

I cannot tell you how much I appreciate you just commenting! I hope you have now forgotten my issue and are enjoying many more Sanria's! Have a great time! ?

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.