[Support] binhex - Plex Pass


Recommended Posts

16 minutes ago, ridley said:

having trouble pointing to my XMLTV Guide date from within the PlexPass docker,

I don't use this particular Plex docker container or the XMLTV guide; however, I think your problem is you are possibly trying to use an unRAID file system path inside a docker container.  The container has no concept of unRAID paths.  You probably need to do a volume mapping in the container setup and map something like /guide to /media/downloads/EPG Data and then specify /guide in the XMLTV Guide location.

 

I am not sure if that setup wants a path including the xml file name or just a path to the folder that contains the xml file.  That would alter your volume mapping depending on which is needed.

 

Something like this is needed:

image.png.85daa2fefa33c6aaff12721660dfbfea.png

 

Another potential issue is spaces in the folder path (EPG Data).  I don't know how the container will handle that.  I eliminate spaces in unRAID folder names just because I know they can cause problems at the command line and maybe in docker containers/plugins.

 

 

 

Edited by Hoopster
  • Like 1
Link to comment
9 hours ago, Hoopster said:

I don't use this particular Plex docker container or the XMLTV guide; however, I think your problem is you are possibly trying to use an unRAID file system path inside a docker container.  The container has no concept of unRAID paths.  You probably need to do a volume mapping in the container setup and map something like /guide to /media/downloads/EPG Data and then specify /guide in the XMLTV Guide location.

 

I am not sure if that setup wants a path including the xml file name or just a path to the folder that contains the xml file.  That would alter your volume mapping depending on which is needed.

 

Something like this is needed:

image.png.85daa2fefa33c6aaff12721660dfbfea.png

 

Another potential issue is spaces in the folder path (EPG Data).  I don't know how the container will handle that.  I eliminate spaces in unRAID folder names just because I know they can cause problems at the command line and maybe in docker containers/plugins.

 

 

 

 

Thanks for that, that helped to get that part working.

 

However it did not solve my problem.

 

TVHeadEnd has found 100's of channels, I am using Antennas to create a virtual HDHomeRun to all PLEX to access them but when add the HDHOMERUN it scans the channels finds 900+ on the tuner, 400+ on the EPG (Freesat UK) but then only lists 13 channels with 3 matches.

Any idea where I need to look to see what is going wrong?

Link to comment
8 hours ago, ridley said:

I am using Antennas to create a virtual HDHomeRun to all PLEX

I doubt I could be of much help with this.  I have two physical HDHomeRun tuners connected to Plex and all is well.  I have never tried Antennas/TVHeadend (I'm in the US) for virtual HDHR.

Link to comment
  • 3 weeks later...

Space invader one has a comprehensive video on how to do this just search YouTube for his videos unfortunately I don't have it handy right now but if I get it I'll post it below it is very easy to migrate over I did it myself to the official container sadly it does not update on its own as it posts in the web gooey to update and all you have to do to update on the official container is restart the container but it would be nice if it sent a notification through Docker there was an update so it could update through normal channels other than that it's been Rock solid for me

Link to comment
  • 3 weeks later...

Trying to understand what just happend.

Pushed an update to the container that popped up, and now the web UI is completely inaccessible even locally by going to my machines IP and port. 

Log is showing Critical: libusb_init failed after I try to restart.

 

I will retract this because after about 5 minutes.. it suddenly started working again.. however I do not know why. I do not see any errors in the log other than random metadata errors about an unknown metadata type. so, if there is something I can provide that may illuminate what happened i would be more than happy to. 

Edited by xangetzu
Link to comment
On 4/12/2022 at 10:43 PM, xangetzu said:

Trying to understand what just happend.

Pushed an update to the container that popped up, and now the web UI is completely inaccessible even locally by going to my machines IP and port. 

Log is showing Critical: libusb_init failed after I try to restart.

 

I will retract this because after about 5 minutes.. it suddenly started working again.. however I do not know why. I do not see any errors in the log other than random metadata errors about an unknown metadata type. so, if there is something I can provide that may illuminate what happened i would be more than happy to. 

I am having same issue except webui never came back 

 

I retract as well after about 10 mins and 2 server reboots webui came back

Edited by fireishott1
Link to comment

I restarted my server and noticed plex wasn't running. When I checked the logs it's saying the container is out of space. I know for a fact that my docker image isn't full. Are there limitations on the size of the container? I'm not sure as to why it's not storing everything in the appdata folder.

Quote

Error: Unable to set up server: sqlite3_statement_backend::prepare: disk I/O error for SQL: PRAGMA cache_size=2000 (N4soci10soci_errorE)

Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 109, in emit
self.flush()
File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 68, in flush
self.stream.flush()
OSError: [Errno 28] No space left on device
2022-04-15 12:54:41,155 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23428234374896 for <Subprocess at 23428234369712 with name plexmediaserver in state STARTING> (stdout)>
Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 109, in emit
self.flush()
File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 68, in flush
self.stream.flush()
2022-04-15 12:54:41,155 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23428234374704 for <Subprocess at 23428234369712 with name plexmediaserver in state STARTING> (stderr)>
OSError: [Errno 28] No space left on device
Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 109, in emit
self.flush()
File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 68, in flush
self.stream.flush()
OSError: [Errno 28] No space left on device
2022-04-15 12:54:41,155 INFO exited: plexmediaserver (exit status 255; not expected)
2022-04-15 12:54:41,156 DEBG received SIGCHLD indicating a child quit
Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 109, in emit
self.flush()
File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 68, in flush
self.stream.flush()
OSError: [Errno 28] No space left on device
Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 109, in emit
self.flush()
File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 68, in flush
self.stream.flush()
OSError: [Errno 28] No space left on device
2022-04-15 12:54:42,157 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly
Traceback (most recent call last):
File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 109, in emit
self.flush()
File "/usr/lib/python3.10/site-packages/supervisor/loggers.py", line 68, in flush
self.stream.flush()
OSError: [Errno 28] No space left on device

Any ideas?

 

Update: I figured it out. Before I restarted my computer I updated unassigned devices which. I have my appdata located on an enterprise nvme ssd. Evidently the update disabled the automount. Don't know why I didn't catch it earlier...

Edited by thatnovaguy
Update
Link to comment
On 4/14/2022 at 5:04 AM, fireishott1 said:

I am having same issue except webui never came back 

 

I retract as well after about 10 mins and 2 server reboots webui came back

I had the official version of the container do a similar thing last night at 10:30 p.m. everything just crashed restarting the container never resolved it I had to stop my entire array and restarted and then it started working again

Link to comment

Hello,

 

I'm having a problem with my Plex today, it appears to no longer be starting.

 

This is the error I get in the logs;

"PMS: failure detected. Read/write access is required for path: /config/Plex Media Server"

 

And the docker command is as follows, and executes successfully.

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-plexpass' --net='host' --cpuset-cpus='0,1' -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="tower" -e HOST_CONTAINERNAME="binhex-plexpass" -e 'TRANS_DIR'='/config/transcode' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:32400]/web/index.html' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/plex-icon.png' -v '/mnt/user/Media/':'/media':'rw' -v '/mnt/user/appdata/binhex-plexpass':'/config':'rw' 'binhex/arch-plexpass'

 

 

The complete log is here;

 

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

2022-04-23 12:27:33.039632 [info] Host is running unRAID
2022-04-23 12:27:33.069862 [info] System information Linux tower 5.15.30-Unraid #1 SMP Sat Mar 19 08:42:03 PDT 2022 x86_64 GNU/Linux
2022-04-23 12:27:33.110278 [info] OS_ARCH defined as 'x86-64'
2022-04-23 12:27:33.150647 [info] PUID defined as '99'
2022-04-23 12:27:33.243654 [info] PGID defined as '100'
2022-04-23 12:27:33.328836 [info] UMASK defined as '000'
2022-04-23 12:27:33.359542 [info] Permissions already set for '/config'
2022-04-23 12:27:33.399324 [info] Deleting files in /tmp (non recursive)...
2022-04-23 12:27:33.438181 [info] TRANS_DIR defined as '/config/transcode'
2022-04-23 12:27:33.521726 [info] Starting Supervisor...
2022-04-23 12:27:34,038 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2022-04-23 12:27:34,038 INFO Set uid to user 0 succeeded
2022-04-23 12:27:34,043 INFO supervisord started with pid 7
2022-04-23 12:27:35,046 INFO spawned: 'plexmediaserver' with pid 71
2022-04-23 12:27:35,048 INFO spawned: 'shutdown-script' with pid 72
2022-04-23 12:27:35,049 INFO reaped unknown pid 8 (exit status 0)
2022-04-23 12:27:35,319 DEBG 'plexmediaserver' stderr output:
PMS: failure detected. Read/write access is required for path: /config/Plex Media Server

 

2022-04-23 12:27:35,320 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-04-23 12:27:35,321 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22964515171456 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stdout)>
2022-04-23 12:27:35,322 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22964515171888 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stderr)>
2022-04-23 12:27:35,322 INFO exited: plexmediaserver (exit status 1; not expected)
2022-04-23 12:27:35,322 DEBG received SIGCHLD indicating a child quit
2022-04-23 12:27:36,325 INFO spawned: 'plexmediaserver' with pid 76
2022-04-23 12:27:36,350 DEBG 'plexmediaserver' stderr output:
PMS: failure detected. Read/write access is required for path: /config/Plex Media Server

 

2022-04-23 12:27:36,352 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22964515172368 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stdout)>
2022-04-23 12:27:36,352 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 22964515172416 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stderr)>
2022-04-23 12:27:36,352 INFO exited: plexmediaserver (exit status 1; not expected)
2022-04-23 12:27:36,353 DEBG received SIGCHLD indicating a child quit
2022-04-23 12:27:38,357 INFO spawned: 'plexmediaserver' with pid 79
2022-04-23 12:27:38,386 DEBG 'plexmediaserver' stderr output:
PMS: failure detected. Read/write access is required for path: /config/Plex Media Server

 

2022-04-23 12:27:38,388 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22964515172176 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stdout)>
2022-04-23 12:27:38,388 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 22964515167424 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stderr)>
2022-04-23 12:27:38,389 INFO exited: plexmediaserver (exit status 1; not expected)
2022-04-23 12:27:38,389 DEBG received SIGCHLD indicating a child quit
2022-04-23 12:27:41,395 INFO spawned: 'plexmediaserver' with pid 82
2022-04-23 12:27:41,426 DEBG 'plexmediaserver' stderr output:
PMS: failure detected. Read/write access is required for path: /config/Plex Media Server

 

2022-04-23 12:27:41,428 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22964515168192 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stdout)>
2022-04-23 12:27:41,428 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 22964515172320 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stderr)>
2022-04-23 12:27:41,429 INFO exited: plexmediaserver (exit status 1; not expected)
2022-04-23 12:27:41,429 DEBG received SIGCHLD indicating a child quit
2022-04-23 12:27:42,430 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly

 

Is anyone able to point me to where I might look to rectify this?

 

Thanks

 

Craig

 

Link to comment
9 minutes ago, craig_read said:

Hello,

 

I'm having a problem with my Plex today, it appears to no longer be starting.

 

This is the error I get in the logs;

"PMS: failure detected. Read/write access is required for path: /config/Plex Media Server"

 

And the docker command is as follows, and executes successfully.

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-plexpass' --net='host' --cpuset-cpus='0,1' -e TZ="Europe/London" -e HOST_OS="Unraid" -e HOST_HOSTNAME="tower" -e HOST_CONTAINERNAME="binhex-plexpass" -e 'TRANS_DIR'='/config/transcode' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:32400]/web/index.html' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/plex-icon.png' -v '/mnt/user/Media/':'/media':'rw' -v '/mnt/user/appdata/binhex-plexpass':'/config':'rw' 'binhex/arch-plexpass'

 

 

The complete log is here;

 

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

2022-04-23 12:27:33.039632 [info] Host is running unRAID
2022-04-23 12:27:33.069862 [info] System information Linux tower 5.15.30-Unraid #1 SMP Sat Mar 19 08:42:03 PDT 2022 x86_64 GNU/Linux
2022-04-23 12:27:33.110278 [info] OS_ARCH defined as 'x86-64'
2022-04-23 12:27:33.150647 [info] PUID defined as '99'
2022-04-23 12:27:33.243654 [info] PGID defined as '100'
2022-04-23 12:27:33.328836 [info] UMASK defined as '000'
2022-04-23 12:27:33.359542 [info] Permissions already set for '/config'
2022-04-23 12:27:33.399324 [info] Deleting files in /tmp (non recursive)...
2022-04-23 12:27:33.438181 [info] TRANS_DIR defined as '/config/transcode'
2022-04-23 12:27:33.521726 [info] Starting Supervisor...
2022-04-23 12:27:34,038 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2022-04-23 12:27:34,038 INFO Set uid to user 0 succeeded
2022-04-23 12:27:34,043 INFO supervisord started with pid 7
2022-04-23 12:27:35,046 INFO spawned: 'plexmediaserver' with pid 71
2022-04-23 12:27:35,048 INFO spawned: 'shutdown-script' with pid 72
2022-04-23 12:27:35,049 INFO reaped unknown pid 8 (exit status 0)
2022-04-23 12:27:35,319 DEBG 'plexmediaserver' stderr output:
PMS: failure detected. Read/write access is required for path: /config/Plex Media Server

 

2022-04-23 12:27:35,320 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-04-23 12:27:35,321 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22964515171456 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stdout)>
2022-04-23 12:27:35,322 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22964515171888 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stderr)>
2022-04-23 12:27:35,322 INFO exited: plexmediaserver (exit status 1; not expected)
2022-04-23 12:27:35,322 DEBG received SIGCHLD indicating a child quit
2022-04-23 12:27:36,325 INFO spawned: 'plexmediaserver' with pid 76
2022-04-23 12:27:36,350 DEBG 'plexmediaserver' stderr output:
PMS: failure detected. Read/write access is required for path: /config/Plex Media Server

 

2022-04-23 12:27:36,352 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22964515172368 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stdout)>
2022-04-23 12:27:36,352 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 22964515172416 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stderr)>
2022-04-23 12:27:36,352 INFO exited: plexmediaserver (exit status 1; not expected)
2022-04-23 12:27:36,353 DEBG received SIGCHLD indicating a child quit
2022-04-23 12:27:38,357 INFO spawned: 'plexmediaserver' with pid 79
2022-04-23 12:27:38,386 DEBG 'plexmediaserver' stderr output:
PMS: failure detected. Read/write access is required for path: /config/Plex Media Server

 

2022-04-23 12:27:38,388 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22964515172176 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stdout)>
2022-04-23 12:27:38,388 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 22964515167424 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stderr)>
2022-04-23 12:27:38,389 INFO exited: plexmediaserver (exit status 1; not expected)
2022-04-23 12:27:38,389 DEBG received SIGCHLD indicating a child quit
2022-04-23 12:27:41,395 INFO spawned: 'plexmediaserver' with pid 82
2022-04-23 12:27:41,426 DEBG 'plexmediaserver' stderr output:
PMS: failure detected. Read/write access is required for path: /config/Plex Media Server

 

2022-04-23 12:27:41,428 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22964515168192 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stdout)>
2022-04-23 12:27:41,428 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 22964515172320 for <Subprocess at 22964515167328 with name plexmediaserver in state STARTING> (stderr)>
2022-04-23 12:27:41,429 INFO exited: plexmediaserver (exit status 1; not expected)
2022-04-23 12:27:41,429 DEBG received SIGCHLD indicating a child quit
2022-04-23 12:27:42,430 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly

 

Is anyone able to point me to where I might look to rectify this?

 

Thanks

 

Craig

 

 

Ok so I just did a server restart and now Plex is working.... not sure why this is happening....

Link to comment
  • 2 weeks later...

Hi,

 

I have an issue with the docker container.

 

I've had it happily running for over 12 months taking in regular updates but suddenly the container has stopped and will not start.

 

Other docker containers start normally and run, but attempting to start it up brings up an Execution Error Server Error.

 

No logs appear to be created in either Unraid or the appdata directory.

 

I was wondering whether it was down to a recent update.  Is anyone able to assist?

 

Thanks in advance

Link to comment
16 hours ago, Squid said:

 

The docker run command will show you exactly why that error is coming up

Hi @Squid

 

Thanks for posting.

 

Here is the output of the docker run command.  It appears to complete successfully.  I also tagged to an earlier build in this output, but still have the same issue.

 

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='binhex-plexpass' --net='host' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'TRANS_DIR'='/tmp/' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/Media/':'/media':'rw' -v '/mnt/user/Curated Photos/':'/Photos':'ro' -v '/mnt/user/Music/':'/Music':'rw' -v '/mnt/user/appdata/binhex-plexpass':'/config':'rw' --device='/dev/dri' 'binhex/arch-plexpass:1.26.0.5715-1-01'

34bf46ef5afdbed64debd4a670c313911b64c27d9bc51515acdca098681ea4b0

The command finished successfully!

Link to comment
23 hours ago, minimos said:

Hi @Squid

 

Thanks for posting.

 

Here is the output of the docker run command.  It appears to complete successfully.  I also tagged to an earlier build in this output, but still have the same issue.

 

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='binhex-plexpass' --net='host' -e TZ="Europe/London" -e HOST_OS="Unraid" -e 'TRANS_DIR'='/tmp/' -e 'NVIDIA_DRIVER_CAPABILITIES'='all' -e 'NVIDIA_VISIBLE_DEVICES'='' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -v '/mnt/user/Media/':'/media':'rw' -v '/mnt/user/Curated Photos/':'/Photos':'ro' -v '/mnt/user/Music/':'/Music':'rw' -v '/mnt/user/appdata/binhex-plexpass':'/config':'rw' --device='/dev/dri' 'binhex/arch-plexpass:1.26.0.5715-1-01'

34bf46ef5afdbed64debd4a670c313911b64c27d9bc51515acdca098681ea4b0

The command finished successfully!

Hi,

 

So I finally figured it out.

 

It looks like there was an unintentional power loss rebooting my server.  For some reason the modprobe i915 setting was not in my 'go' config, not sure why as I am sure I added it on server build last year.  However my server had been running 24/7 for over 12 months prior to last week with no reboots.

I figured this out by starting the docker from the terminal using 'docker start' command, which complained of no /dev/dri for hardware transcoding.

 

The 'Power Loss' also explains why my main desktop PC stopped posting late last week (lines up with my Unraid uptime and my wife telling me the 'PC is broken it just went off').  I'd just assumed the old z270 board and 6700k had bit the dust with the latter being nearly 6 years old.  At least I have a z690 and i12600k now though as a shiny replacement, which I could not have justified before. 😀

 

Hope this info helps others in the future.

  • Like 1
Link to comment

I'm having an issue with with both plex and plex pass, after i install them its not asking to setup to the server, its trying contact my old server, that machine is turned off and not being used, i have also tried setting up a new account, and still the name issue  

 

has anyone any thoughts, iv removed the container and reinstalled, removed the appdata, created new config folder

 

TIA

Screenshot 2022-05-08 145937.png

Link to comment
  • 2 weeks later...

Hey guys, I'm getting this error and I tried a couple of things to no avail, does anyone have an idea? Thanks

 

2022-05-16 05:25:16,378 DEBG 'plexmediaserver' stderr output:
Jobs: Exec of /config/Plex Media Server/Codecs/EasyAudioEncoder-1785-linux-x86_64/EasyAudioEncoder/EasyAudioEncoder failed. (13)

 

  • Upvote 2
Link to comment

Hey guys, I've been getting an error that I have been banging my head against that never seen before and can't figure out what is causing it. 

 

Here's the error text:

 

2022-05-21 13:43:19,028 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23247462181536 for <Subprocess at 23247462176064 with name plexmediaserver in state STARTING> (stdout)>
2022-05-21 13:43:19,029 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23247462181584 for <Subprocess at 23247462176064 with name plexmediaserver in state STARTING> (stderr)>
2022-05-21 13:43:19,029 INFO exited: plexmediaserver (exit status 255; not expected)
2022-05-21 13:43:19,029 DEBG received SIGCHLD indicating a child quit
2022-05-21 13:43:21,032 INFO spawned: 'plexmediaserver' with pid 82
2022-05-21 13:43:21,128 DEBG 'plexmediaserver' stdout output:
Error: Unable to set up server: listen: Address in use (N5boost10wrapexceptINS_6system12system_errorEEE)

 

this repeats forever on the official plex docker, and linuxserver repositories, binhex-plexpass cuts it off after like 10 tries.

When I click webUI it just lets me open my plex like normal but there is no server so only the plex served media is there. (kinda obvious since the server wont set up)

 

Here's what I have tried:

Stopping all proxies / tunnels ( I have been messing around with Nginx Proxy manager and Cloudflared tunnels recently, although plex was still working through my messing around so I don't think this is what broke it, but maybe)

 

Factory resetting Router (thought I may have messed up some firewall rule or something that was messing with it, although it should be local so I also am not sure how that could be)

 

uninstalling / reinstalling docker (both with and without deleting appdata)

 

switching to a different plex repository (they all give the same error)

 

Checked that there were no other dockers using that port (there isn't as far as I can tell)

 

I have some kind of hunch that maybe an old process is running and occupying the port, but I have nothing to back that feeling up, nor would I know what to do about a rogue docker process.

 

Any help would be much appreciated, I am a bit of a networking noob so I need a little push sometimes.

 

 

Link to comment

Hello Binhex,

 

Thanks for your many excellent docker apps!

 

Today I experienced an issue with plexpass. I noticed that my clients could not connect and that I could not launch the webUI either. Checking the logs, there were some errors reported. I checked for docker updates and found none available. I then updated UnRaid to 6.10.1. Still no joy. I have tried restarting the docker and UnRaid several times with no change. Below is the log output from the latest restart of the docker. Please let me know if you (or anyone else in the community reading this) knows what this error means and how to correct it.

 

One note possibly of interest. The following line was seen in every log after a restart with the same PID 8 reported. Not sure if that is relevant.

 

2022-05-24 20:30:17,034 INFO reaped unknown pid 8 (exit status 0)

 

Thanks for your assistance. It is truly appreciated.

 

 

 

2022-05-24 20:30:14.855153 [info] Host is running unRAID
2022-05-24 20:30:14.902874 [info] System information Linux UR-Lord 5.15.40-Unraid #1 SMP Mon May 16 10:05:44 PDT 2022 x86_64 GNU/Linux
2022-05-24 20:30:14.960139 [info] OS_ARCH defined as 'x86-64'
2022-05-24 20:30:15.014212 [info] PUID defined as '0'
2022-05-24 20:30:15.081963 [info] PGID defined as '0'
2022-05-24 20:30:15.154679 [info] UMASK defined as '000'
2022-05-24 20:30:15.206388 [info] Permissions already set for '/config'
2022-05-24 20:30:15.269332 [info] Deleting files in /tmp (non recursive)...
2022-05-24 20:30:15.324308 [info] TRANS_DIR defined as '/config/transcode'
2022-05-24 20:30:15.383938 [info] Starting Supervisor...
2022-05-24 20:30:16,022 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2022-05-24 20:30:16,022 INFO Set uid to user 0 succeeded
2022-05-24 20:30:16,028 INFO supervisord started with pid 7
2022-05-24 20:30:17,031 INFO spawned: 'plexmediaserver' with pid 64
2022-05-24 20:30:17,033 INFO spawned: 'shutdown-script' with pid 65
2022-05-24 20:30:17,034 INFO reaped unknown pid 8 (exit status 0)
2022-05-24 20:30:17,308 DEBG 'plexmediaserver' stderr output:
Plex Media Server is already running. Will not start...

 

2022-05-24 20:30:17,308 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-05-24 20:30:17,310 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23110440282496 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stdout)>
2022-05-24 20:30:17,310 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23110440282448 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stderr)>
2022-05-24 20:30:17,310 INFO exited: plexmediaserver (exit status 1; not expected)
2022-05-24 20:30:17,311 DEBG received SIGCHLD indicating a child quit
2022-05-24 20:30:18,313 INFO spawned: 'plexmediaserver' with pid 70
2022-05-24 20:30:18,353 DEBG 'plexmediaserver' stderr output:
Plex Media Server is already running. Will not start...

 

2022-05-24 20:30:18,356 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23110440282736 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stdout)>
2022-05-24 20:30:18,356 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23110440282784 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stderr)>
2022-05-24 20:30:18,357 INFO exited: plexmediaserver (exit status 1; not expected)
2022-05-24 20:30:18,357 DEBG received SIGCHLD indicating a child quit
2022-05-24 20:30:20,361 INFO spawned: 'plexmediaserver' with pid 74
2022-05-24 20:30:20,401 DEBG 'plexmediaserver' stderr output:
Plex Media Server is already running. Will not start...

 

2022-05-24 20:30:20,403 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23110440282544 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stdout)>
2022-05-24 20:30:20,403 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23110440274912 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stderr)>
2022-05-24 20:30:20,403 INFO exited: plexmediaserver (exit status 1; not expected)
2022-05-24 20:30:20,403 DEBG received SIGCHLD indicating a child quit
2022-05-24 20:30:23,408 INFO spawned: 'plexmediaserver' with pid 78
2022-05-24 20:30:23,447 DEBG 'plexmediaserver' stderr output:
Plex Media Server is already running. Will not start...

 

2022-05-24 20:30:23,449 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23110440282640 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stdout)>
2022-05-24 20:30:23,449 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23110440282448 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stderr)>
2022-05-24 20:30:23,449 INFO exited: plexmediaserver (exit status 1; not expected)
2022-05-24 20:30:23,450 DEBG received SIGCHLD indicating a child quit
2022-05-24 20:30:24,451 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly
 

Link to comment

Hi All, I need some help.

I just updated my Plex media server docker. I didnt take note of the old or new versions.

Since the update, when I restart the container, the webUI is available for less than 1 minute. by the time I login I only get the following in the browser
"

This page isn’t working right now

192.168.X.X didn’t send any data.

ERR_EMPTY_RESPONSE
"


I tried updating my Unraid to 6.10.1 and all plugins no change. I've stopped all other containers which also no change.
Container and Unraid have been rebooted multiple times.


Any and all help appreciated

 

Here are the logs from a restart to when the UI fails:

2022-05-27 20:05:43.605456 [info] Host is running unRAID
2022-05-27 20:05:43.648341 [info] System information Linux Media 5.15.40-Unraid #1 SMP Mon May 16 10:05:44 PDT 2022 x86_64 GNU/Linux
2022-05-27 20:05:43.696161 [info] OS_ARCH defined as 'x86-64'
2022-05-27 20:05:43.745276 [info] PUID defined as '99'
2022-05-27 20:05:43.800075 [info] PGID defined as '100'
2022-05-27 20:05:43.861897 [info] UMASK defined as '000'
2022-05-27 20:05:43.910614 [info] Permissions already set for '/config'
2022-05-27 20:05:43.959139 [info] Deleting files in /tmp (non recursive)...
2022-05-27 20:05:44.013444 [info] TRANS_DIR defined as '/tmp'
2022-05-27 20:05:44.066548 [info] Starting Supervisor...
2022-05-27 20:05:44,334 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing
2022-05-27 20:05:44,335 INFO Set uid to user 0 succeeded
2022-05-27 20:05:44,338 INFO supervisord started with pid 8
2022-05-27 20:05:45,341 INFO spawned: 'plexmediaserver' with pid 65
2022-05-27 20:05:45,345 INFO spawned: 'shutdown-script' with pid 66
2022-05-27 20:05:45,346 INFO reaped unknown pid 9 (exit status 0)
2022-05-27 20:05:46,348 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-05-27 20:05:46,348 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-05-27 20:06:33,967 DEBG 'plexmediaserver' stderr output:
libc++abi: terminating with uncaught exception of type std::bad_cast: std::bad_cast

2022-05-27 20:06:36,504 DEBG 'plexmediaserver' stderr output:
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Plex Media Server/Crash Reports/1.26.2.5797-5bd057d2b/PLEX MEDIA SERVER/7c89788c-4091-4c38-a6b0ab8f-f050f596.dmp

2022-05-27 20:06:37,506 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 22722773641792 for <Subprocess at 22722773636560 with name plexmediaserver in state RUNNING> (stdout)>
2022-05-27 20:06:37,507 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 22722773641744 for <Subprocess at 22722773636560 with name plexmediaserver in state RUNNING> (stderr)>
2022-05-27 20:06:37,507 INFO exited: plexmediaserver (terminated by SIGABRT; not expected)
2022-05-27 20:06:37,508 DEBG received SIGCHLD indicating a child quit
2022-05-27 20:06:37,510 INFO spawned: 'plexmediaserver' with pid 211
2022-05-27 20:06:38,512 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)


 

Link to comment
On 5/25/2022 at 1:49 AM, erikm101 said:

2022-05-24 20:30:23,449 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23110440282640 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stdout)>
2022-05-24 20:30:23,449 DEBG fd 12 closed, stopped monitoring <POutputDispatcher at 23110440282448 for <Subprocess at 23110440277264 with name plexmediaserver in state STARTING> (stderr)>
2022-05-24 20:30:23,449 INFO exited: plexmediaserver (exit status 1; not expected)
2022-05-24 20:30:23,450 DEBG received SIGCHLD indicating a child quit
2022-05-24 20:30:24,451 INFO gave up: plexmediaserver entered FATAL state, too many start retries too quickly
 

See Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md

  • Thanks 1
Link to comment
7 hours ago, binhex said:

 

Thanks. I reviewed the logs and found no corruption or fatal entries. I did find a few error relating to parsing xml. Please see below. The last lines for parsing device schema are referencing an NVidia ShieldTV device. I changed the IP to read x.x.x.x.

 

This series of errors repeats several times.

 

Line 20475: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - XML: Entity: line 1:
	Line 20476: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - XML: parser
	Line 20477: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - XML: error :
	Line 20477: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - XML: error :
	Line 20478: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - XML: Start tag expected, '<' not found
	Line 20479: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - XML: status=ok
	Line 20480: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - XML: ^
	Line 20481: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - Error parsing content.
	Line 20481: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - Error parsing content.
	Line 20482: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - Error parsing XML: Error parsing file.
	Line 20482: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - Error parsing XML: Error parsing file.
	Line 20482: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - Error parsing XML: Error parsing file.
	Line 20483: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - SSDP: Error parsing device schema for http://x.x.x.x:9080
	Line 20483: May 24, 2022 05:45:41.053 [0x14684350db38] ERROR - SSDP: Error parsing device schema for http://x.x.x.x:9080

 

Edited by erikm101
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.