[Support] Linuxserver.io - Plex Media Server


Recommended Posts

43 minutes ago, biiiink said:

 

Yes.  I've restarted the Docker multiple times

I think this is your problem since you nuked everything and started over-

 

quote from github readme

For new users, no updates will take place on the first run of the container as there is no preferences file to read your token from, to update restart the Docker container after logging in through the webui

Link to comment
49 minutes ago, wgstarks said:

Was it after you logged in via the webUI?

Yes.

 

I just did it again.  I restarted the Docker, opened the WebUI, logged out, Restarted the docker, opened the WebUI, logged in, restarted the Docker.  The message you referred to comes up every time.  Although I noticed that the last time I restarted, the log looked different:

-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/


Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donations/
-------------------------------------
GID/UID
-------------------------------------

User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-dbus: executing...
[cont-init.d] 30-dbus: exited 0.
[cont-init.d] 40-chown-files: executing...
[cont-init.d] 40-chown-files: exited 0.
[cont-init.d] 50-plex-update: executing...



#####################################################
# Login via the webui at http://<ip>:32400/web #
# and restart the docker, because there was no #
# plex token found in the preference file #
#####################################################


[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting dbus-daemon
Starting Plex Media Server.
[services.d] done.
dbus[274]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted

Starting Avahi daemon
Found user 'avahi' (UID 106) and group 'avahi' (GID 107).
Successfully dropped root privileges.
avahi-daemon 0.6.32-rc starting up.
No service file found in /etc/avahi/services.
*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***

*** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***

Joining mDNS multicast group on interface vethdd568c3.IPv6 with address fe80::4c23:22ff:feda:9e2b.
New relevant interface vethdd568c3.IPv6 for mDNS.
Joining mDNS multicast group on interface vethfe169a7.IPv6 with address fe80::6883:1bff:fe32:bc4b.
New relevant interface vethfe169a7.IPv6 for mDNS.
Joining mDNS multicast group on interface veth1470a2b.IPv6 with address fe80::90f9:acff:fec8:8263.
New relevant interface veth1470a2b.IPv6 for mDNS.
Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:48ff:fe16:8974.
New relevant interface docker0.IPv6 for mDNS.
Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
New relevant interface docker0.IPv4 for mDNS.
Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
New relevant interface virbr0.IPv4 for mDNS.
Joining mDNS multicast group on interface br0.IPv6 with address fe80::ba:e1ff:fe91:340d.
New relevant interface br0.IPv6 for mDNS.
Joining mDNS multicast group on interface br0.IPv4 with address 13.13.13.2.
New relevant interface br0.IPv4 for mDNS.
Joining mDNS multicast group on interface bond0.IPv6 with address fe80::92e6:baff:fe2e:d6c9.
New relevant interface bond0.IPv6 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::4c23:22ff:feda:9e2b on vethdd568c3.*.
Registering new address record for fe80::6883:1bff:fe32:bc4b on vethfe169a7.*.
Registering new address record for fe80::90f9:acff:fec8:8263 on veth1470a2b.*.
Registering new address record for fe80::42:48ff:fe16:8974 on docker0.*.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for 192.168.122.1 on virbr0.IPv4.
Registering new address record for fe80::ba:e1ff:fe91:340d on br0.*.
Registering new address record for 13.13.13.2 on br0.IPv4.
Registering new address record for fe80::92e6:baff:fe2e:d6c9 on bond0.*.
Server startup complete. Host name is Titania.local. Local service cookie is 2159768972.
Server startup complete. Host name is Titania.local. Local service cookie is 2159768972.

 

Link to comment
4 hours ago, Maticks said:

Very interesting... Have you tried the binhex container? I might have to fire up a second Plex docker see if that fixes it.

 

Do other transcodes work though writing to /tmp

 

I'm using the official Plex Inc Docker container. Not tried the binhex container.

 

I now have the transcode directory on the cache drive. 

 

I'm not sure what messed up my linuxserver.io container. It's interesting to do a new install of the linuxserver.io container to check if the problem still exists. Maybe writing to /tmp messed everything up. On the other hand I copied my docker plex linuxserver.io config to the new docker plex inc container. So it's running with the same settings. Of course I did change the directory of transcode location in the setting of plex server.

Link to comment
51 minutes ago, Stupifier said:

Is Hardware Acceleration still only possible for those who have iGPU (integrated graphics through CPU)? I have two AMD graphics cards (both on different PCI slots).......still not really sure if I can get Hardware Acceleration on docker Plex. Can anyone confirm?

 

See Plex Hardware-Acelerated Streaming page for details.  https://support.plex.tv/articles/115002178853-using-hardware-accelerated-streaming/

 

Short answer is that with a docker running on unRAID, you are limited to Intel iGPU with Quick Sync Video support.  Although there is a mention on that page of AMD GPU support from Plex, no details are given and there are no nVidia drivers in unRAID to support hardware acceleration with nVidia GPUs.  Some in the community have looked into creating a version of unRAID with nVidia drivers (Like CHBMB does with his DVB version), but, that has not happened. Same is true for AMD GPUs.  They are only mentioned as being supported on Plex in Windows; not Linux.

 

Here is what Plex says about Linux requirements for hardware acceleration:

Linux system requirements

Hardware-Accelerated Streaming on Linux requires:

  • 64-bit Ubuntu (16.04 or later) or 64-bit Fedora (26 or later) distributions. (Other distributions may be capable, but are not officially supported.)
  • A recent Intel CPU meeting these requirements:
    • 2nd-generation Intel Core (Sandy Bridge, 2011) or newer (we recommend 5th-gen Broadwell or newer for the best experience; Sandy Bridge, in particular, is known to sometimes have poor visual output on Linux)
    • Supports Intel Quick Sync Video (Not sure? Look up your processor)
  • Plex Media Server 1.9.3 or later
  • Plex Pass subscription

If your Linux computer also has a dedicated graphics card, the video encoding acceleration of Intel Quick Sync Video may become unavailable when the GPU is in use. If your computer has an NVIDIA GPU, please install the latest Latest NVIDIA drivers for Linux to make sure that Plex can use your NVIDIA graphics card for video encoding (only) when Intel Quick Sync Video becomes unavailable.

Edited by Hoopster
Link to comment
23 minutes ago, Hoopster said:

Short answer it that with a docker running on unRAID, you are limited to Intel iGPU with Quick Sync Video support.

 

Bingo! That's what I thought too.....I often hear a lot of misinformation about this and needed a straight answer. Thanks!

And yes, obviously, if you run a VM and pass a GPU through to the VM successfully....you can do HW acceleration....but that is NOT what we are talking about.

Edited by Stupifier
Link to comment
On 4/20/2018 at 1:09 AM, biiiink said:

I seem to be having an issue with Plex not finding the server

screen_capture04.JPG.57e37e71d555b2a6163705508ec0622c.JPG

 

I was having issues with Plex, and decided to reinstall.  I deleted the Plex docker and deleted the plex folder in the appdata folder.  Reinstalled the plex docker and that is when the issue started.  I've tried the other plex dockers with the same issue.  I've also tried deleting and recreating the docker img file, but I still get the same issue.

 

Here is my plex log:


[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...

-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/


Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donations/
-------------------------------------
GID/UID
-------------------------------------

User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-dbus: executing...
[cont-init.d] 30-dbus: exited 0.
[cont-init.d] 40-chown-files: executing...
[cont-init.d] 40-chown-files: exited 0.
[cont-init.d] 50-plex-update: executing...



#####################################################
# Login via the webui at http://<ip>:32400/web #
# and restart the docker, because there was no #
# plex token found in the preference file #
#####################################################


[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting dbus-daemon
Starting Plex Media Server.
[services.d] done.
dbus[271]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted

Starting Avahi daemon
Found user 'avahi' (UID 106) and group 'avahi' (GID 107).
Successfully dropped root privileges.
avahi-daemon 0.6.32-rc starting up.
No service file found in /etc/avahi/services.
*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***

*** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***

Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
New relevant interface docker0.IPv4 for mDNS.
Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
New relevant interface virbr0.IPv4 for mDNS.
Joining mDNS multicast group on interface br0.IPv6 with address fe80::ba:e1ff:fe91:340d.
New relevant interface br0.IPv6 for mDNS.
Joining mDNS multicast group on interface br0.IPv4 with address 13.13.13.2.
New relevant interface br0.IPv4 for mDNS.
Joining mDNS multicast group on interface bond0.IPv6 with address fe80::92e6:baff:fe2e:d6c9.
New relevant interface bond0.IPv6 for mDNS.
Network interface enumeration completed.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for 192.168.122.1 on virbr0.IPv4.
Registering new address record for fe80::ba:e1ff:fe91:340d on br0.*.
Registering new address record for 13.13.13.2 on br0.IPv4.
Registering new address record for fe80::92e6:baff:fe2e:d6c9 on bond0.*.
Server startup complete. Host name is Titania.local. Local service cookie is 462890458.

 

 

Any more help with my issue would be greatly appreciated

 

Thanks

Link to comment

Hi guys,

 

I've been happily running this container for years now without any problems. I went to use it today and got nothing, so checked the log and it's doing some weird:

 

It all looks good until it actually gets to the line "Starting Plex Media Server", where it just repeats and never starts the server.

 

I'm not sure whether it's something to do with last weekend's build? Though a quick google revealed no other problems out there.

 

Any ideas?

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
usermod: no changes

-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/


Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donations/
-------------------------------------
GID/UID
-------------------------------------

User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-dbus: executing...
[cont-init.d] 30-dbus: exited 0.
[cont-init.d] 40-chown-files: executing...
[cont-init.d] 40-chown-files: exited 0.
[cont-init.d] 50-plex-update: executing...
No update required
[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting Plex Media Server.
[services.d] done.
Starting dbus-daemon
dbus[276]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted
Starting Avahi daemon
Starting Plex Media Server.
Found user 'avahi' (UID 106) and group 'avahi' (GID 107).
Successfully dropped root privileges.
avahi-daemon 0.6.32-rc starting up.
No service file found in /etc/avahi/services.
*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
*** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
Joining mDNS multicast group on interface veth288010d.IPv6 with address fe80::473:83ff:fee3:4a39.
New relevant interface veth288010d.IPv6 for mDNS.
Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
New relevant interface virbr0.IPv4 for mDNS.
Joining mDNS multicast group on interface vethde15982.IPv6 with address fe80::8c7c:13ff:fe06:4d73.
New relevant interface vethde15982.IPv6 for mDNS.
Joining mDNS multicast group on interface vethe43364f.IPv6 with address fe80::a080:87ff:fe0d:1d26.
New relevant interface vethe43364f.IPv6 for mDNS.
Joining mDNS multicast group on interface veth6cfbdfa.IPv6 with address fe80::4a8:42ff:fecf:47e1.
New relevant interface veth6cfbdfa.IPv6 for mDNS.
Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:9fff:fe44:581d.
New relevant interface docker0.IPv6 for mDNS.
Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
New relevant interface docker0.IPv4 for mDNS.
Joining mDNS multicast group on interface br0.IPv6 with address fe80::9c30:56ff:fe9b:fc4e.
New relevant interface br0.IPv6 for mDNS.
Joining mDNS multicast group on interface br0.IPv4 with address 192.168.178.25.
New relevant interface br0.IPv4 for mDNS.
Joining mDNS multicast group on interface eth0.IPv6 with address fe80::7285:c2ff:fe21:72b3.
New relevant interface eth0.IPv6 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::473:83ff:fee3:4a39 on veth288010d.*.
Registering new address record for 192.168.122.1 on virbr0.IPv4.
Registering new address record for fe80::8c7c:13ff:fe06:4d73 on vethde15982.*.
Registering new address record for fe80::a080:87ff:fe0d:1d26 on vethe43364f.*.
Registering new address record for fe80::4a8:42ff:fecf:47e1 on veth6cfbdfa.*.
Registering new address record for fe80::42:9fff:fe44:581d on docker0.*.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for fe80::9c30:56ff:fe9b:fc4e on br0.*.
Registering new address record for 192.168.178.25 on br0.IPv4.
Registering new address record for fe80::7285:c2ff:fe21:72b3 on eth0.*.
Server startup complete. Host name is Apollo.local. Local service cookie is 77526132.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.

 

Link to comment
4 minutes ago, giantkingsquid said:

Hi guys,

 

I've been happily running this container for years now without any problems. I went to use it today and got nothing, so checked the log and it's doing some weird:

 

It all looks good until it actually gets to the line "Starting Plex Media Server", where it just repeats and never starts the server.

 

I'm not sure whether it's something to do with last weekend's build? Though a quick google revealed no other problems out there.

 

Any ideas?


[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
usermod: no changes

-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/


Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donations/
-------------------------------------
GID/UID
-------------------------------------

User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-dbus: executing...
[cont-init.d] 30-dbus: exited 0.
[cont-init.d] 40-chown-files: executing...
[cont-init.d] 40-chown-files: exited 0.
[cont-init.d] 50-plex-update: executing...
No update required
[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting Plex Media Server.
[services.d] done.
Starting dbus-daemon
dbus[276]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted
Starting Avahi daemon
Starting Plex Media Server.
Found user 'avahi' (UID 106) and group 'avahi' (GID 107).
Successfully dropped root privileges.
avahi-daemon 0.6.32-rc starting up.
No service file found in /etc/avahi/services.
*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
*** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
Joining mDNS multicast group on interface veth288010d.IPv6 with address fe80::473:83ff:fee3:4a39.
New relevant interface veth288010d.IPv6 for mDNS.
Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
New relevant interface virbr0.IPv4 for mDNS.
Joining mDNS multicast group on interface vethde15982.IPv6 with address fe80::8c7c:13ff:fe06:4d73.
New relevant interface vethde15982.IPv6 for mDNS.
Joining mDNS multicast group on interface vethe43364f.IPv6 with address fe80::a080:87ff:fe0d:1d26.
New relevant interface vethe43364f.IPv6 for mDNS.
Joining mDNS multicast group on interface veth6cfbdfa.IPv6 with address fe80::4a8:42ff:fecf:47e1.
New relevant interface veth6cfbdfa.IPv6 for mDNS.
Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:9fff:fe44:581d.
New relevant interface docker0.IPv6 for mDNS.
Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
New relevant interface docker0.IPv4 for mDNS.
Joining mDNS multicast group on interface br0.IPv6 with address fe80::9c30:56ff:fe9b:fc4e.
New relevant interface br0.IPv6 for mDNS.
Joining mDNS multicast group on interface br0.IPv4 with address 192.168.178.25.
New relevant interface br0.IPv4 for mDNS.
Joining mDNS multicast group on interface eth0.IPv6 with address fe80::7285:c2ff:fe21:72b3.
New relevant interface eth0.IPv6 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::473:83ff:fee3:4a39 on veth288010d.*.
Registering new address record for 192.168.122.1 on virbr0.IPv4.
Registering new address record for fe80::8c7c:13ff:fe06:4d73 on vethde15982.*.
Registering new address record for fe80::a080:87ff:fe0d:1d26 on vethe43364f.*.
Registering new address record for fe80::4a8:42ff:fecf:47e1 on veth6cfbdfa.*.
Registering new address record for fe80::42:9fff:fe44:581d on docker0.*.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for fe80::9c30:56ff:fe9b:fc4e on br0.*.
Registering new address record for 192.168.178.25 on br0.IPv4.
Registering new address record for fe80::7285:c2ff:fe21:72b3 on eth0.*.
Server startup complete. Host name is Apollo.local. Local service cookie is 77526132.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.

 

 

Post your docker run command please. 

Link to comment

Here you go:

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex' --net='host' -e TZ="Australia/Sydney" -e HOST_OS="unRAID" -e 'PUID'='99' -e 'PGID'='100' -e 'VERSION'='latest' -v '/mnt/user/movies/':'/media':'rw' -v '/tmp':'/transcode':'rw' -v '/mnt/user/appdata/plex':'/config':'rw' 'linuxserver/plex'

bcfff21d0457b684aeda8c996f4c7d3cc3fadd582b5471d5c29b04c27c94ad1a

 

Thanks in advance for any suggestions :)

Link to comment

Is it normal that once installed this, not only takes forever to load a large library, but this also seems to really not like any really large files. To explain, I have part of my library which is average sized (6-10gb) x264 mkv's and it likes those just fine. On the other hand i have a growing number remuxed x264's (25-40gb) and x265 HEVC's (25-50gb 7.1 dolby atmos) and it hartes those.when the library is loading in it freezes sold, and won't get past it. On the other hand I can just go to my htpc and run anything I want from kodi (just none of the features that a media server like plex gives me).

I have messed around with plex and emby since way back and like them both, but plex so far is not liking my collection which is growing towards 46TB at this time. 

 

I just did a complete metadata rewrite for my files with metabrowser (manually - ouch), and upgraded to 6.5.0 unraid. The install is the most recent docker plex by you, installed though the gui. Should i just keep pluging away at it, or am I missing something? 

I just need some pointers I guess.

 

Thanks for all,

Ice

Link to comment
11 hours ago, giantkingsquid said:

Here you go:

 


root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='plex' --net='host' -e TZ="Australia/Sydney" -e HOST_OS="unRAID" -e 'PUID'='99' -e 'PGID'='100' -e 'VERSION'='latest' -v '/mnt/user/movies/':'/media':'rw' -v '/tmp':'/transcode':'rw' -v '/mnt/user/appdata/plex':'/config':'rw' 'linuxserver/plex'

bcfff21d0457b684aeda8c996f4c7d3cc3fadd582b5471d5c29b04c27c94ad1a

 

Thanks in advance for any suggestions :)

 

Change the config mount to /mnt/cache or /mnt/diskX and it should work again. 

Link to comment
16 hours ago, giantkingsquid said:

Hi guys,

 

I've been happily running this container for years now without any problems. I went to use it today and got nothing, so checked the log and it's doing some weird:

 

It all looks good until it actually gets to the line "Starting Plex Media Server", where it just repeats and never starts the server.

 

I'm not sure whether it's something to do with last weekend's build? Though a quick google revealed no other problems out there.

 

Any ideas?


[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
usermod: no changes

-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/


Brought to you by linuxserver.io
We gratefully accept donations at:
https://www.linuxserver.io/donations/
-------------------------------------
GID/UID
-------------------------------------

User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-dbus: executing...
[cont-init.d] 30-dbus: exited 0.
[cont-init.d] 40-chown-files: executing...
[cont-init.d] 40-chown-files: exited 0.
[cont-init.d] 50-plex-update: executing...
No update required
[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting Plex Media Server.
[services.d] done.
Starting dbus-daemon
dbus[276]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted
Starting Avahi daemon
Starting Plex Media Server.
Found user 'avahi' (UID 106) and group 'avahi' (GID 107).
Successfully dropped root privileges.
avahi-daemon 0.6.32-rc starting up.
No service file found in /etc/avahi/services.
*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
*** WARNING: Detected another IPv6 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. ***
Joining mDNS multicast group on interface veth288010d.IPv6 with address fe80::473:83ff:fee3:4a39.
New relevant interface veth288010d.IPv6 for mDNS.
Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
New relevant interface virbr0.IPv4 for mDNS.
Joining mDNS multicast group on interface vethde15982.IPv6 with address fe80::8c7c:13ff:fe06:4d73.
New relevant interface vethde15982.IPv6 for mDNS.
Joining mDNS multicast group on interface vethe43364f.IPv6 with address fe80::a080:87ff:fe0d:1d26.
New relevant interface vethe43364f.IPv6 for mDNS.
Joining mDNS multicast group on interface veth6cfbdfa.IPv6 with address fe80::4a8:42ff:fecf:47e1.
New relevant interface veth6cfbdfa.IPv6 for mDNS.
Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:9fff:fe44:581d.
New relevant interface docker0.IPv6 for mDNS.
Joining mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
New relevant interface docker0.IPv4 for mDNS.
Joining mDNS multicast group on interface br0.IPv6 with address fe80::9c30:56ff:fe9b:fc4e.
New relevant interface br0.IPv6 for mDNS.
Joining mDNS multicast group on interface br0.IPv4 with address 192.168.178.25.
New relevant interface br0.IPv4 for mDNS.
Joining mDNS multicast group on interface eth0.IPv6 with address fe80::7285:c2ff:fe21:72b3.
New relevant interface eth0.IPv6 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::473:83ff:fee3:4a39 on veth288010d.*.
Registering new address record for 192.168.122.1 on virbr0.IPv4.
Registering new address record for fe80::8c7c:13ff:fe06:4d73 on vethde15982.*.
Registering new address record for fe80::a080:87ff:fe0d:1d26 on vethe43364f.*.
Registering new address record for fe80::4a8:42ff:fecf:47e1 on veth6cfbdfa.*.
Registering new address record for fe80::42:9fff:fe44:581d on docker0.*.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for fe80::9c30:56ff:fe9b:fc4e on br0.*.
Registering new address record for 192.168.178.25 on br0.IPv4.
Registering new address record for fe80::7285:c2ff:fe21:72b3 on eth0.*.
Server startup complete. Host name is Apollo.local. Local service cookie is 77526132.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.

 

 Plex is crashing for you. Could be corrupt database. Check the plex media server logs in your config folder. That should tell you the reason for the crash

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.