[Support] Linuxserver.io - Plex Media Server


Recommended Posts

@mrbilky

 

Get rid of your plex appdata, remove the container and the image and reinstall.  On the FIRST install, post your logs and your docker run command like I have below

 

docker run -d --name='plex' --net='host' -e TZ="Europe/London" -e HOST_OS="unRAID" -e 'PUID'='99' -e 'PGID'='100' -e 'VERSION'='latest' -v '/mnt/user/movies/':'/movies':'rw' -v '/mnt/user/tv/':'/tv':'rw' -v '/mnt/user/music/':'/music':'rw' -v '/mnt/disks/virtualisation/.appdata/plex-test':'/config':'rw,slave' 'linuxserver/plex'
[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 #
# preference file found, possibly first startup. #
#####################################################


[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[272]: [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 virbr0.IPv4 with address 192.168.122.1.
New relevant interface virbr0.IPv4 for mDNS.
Joining mDNS multicast group on interface veth73d18bc.IPv6 with address fe80::b0b3:3ff:feef:8ad4.
New relevant interface veth73d18bc.IPv6 for mDNS.
Joining mDNS multicast group on interface veth0c26bb0.IPv6 with address fe80::a88a:5cff:fe98:6b73.
New relevant interface veth0c26bb0.IPv6 for mDNS.
Joining mDNS multicast group on interface veth6e2d851.IPv6 with address fe80::2c7b:85ff:fe87:48d.
New relevant interface veth6e2d851.IPv6 for mDNS.
Joining mDNS multicast group on interface veth0b7125d.IPv6 with address fe80::801e:31ff:fede:bc8f.
New relevant interface veth0b7125d.IPv6 for mDNS.
Joining mDNS multicast group on interface vethe473a31.IPv6 with address fe80::f046:5bff:fecd:f333.
New relevant interface vethe473a31.IPv6 for mDNS.
Joining mDNS multicast group on interface vethc0ba8de.IPv6 with address fe80::1493:67ff:feaf:f9c4.
New relevant interface vethc0ba8de.IPv6 for mDNS.
Joining mDNS multicast group on interface veth023105f.IPv6 with address fe80::fc7a:3fff:fe08:b9bd.
New relevant interface veth023105f.IPv6 for mDNS.
Joining mDNS multicast group on interface veth3f99e43.IPv6 with address fe80::3c4c:dff:fe71:c4d7.
New relevant interface veth3f99e43.IPv6 for mDNS.
Joining mDNS multicast group on interface veth011c810.IPv6 with address fe80::f41b:7eff:fef4:7e16.
New relevant interface veth011c810.IPv6 for mDNS.
Joining mDNS multicast group on interface veth04bd526.IPv6 with address fe80::1c8a:63ff:fe45:49e7.
New relevant interface veth04bd526.IPv6 for mDNS.
Joining mDNS multicast group on interface veth16dee29.IPv6 with address fe80::c89b:17ff:fefe:96f0.
New relevant interface veth16dee29.IPv6 for mDNS.
Joining mDNS multicast group on interface vethe1a3273.IPv6 with address fe80::84e:3aff:fedc:b39a.
New relevant interface vethe1a3273.IPv6 for mDNS.
Joining mDNS multicast group on interface veth23bb0b2.IPv6 with address fe80::5099:eff:fe51:62eb.
New relevant interface veth23bb0b2.IPv6 for mDNS.
Joining mDNS multicast group on interface vethe0abaf8.IPv6 with address fe80::4461:79ff:fe8a:8fbd.
New relevant interface vethe0abaf8.IPv6 for mDNS.
Joining mDNS multicast group on interface veth51892a4.IPv6 with address fe80::60e2:eaff:febd:c4d2.
New relevant interface veth51892a4.IPv6 for mDNS.
Joining mDNS multicast group on interface veth21785d9.IPv6 with address fe80::6880:a5ff:fe8a:c531.
New relevant interface veth21785d9.IPv6 for mDNS.
Joining mDNS multicast group on interface veth47495d9.IPv6 with address fe80::742c:dfff:fe01:8c4d.
New relevant interface veth47495d9.IPv6 for mDNS.
Joining mDNS multicast group on interface veth3e45e33.IPv6 with address fe80::5c5c:2bff:fe15:c63f.
New relevant interface veth3e45e33.IPv6 for mDNS.
Joining mDNS multicast group on interface veth78c341e.IPv6 with address fe80::14e9:4fff:fed7:5345.
New relevant interface veth78c341e.IPv6 for mDNS.
Joining mDNS multicast group on interface vethf035633.IPv6 with address fe80::c004:6fff:fe9a:65fe.
New relevant interface vethf035633.IPv6 for mDNS.
Joining mDNS multicast group on interface vethafd8338.IPv6 with address fe80::ec3b:3aff:fe58:a5ab.
New relevant interface vethafd8338.IPv6 for mDNS.
Joining mDNS multicast group on interface veth0d2e265.IPv6 with address fe80::9c42:45ff:fed9:679e.
New relevant interface veth0d2e265.IPv6 for mDNS.
Joining mDNS multicast group on interface vethe6803dd.IPv6 with address fe80::c00b:5ff:fe22:a48a.
New relevant interface vethe6803dd.IPv6 for mDNS.
Joining mDNS multicast group on interface veth241b8af.IPv6 with address fe80::906d:87ff:feba:a655.
New relevant interface veth241b8af.IPv6 for mDNS.
Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:aeff:fe47:1dd2.
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::5c97:34ff:fe2d:f7b9.
New relevant interface br0.IPv6 for mDNS.
Joining mDNS multicast group on interface br0.IPv4 with address 192.168.0.1.
New relevant interface br0.IPv4 for mDNS.
Joining mDNS multicast group on interface eth0.IPv6 with address fe80::ae1f:6bff:fe1b:4d76.
New relevant interface eth0.IPv6 for mDNS.
Network interface enumeration completed.
Registering new address record for 192.168.122.1 on virbr0.IPv4.
Registering new address record for fe80::b0b3:3ff:feef:8ad4 on veth73d18bc.*.
Registering new address record for fe80::a88a:5cff:fe98:6b73 on veth0c26bb0.*.
Registering new address record for fe80::2c7b:85ff:fe87:48d on veth6e2d851.*.
Registering new address record for fe80::801e:31ff:fede:bc8f on veth0b7125d.*.
Registering new address record for fe80::f046:5bff:fecd:f333 on vethe473a31.*.
Registering new address record for fe80::1493:67ff:feaf:f9c4 on vethc0ba8de.*.
Registering new address record for fe80::fc7a:3fff:fe08:b9bd on veth023105f.*.
Registering new address record for fe80::3c4c:dff:fe71:c4d7 on veth3f99e43.*.
Registering new address record for fe80::f41b:7eff:fef4:7e16 on veth011c810.*.
Registering new address record for fe80::1c8a:63ff:fe45:49e7 on veth04bd526.*.
Registering new address record for fe80::c89b:17ff:fefe:96f0 on veth16dee29.*.
Registering new address record for fe80::84e:3aff:fedc:b39a on vethe1a3273.*.
Registering new address record for fe80::5099:eff:fe51:62eb on veth23bb0b2.*.
Registering new address record for fe80::4461:79ff:fe8a:8fbd on vethe0abaf8.*.
Registering new address record for fe80::60e2:eaff:febd:c4d2 on veth51892a4.*.
Registering new address record for fe80::6880:a5ff:fe8a:c531 on veth21785d9.*.
Registering new address record for fe80::742c:dfff:fe01:8c4d on veth47495d9.*.
Registering new address record for fe80::5c5c:2bff:fe15:c63f on veth3e45e33.*.
Registering new address record for fe80::14e9:4fff:fed7:5345 on veth78c341e.*.
Registering new address record for fe80::c004:6fff:fe9a:65fe on vethf035633.*.
Registering new address record for fe80::ec3b:3aff:fe58:a5ab on vethafd8338.*.
Registering new address record for fe80::9c42:45ff:fed9:679e on veth0d2e265.*.
Registering new address record for fe80::c00b:5ff:fe22:a48a on vethe6803dd.*.
Registering new address record for fe80::906d:87ff:feba:a655 on veth241b8af.*.
Registering new address record for fe80::42:aeff:fe47:1dd2 on docker0.*.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for fe80::5c97:34ff:fe2d:f7b9 on br0.*.
Registering new address record for 192.168.0.1 on br0.IPv4.
Registering new address record for fe80::ae1f:6bff:fe1b:4d76 on eth0.*.

 

Link to comment
23 minutes ago, CHBMB said:

@mrbilky

 

Get rid of your plex appdata, remove the container and the image and reinstall.  On the FIRST install, post your logs and your docker run command like I have below

 


docker run -d --name='plex' --net='host' -e TZ="Europe/London" -e HOST_OS="unRAID" -e 'PUID'='99' -e 'PGID'='100' -e 'VERSION'='latest' -v '/mnt/user/movies/':'/movies':'rw' -v '/mnt/user/tv/':'/tv':'rw' -v '/mnt/user/music/':'/music':'rw' -v '/mnt/disks/virtualisation/.appdata/plex-test':'/config':'rw,slave' 'linuxserver/plex'

[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 #
# preference file found, possibly first startup. #
#####################################################


[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[272]: [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 virbr0.IPv4 with address 192.168.122.1.
New relevant interface virbr0.IPv4 for mDNS.
Joining mDNS multicast group on interface veth73d18bc.IPv6 with address fe80::b0b3:3ff:feef:8ad4.
New relevant interface veth73d18bc.IPv6 for mDNS.
Joining mDNS multicast group on interface veth0c26bb0.IPv6 with address fe80::a88a:5cff:fe98:6b73.
New relevant interface veth0c26bb0.IPv6 for mDNS.
Joining mDNS multicast group on interface veth6e2d851.IPv6 with address fe80::2c7b:85ff:fe87:48d.
New relevant interface veth6e2d851.IPv6 for mDNS.
Joining mDNS multicast group on interface veth0b7125d.IPv6 with address fe80::801e:31ff:fede:bc8f.
New relevant interface veth0b7125d.IPv6 for mDNS.
Joining mDNS multicast group on interface vethe473a31.IPv6 with address fe80::f046:5bff:fecd:f333.
New relevant interface vethe473a31.IPv6 for mDNS.
Joining mDNS multicast group on interface vethc0ba8de.IPv6 with address fe80::1493:67ff:feaf:f9c4.
New relevant interface vethc0ba8de.IPv6 for mDNS.
Joining mDNS multicast group on interface veth023105f.IPv6 with address fe80::fc7a:3fff:fe08:b9bd.
New relevant interface veth023105f.IPv6 for mDNS.
Joining mDNS multicast group on interface veth3f99e43.IPv6 with address fe80::3c4c:dff:fe71:c4d7.
New relevant interface veth3f99e43.IPv6 for mDNS.
Joining mDNS multicast group on interface veth011c810.IPv6 with address fe80::f41b:7eff:fef4:7e16.
New relevant interface veth011c810.IPv6 for mDNS.
Joining mDNS multicast group on interface veth04bd526.IPv6 with address fe80::1c8a:63ff:fe45:49e7.
New relevant interface veth04bd526.IPv6 for mDNS.
Joining mDNS multicast group on interface veth16dee29.IPv6 with address fe80::c89b:17ff:fefe:96f0.
New relevant interface veth16dee29.IPv6 for mDNS.
Joining mDNS multicast group on interface vethe1a3273.IPv6 with address fe80::84e:3aff:fedc:b39a.
New relevant interface vethe1a3273.IPv6 for mDNS.
Joining mDNS multicast group on interface veth23bb0b2.IPv6 with address fe80::5099:eff:fe51:62eb.
New relevant interface veth23bb0b2.IPv6 for mDNS.
Joining mDNS multicast group on interface vethe0abaf8.IPv6 with address fe80::4461:79ff:fe8a:8fbd.
New relevant interface vethe0abaf8.IPv6 for mDNS.
Joining mDNS multicast group on interface veth51892a4.IPv6 with address fe80::60e2:eaff:febd:c4d2.
New relevant interface veth51892a4.IPv6 for mDNS.
Joining mDNS multicast group on interface veth21785d9.IPv6 with address fe80::6880:a5ff:fe8a:c531.
New relevant interface veth21785d9.IPv6 for mDNS.
Joining mDNS multicast group on interface veth47495d9.IPv6 with address fe80::742c:dfff:fe01:8c4d.
New relevant interface veth47495d9.IPv6 for mDNS.
Joining mDNS multicast group on interface veth3e45e33.IPv6 with address fe80::5c5c:2bff:fe15:c63f.
New relevant interface veth3e45e33.IPv6 for mDNS.
Joining mDNS multicast group on interface veth78c341e.IPv6 with address fe80::14e9:4fff:fed7:5345.
New relevant interface veth78c341e.IPv6 for mDNS.
Joining mDNS multicast group on interface vethf035633.IPv6 with address fe80::c004:6fff:fe9a:65fe.
New relevant interface vethf035633.IPv6 for mDNS.
Joining mDNS multicast group on interface vethafd8338.IPv6 with address fe80::ec3b:3aff:fe58:a5ab.
New relevant interface vethafd8338.IPv6 for mDNS.
Joining mDNS multicast group on interface veth0d2e265.IPv6 with address fe80::9c42:45ff:fed9:679e.
New relevant interface veth0d2e265.IPv6 for mDNS.
Joining mDNS multicast group on interface vethe6803dd.IPv6 with address fe80::c00b:5ff:fe22:a48a.
New relevant interface vethe6803dd.IPv6 for mDNS.
Joining mDNS multicast group on interface veth241b8af.IPv6 with address fe80::906d:87ff:feba:a655.
New relevant interface veth241b8af.IPv6 for mDNS.
Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:aeff:fe47:1dd2.
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::5c97:34ff:fe2d:f7b9.
New relevant interface br0.IPv6 for mDNS.
Joining mDNS multicast group on interface br0.IPv4 with address 192.168.0.1.
New relevant interface br0.IPv4 for mDNS.
Joining mDNS multicast group on interface eth0.IPv6 with address fe80::ae1f:6bff:fe1b:4d76.
New relevant interface eth0.IPv6 for mDNS.
Network interface enumeration completed.
Registering new address record for 192.168.122.1 on virbr0.IPv4.
Registering new address record for fe80::b0b3:3ff:feef:8ad4 on veth73d18bc.*.
Registering new address record for fe80::a88a:5cff:fe98:6b73 on veth0c26bb0.*.
Registering new address record for fe80::2c7b:85ff:fe87:48d on veth6e2d851.*.
Registering new address record for fe80::801e:31ff:fede:bc8f on veth0b7125d.*.
Registering new address record for fe80::f046:5bff:fecd:f333 on vethe473a31.*.
Registering new address record for fe80::1493:67ff:feaf:f9c4 on vethc0ba8de.*.
Registering new address record for fe80::fc7a:3fff:fe08:b9bd on veth023105f.*.
Registering new address record for fe80::3c4c:dff:fe71:c4d7 on veth3f99e43.*.
Registering new address record for fe80::f41b:7eff:fef4:7e16 on veth011c810.*.
Registering new address record for fe80::1c8a:63ff:fe45:49e7 on veth04bd526.*.
Registering new address record for fe80::c89b:17ff:fefe:96f0 on veth16dee29.*.
Registering new address record for fe80::84e:3aff:fedc:b39a on vethe1a3273.*.
Registering new address record for fe80::5099:eff:fe51:62eb on veth23bb0b2.*.
Registering new address record for fe80::4461:79ff:fe8a:8fbd on vethe0abaf8.*.
Registering new address record for fe80::60e2:eaff:febd:c4d2 on veth51892a4.*.
Registering new address record for fe80::6880:a5ff:fe8a:c531 on veth21785d9.*.
Registering new address record for fe80::742c:dfff:fe01:8c4d on veth47495d9.*.
Registering new address record for fe80::5c5c:2bff:fe15:c63f on veth3e45e33.*.
Registering new address record for fe80::14e9:4fff:fed7:5345 on veth78c341e.*.
Registering new address record for fe80::c004:6fff:fe9a:65fe on vethf035633.*.
Registering new address record for fe80::ec3b:3aff:fe58:a5ab on vethafd8338.*.
Registering new address record for fe80::9c42:45ff:fed9:679e on veth0d2e265.*.
Registering new address record for fe80::c00b:5ff:fe22:a48a on vethe6803dd.*.
Registering new address record for fe80::906d:87ff:feba:a655 on veth241b8af.*.
Registering new address record for fe80::42:aeff:fe47:1dd2 on docker0.*.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for fe80::5c97:34ff:fe2d:f7b9 on br0.*.
Registering new address record for 192.168.0.1 on br0.IPv4.
Registering new address record for fe80::ae1f:6bff:fe1b:4d76 on eth0.*.

 

 

 

Here it is but I had to stop the docker or it would just keep posting "Starting Plex Media Server."

 

[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 #
# preference file found, possibly first startup. #
#####################################################


[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting Plex Media Server.
Starting dbus-daemon
[services.d] done.
dbus[271]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted
Starting Plex Media Server.
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 veth51be318.IPv6 with address fe80::204e:f2ff:febe:a047.
New relevant interface veth51be318.IPv6 for mDNS.
Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:40ff:fe25:e4ec.
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 eth2.IPv4 with address 192.168.51.2.
New relevant interface eth2.IPv4 for mDNS.
Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.50.2.
New relevant interface eth1.IPv4 for mDNS.
Joining mDNS multicast group on interface eth0.IPv6 with address fe80::ec4:7aff:fe81:28d3.
New relevant interface eth0.IPv6 for mDNS.
Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.154.
New relevant interface eth0.IPv4 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::204e:f2ff:febe:a047 on veth51be318.*.
Registering new address record for fe80::42:40ff:fe25:e4ec on docker0.*.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for 192.168.51.2 on eth2.IPv4.
Registering new address record for 192.168.50.2 on eth1.IPv4.
Registering new address record for fe80::ec4:7aff:fe81:28d3 on eth0.*.
Registering new address record for 192.168.1.154 on eth0.IPv4.
Starting Plex Media Server.
Server startup complete. Host name is homeNAS.local. Local service cookie is 7152946.
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.
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.
Got SIGTERM, quitting.
Leaving mDNS multicast group on interface veth51be318.IPv6 with address fe80::204e:f2ff:febe:a047.
Leaving mDNS multicast group on interface docker0.IPv6 with address fe80::42:40ff:fe25:e4ec.
Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Leaving mDNS multicast group on interface eth2.IPv4 with address 192.168.51.2.
Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.50.2.
Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::ec4:7aff:fe81:28d3.
Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.154.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
avahi-daemon 0.6.32-rc exiting.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

Link to comment
Just now, aptalca said:

If it's repeating "Starting Plex Media Server." that means plex is crashing and is restarted by the container.

 

Check the plex server logs in your config folder. Likely a corrupt database.

 

Was a fresh pull...... or at least that's what I asked for...

Link to comment
15 minutes ago, CHBMB said:

 

Was a fresh pull...... or at least that's what I asked for...

Yep it was its identical or so it appears as the first one I posted think I'll go to the extreme of pulling my 10GB nic is that is the only hardware change made to this and I had plex running on this server without issue several times when I first built it guess I should have left well enough alone but I was trying too many things at once and getting bogged down so I removed all but what I needed at the time the only other change is the updates anyone have the link to older versions namely 6.3.5 that was the version it ran on

Link to comment
4 hours ago, CHBMB said:

 

Err, no, look at my signature and it'll show you what I mean.....

Quote

 

Stopping container: plex

Error: Error code

Removing container: plex

Successfully removed container 'plex'

Command:root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="plex" --net="host" -e TZ="America/Phoenix" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -e "VERSION"="latest" -v "/mnt/user/My Movies/":"/Movies":rw -v "/mnt/user/TV/":"/Television":rw -v "/mnt/user/appdata/plex":"/config":rw linuxserver/plex

37f2d2020bd4f96c1835da0f6eacb624de29039539e8df068c7d097216786309

The command finished successfully!

 

Quote

 

ErrorWarningSystemArrayLogin

[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[273]: [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. ***
socket() failed: Address family not supported by protocol
Failed to create IPv6 socket, proceeding in IPv4 only mode
socket() failed: Address family not supported by protocol
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 eth0.IPv4 with address 192.168.1.199.
New relevant interface eth0.IPv4 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.1.199 on eth0.IPv4.
Server startup complete. Host name is Whoshouse.local. Local service cookie is 2897057835.
Sqlite3: Sleeping for 200ms to retry busy DB.

Disconnected from D-Bus, exiting.
Got SIGTERM, quitting.
Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.199.
avahi-daemon 0.6.32-rc exiting.
Sq[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
Critical: libusb_init failed
[s6-finish] sending all processes the KILL signal and exiting.
[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.
Starting dbus-daemon
[services.d] done.
dbus[278]: [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. ***
socket() failed: Address family not supported by protocol
Failed to create IPv6 socket, proceeding in IPv4 only mode
socket() failed: Address family not supported by protocol
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 eth0.IPv4 with address 192.168.1.199.
New relevant interface eth0.IPv4 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.1.199 on eth0.IPv4.
Server startup complete. Host name is Whoshouse.local. Local service cookie is 4190026496.
Connection to 184.105.148.104 closed by remote host.
e":"No such container: 36a8dde0ff30"}

 

running the risk at being wrong because that link talked about two things even though one was specifically saying docker command ill post both ha ha.. but it is working as of right now since we deleted app data and reinstalled the docker. i dont know if you caught that or if you requested this info for something else. thanks!!!

Link to comment
31 minutes ago, carlos28355 said:

running the risk at being wrong because that link talked about two things even though one was specifically saying docker command ill post both ha ha.. but it is working as of right now since we deleted app data and reinstalled the docker. i dont know if you caught that or if you requested this info for something else. thanks!!!

 

You rebooted yet?

 

Link to comment

Docker stopped working for me now :(

Yesterday I got some messages about full docker image.. And today Plex and a few others did not work.

Tried restarting all dockers, and they started working.. But not Plex :(

 

Tried a reboot, and also stopping and starting docker service, and also expand image to 25GB.

 

Nothing worked.. I then did a backup of docker image, and deleted it, an set up plex again.. Same issue..

It shows up as running, but in the log it is spammed with "starting plex"

 

Krusader is also not working as it should.. I can start it and connect to web-ui.. but freezes when I try to start a session.

 

Any tips?

I'm not very good at dockers.. But I try my best ;)

 

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...
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 dbus-daemon
Starting Plex Media Server.
[services.d] done.
Starting Plex Media Server.
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 veth8b87479.IPv6 with address fe80::c450:a4ff:fe21:a90b.
New relevant interface veth8b87479.IPv6 for mDNS.
Joining mDNS multicast group on interface veth642ac2b.IPv6 with address fe80::b43e:e2ff:fe65:f723.
New relevant interface veth642ac2b.IPv6 for mDNS.
Joining mDNS multicast group on interface vethf8591d6.IPv6 with address fe80::e49c:46ff:fe36:e16f.
New relevant interface vethf8591d6.IPv6 for mDNS.
Joining mDNS multicast group on interface vethc54da26.IPv6 with address fe80::7484:a5ff:fe06:4f8e.
New relevant interface vethc54da26.IPv6 for mDNS.
Joining mDNS multicast group on interface docker0.IPv6 with address fe80::42:4dff:fef0:ae66.
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 vnet1.IPv6 with address fe80::fc54:ff:fed9:40c3.
New relevant interface vnet1.IPv6 for mDNS.
Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe5b:8375.
New relevant interface vnet0.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 br0.IPv6 with address 2a01:79d:469e:c0a0:d250:99ff:fe3b:7cab.
New relevant interface br0.IPv6 for mDNS.
Joining mDNS multicast group on interface br0.IPv4 with address 192.168.10.10.
New relevant interface br0.IPv4 for mDNS.
Joining mDNS multicast group on interface eth0.IPv6 with address fe80::d250:99ff:fe3b:7cab.
New relevant interface eth0.IPv6 for mDNS.
Network interface enumeration completed.
Registering new address record for fe80::c450:a4ff:fe21:a90b on veth8b87479.*.
Registering new address record for fe80::b43e:e2ff:fe65:f723 on veth642ac2b.*.
Registering new address record for fe80::e49c:46ff:fe36:e16f on vethf8591d6.*.
Registering new address record for fe80::7484:a5ff:fe06:4f8e on vethc54da26.*.
Registering new address record for fe80::42:4dff:fef0:ae66 on docker0.*.
Registering new address record for 172.17.0.1 on docker0.IPv4.
Registering new address record for fe80::fc54:ff:fed9:40c3 on vnet1.*.
Registering new address record for fe80::fc54:ff:fe5b:8375 on vnet0.*.
Registering new address record for 192.168.122.1 on virbr0.IPv4.
Registering new address record for 2a01:79d:469e:c0a0:d250:99ff:fe3b:7cab on br0.*.
Registering new address record for 192.168.10.10 on br0.IPv4.
Registering new address record for fe80::d250:99ff:fe3b:7cab on eth0.*.
Server startup complete. Host name is unRAID.local. Local service cookie is 3700525280.
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.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.

Edited by Ja9
attached log from plex docker
Link to comment

Has anyone ever experienced Plex not loading the proper Metadata for certain scanned playlists?  My plex server is setup and all of my Movie playlists have been properly scanned and the thumbnails loaded and applied, but in my TV playlist only a quarter have been properly scanner and the rest are blank and even when doing manually not proper title or thumbnails are applied.

Link to comment
4 hours ago, trurl said:

What did you do with the backup? There is no point in backing it up since you can't restore it and it was corrupt anyway.

I did a backup just to have it.

I have some other dockers running to.. one of them is delugevpn, and it is currently downloading some big files ;)
So, i just copyed the image back, when I had testet a fresh install of Plex.
The backup copy worked just fine for the other dockers, so they are up again.

Only Plex and Krusader that has problems.

Link to comment
9 minutes ago, TheBawse said:

Has anyone ever experienced Plex not loading the proper Metadata for certain scanned playlists?  My plex server is setup and all of my Movie playlists have been properly scanned and the thumbnails loaded and applied, but in my TV playlist only a quarter have been properly scanner and the rest are blank and even when doing manually not proper title or thumbnails are applied.

Sounds like a question for the plex forums. How long have you been using Plex?

 

Plus, you haven't really given us any details about what you have done. Plex tries to match movies and shows to online databases but it can have trouble matching those databases with the way you have named your files/folders. If one database doesn't match, you can get it to try another.

 

But, we don't have any plex developers here. This thread is mostly about how to get this particular plex docker setup and running.

 

And there are more plex users on the plex forums than here so maybe those forums are better suited to answer questions about how to actually use plex.

Link to comment
1 minute ago, Ja9 said:

I did a backup just to have it.

I have some other dockers running to.. one of them is delugevpn, and it is currently downloading some big files ;)
So, i just copyed the image back, when I had testet a fresh install of Plex.
The backup copy worked just fine for the other dockers, so they are up again.

Only Plex and Krusader that has problems.

 

This is not the way you should reinstall your dockers.

 

You should delete docker.img, recreate it from scratch, then reinstall your dockers from Community Applications - Previous Apps. All the settings from your dockers are saved on flash and Previous Apps will use those settings. Then you will get fresh copies of the applications, but they will use the application data you already have.

Link to comment

I was not shure if deluge would find the torrents again.. Thats why I did it that way.

But I did re-create Plex from scratch after I deleted the docker.img.. It did not help.
Then I deleted the docker.img again, and copyed back the backup I did make.

Link to comment
2 hours ago, trurl said:

Sounds like a question for the plex forums. How long have you been using Plex?

 

Plus, you haven't really given us any details about what you have done. Plex tries to match movies and shows to online databases but it can have trouble matching those databases with the way you have named your files/folders. If one database doesn't match, you can get it to try another.

 

But, we don't have any plex developers here. This thread is mostly about how to get this particular plex docker setup and running.

 

And there are more plex users on the plex forums than here so maybe those forums are better suited to answer questions about how to actually use plex.

Thanks.  I just started using it.  The issue i'm having is even when I attempt to manually add metadata through searching on the various databases available it won't apply it to the media in question.  e.g: simpsons.  I search on tvdb...find it...tell plex to apply it...and no thumbnails or episode title are applied.  Weird thing is for movies there are no metedata issues plex found most of them and added thumbnails and titles, and for the ones it couldn't find i was able to apply manually.  its just tv shows that won't work.

Another question.  If I wanted to start again from scratch.  How would I go about removing plexserver along with all of the files and docker container off the share its using and start over? 100% clean re-install

Thanks

Edited by TheBawse
Link to comment
3 minutes ago, TheBawse said:

Thanks.  I just started using it.  The issue i'm having is even when I attempt to manually add metadata through searching on the various databases available it won't apply it to the media in question.  e.g: simpsons.  I search on tvdb...find it...tell plex to apply it...and no thumbnails or episode title are applied.  Weird thing is for movies there are no metedata issues plex found most of them and added thumbnails and titles, and for the ones it couldn't find i was able to apply manually.  its just tv shows that won't work.

Another question.  If I wanted to start again from scratch.  How would I go about removing plexserver along with all of the files and docker container off the share its using and start over? 100% clean re-install

Thanks

For an absolutely clean install you would go to dockers, click the logo and select “Remove”. You should also be prompted to remove the image file. Go to your appdata folder (probably cache/appdata) and delete the Plex folder.

Link to comment

Hi guys, after bit of help - thought I'd try here before heading over the the Plex forums.

 

Just started my server up after 6 months in storage. Everything is fine, but Plex isn't seeing the server. I can fire up [ip]:32400 but I just get taken to one of my other plex servers and unPlex doesn't appear in the list

 

The only workaround I can find is to go to devices-->server where it does list the unPlex device as being recently active. If I remove it, restart the Plex docker - bam, I can see the server and it prompts me to claim it.

 

However, as soon as I claim it, it disappears again and I have to repeat the process.

 

Any thoughts on what I can do to stop the cycle?

 

Thanks!

Link to comment

Still having issues getting into Plex. I can claim / unclaim - but as soon as I claim, the server becomes unavailable.

- I've tried removing recommended fields from the preferences.xml file

- I've tried removing the entire preferences.xml file and going through the basic setup process again

- I've tried removing the docker.img file

- I've gone ahead with the 6.3.5-->6.4.1 unRaid update

 

Occasionally (depending on what I click on once I've tried claiming), I do get the message...


 

Quote

 

No soup for you!

The server you're trying to access doesn't want to let you in. Make sure you're signed in as a user with access to this server.


 

 

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.