December 31, 20169 yr ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/index.php/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. 6 3000 /config/Library/Application Support d 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 virbr0.IPv4 with address 192.168.122.1. New relevant interface virbr0.IPv4 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.IPv4 with address 10.11.12.200. New relevant interface br0.IPv4 for mDNS. Network interface enumeration completed. Registering new address record for 192.168.122.1 on virbr0.IPv4. Registering new address record for 172.17.0.1 on docker0.IPv4. Registering new address record for 10.11.12.200 on br0.IPv4. Server startup complete. Host name is nerdyRAID.local. Local service cookie is 1948580408. Starting Plex Media Server. 6 3000 /config/Library/Application Support d Starting Plex Media Server. 6 3000 /config/Library/Application Support d Starting Plex Media Server. 6 3000 /config/Library/Application Support d Starting Plex Media Server. 6 3000 /config/Library/Application Support d Starting Plex Media Server. 6 3000 /config/Library/Application Support d Starting Plex Media Server. 6 3000 /config/Library/Application Support ... Until I stop docker... and it exits cleanly. It seems like permissions are being denied?
December 31, 20169 yr You got teamviewer? Ever since their breach...and leak of user data, I have been loathe to use teamviewer. I know, i am overtly paranoid.
December 31, 20169 yr Then I only have my previous suggestion regarding appdata, docker image and container.
December 31, 20169 yr Sorry for double post... My brain clicked... it was hanging on looking for config, thats why the log was full of /config/ over and over again. I did not point the config path correctly. Stopped image. Cleared data. removed image. Reinstalled. Pointed paths correctly... and we are good to go. Thanks! Appreciate everyone's patience.
December 31, 20169 yr Sorry for double post... My brain clicked... it was hanging on looking for config, thats why the log was full of /config/ over and over again. I did not point the config path correctly. Stopped image. Cleared data. removed image. Reinstalled. Pointed paths correctly... and we are good to go. Thanks! Appreciate everyone's patience. It was defined correctly in your original docker run command.
December 31, 20169 yr I was hoping someone could shed some insight into why I am having a strange error. Just recently installed the Plex Docker (have run it in the past for year, just not on unRAID) .. Everything is working correctly, but he Plex Trans+ process is running at about 450% CPU usage. No one is transcoding anything right now. I have no idea why this process is running and why it is running so high. No Libraries are updating. All the media is new, but I have turned off "live thumbnail creation" as I thought that might be causing it. Has anyone experienced this before? thanks!
January 1, 20179 yr Sorry for double post... My brain clicked... it was hanging on looking for config, thats why the log was full of /config/ over and over again. I did not point the config path correctly. Stopped image. Cleared data. removed image. Reinstalled. Pointed paths correctly... and we are good to go. Thanks! Appreciate everyone's patience. It was defined correctly in your original docker run command. Yeah... I borked it, when changing cache preference.
January 1, 20179 yr I am having problems with plex media server (the server is not connecting and i don't have a server tab, also the port 32400 shows up red in the deployed hosts when i click edit) I have tried host and bridge mode. I have had previous installs of dockers of plex and switched to linuxserver a while ago. I am thinking of clean installing plex media server, but from what i read i will have to delete the docker image, i also have the following dockers working well (deluge, nzget,sabnzbd,sonarr and sickrage)- Would deleting the docker.img mess all that up? I am attaching my log from the docker if anyone wants to have a look and advise me. Thanks in advance. log_2.txt
January 1, 20179 yr I am having problems with plex media server (the server is not connecting and i don't have a server tab, also the port 32400 shows up red in the deployed hosts when i click edit) I have tried host and bridge mode. I have had previous installs of dockers of plex and switched to linuxserver a while ago. I am thinking of clean installing plex media server, but from what i read i will have to delete the docker image, i also have the following dockers working well (deluge, nzget,sabnzbd,sonarr and sickrage)- Would deleting the docker.img mess all that up? I am attaching my log from the docker if anyone wants to have a look and advise me. Thanks in advance. same here, port seems to be gone from the plex container for some reason right now.
January 1, 20179 yr My Plex docker that has worked for months stopped around 12:07AM so a little while after the latest update as I have my dockers auto update nightly. It won't start and I cannot really see where to get logs from as the usual log remains empty. I'll report back if I find anything. EDIT: Resolved the issue.
January 1, 20179 yr I've posted earlier in here about general lockups and I have more info. Off a clean shutdown and reboot of the system I'm seeing the following in my plex container docker log when starting it: ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/index.php/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. Starting Avahi daemon [services.d] done. 6 3000 /config/Library/Application Support d Daemon already running on PID 277 dbus[277]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted 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. Starting Avahi daemon [services.d] done. 6 3000 /config/Library/Application Support d Daemon already running on PID 277 dbus[277]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Those last lines will repeat until I kill it. Things I've done to this point in an effort to pinpoint the random lockups (where I can ping host but not SSH or get webgui functionality): Full memtest multiple times and for 24 hours plus runs. Removed and rebuilt docker.img multiple times. Running Plex and only Plex docker. Set CPU variable to only use anywhere from 6 down to 3 cores (out of 8 ). Replaced power supply thinking perhaps not enough on the +12v. I just can't stay stable for more than 24 hours with Plex running. At this point I'm ready to replace my hardware (Xeon x3470 on Supermicro X8SIL so it's pretty old) with new hardware in an effort to resolve these months of hard resets and reboots. I've attached my diagnostics log here in the hope it might shed some light--appreciate any feedback! diagnostics-20170101-1140.zip
January 1, 20179 yr I've posted earlier in here about general lockups and I have more info. Off a clean shutdown and reboot of the system I'm seeing the following in my plex container docker log when starting it: ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/index.php/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. Starting Avahi daemon [services.d] done. 6 3000 /config/Library/Application Support d Daemon already running on PID 277 dbus[277]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted 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. Starting Avahi daemon [services.d] done. 6 3000 /config/Library/Application Support d Daemon already running on PID 277 dbus[277]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Those last lines will repeat until I kill it. Things I've done to this point in an effort to pinpoint the random lockups (where I can ping host but not SSH or get webgui functionality): Full memtest multiple times and for 24 hours plus runs. Removed and rebuilt docker.img multiple times. Running Plex and only Plex docker. Set CPU variable to only use anywhere from 6 down to 3 cores (out of 8 ). Replaced power supply thinking perhaps not enough on the +12v. I just can't stay stable for more than 24 hours with Plex running. At this point I'm ready to replace my hardware (Xeon x3470 on Supermicro X8SIL so it's pretty old) with new hardware in an effort to resolve these months of hard resets and reboots. I've attached my diagnostics log here in the hope it might shed some light--appreciate any feedback! I got no idea. what's your docker run command? I'll see if I can reproduce.
January 1, 20179 yr I've posted earlier in here about general lockups and I have more info. Off a clean shutdown and reboot of the system I'm seeing the following in my plex container docker log when starting it: ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/index.php/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. Starting Avahi daemon [services.d] done. 6 3000 /config/Library/Application Support d Daemon already running on PID 277 dbus[277]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted 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. Starting Avahi daemon [services.d] done. 6 3000 /config/Library/Application Support d Daemon already running on PID 277 dbus[277]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Daemon already running on PID 277 Starting Avahi daemon Those last lines will repeat until I kill it. Things I've done to this point in an effort to pinpoint the random lockups (where I can ping host but not SSH or get webgui functionality): Full memtest multiple times and for 24 hours plus runs. Removed and rebuilt docker.img multiple times. Running Plex and only Plex docker. Set CPU variable to only use anywhere from 6 down to 3 cores (out of 8 ). Replaced power supply thinking perhaps not enough on the +12v. I just can't stay stable for more than 24 hours with Plex running. At this point I'm ready to replace my hardware (Xeon x3470 on Supermicro X8SIL so it's pretty old) with new hardware in an effort to resolve these months of hard resets and reboots. I've attached my diagnostics log here in the hope it might shed some light--appreciate any feedback! I got no idea. what's your docker run command? I'll see if I can reproduce. Thanks CHBMB! Where would I locate the run command? Getting a bit deeper than I've been before...
January 1, 20179 yr Thanks CHBMB! Where would I locate the run command? Getting a bit deeper than I've been before... Link in my sig
January 1, 20179 yr Thanks CHBMB! Where would I locate the run command? Getting a bit deeper than I've been before... Link in my sig Should have looked there first--apologies. Here it is. I did find another post while searching for the freedesk error that hinted at using /mnt/user instead of the individual folders for my library. Might simplify the go command... root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name="plex" --net="host" -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -e "VERSION"="latest" -v "/mnt/user/appdata/plexmediaserver/":"/config":rw -v "/mnt/user/Jason":"/JMovies":rw -v "/mnt/user/Movies":"/Movies":rw -v "/mnt/user/Jason TV/PlexTV/":"/JTV":rw -v "/mnt/user/Television/PlexTV/":"/TV":rw -v "/mnt/user/Photos":"/Photos":rw -v "/mnt/user/Christmas Movies":"/Christmas":rw --cpuset-cpus=0-3 linuxserver/plex 4c3704bfb34c8244fd6c9a848cee7959d4dc76ea9da79a1a3f7c4ec628297f2c
January 2, 20179 yr Thanks CHBMB! Where would I locate the run command? Getting a bit deeper than I've been before... Link in my sig In what may go down as one of the biggest "OMG" moments in the history of unRAID, I happened to notice on the dashboard screen that 3508 MB of RAM was listed as allocated and 16GB of RAM available. Hmmm...that's odd I thought. Rebooted and checked in BIOS--showed 3gb there. Powered down, reseated memory, still 3gb. Pulled DIMM thinking perhaps I hadn't bought qualified memory and wanted to check DIMM stats. Sure enough it's listed on qualified manufacturers list for my mobo. Rinse repeat--still 3gb. Started poking through the BIOS and there's a check field for qualified CPU and DIMM compatibility. Disabled that option, rebooted and low and behold 16gb. I've been struggling with these random lock ups for at least a month now and at some point perhaps I loaded bios defaults or things reset. But now the UI screams as does docker UI's and scans--it's clear that just between plex and unraid I was running right up against the limit. Sometimes it's the most simple things...hope this is the resolution once and for all.
January 2, 20179 yr Thanks CHBMB! Where would I locate the run command? Getting a bit deeper than I've been before... Link in my sig In what may go down as one of the biggest "OMG" moments in the history of unRAID, I happened to notice on the dashboard screen that 3508 MB of RAM was listed as allocated and 16GB of RAM available. Hmmm...that's odd I thought. Rebooted and checked in BIOS--showed 3gb there. Powered down, reseated memory, still 3gb. Pulled DIMM thinking perhaps I hadn't bought qualified memory and wanted to check DIMM stats. Sure enough it's listed on qualified manufacturers list for my mobo. Rinse repeat--still 3gb. Started poking through the BIOS and there's a check field for qualified CPU and DIMM compatibility. Disabled that option, rebooted and low and behold 16gb. I've been struggling with these random lock ups for at least a month now and at some point perhaps I loaded bios defaults or things reset. But now the UI screams as does docker UI's and scans--it's clear that just between plex and unraid I was running right up against the limit. Sometimes it's the most simple things...hope this is the resolution once and for all. Does that mean you need to memtest the other 13GB? Sent from my LG-H815 using Tapatalk
January 2, 20179 yr Thanks CHBMB! Where would I locate the run command? Getting a bit deeper than I've been before... Link in my sig In what may go down as one of the biggest "OMG" moments in the history of unRAID, I happened to notice on the dashboard screen that 3508 MB of RAM was listed as allocated and 16GB of RAM available. Hmmm...that's odd I thought. Rebooted and checked in BIOS--showed 3gb there. Powered down, reseated memory, still 3gb. Pulled DIMM thinking perhaps I hadn't bought qualified memory and wanted to check DIMM stats. Sure enough it's listed on qualified manufacturers list for my mobo. Rinse repeat--still 3gb. Started poking through the BIOS and there's a check field for qualified CPU and DIMM compatibility. Disabled that option, rebooted and low and behold 16gb. I've been struggling with these random lock ups for at least a month now and at some point perhaps I loaded bios defaults or things reset. But now the UI screams as does docker UI's and scans--it's clear that just between plex and unraid I was running right up against the limit. Sometimes it's the most simple things...hope this is the resolution once and for all. Does that mean you need to memtest the other 13GB? Sent from my LG-H815 using Tapatalk Not sure..I'm certain I've tested it numerous times and can't imagine I wouldn't have noticed if it was only testing 3gb. But based on my recent history who knows...time to test for sure. Had a lockup again last night while transcoding and saw a new error "hangcheck value past margin!" A search against that showed another user had to replace his CPU so Im looking for new hardware at this point.
January 2, 20179 yr Is there a way to assign two cores, even specific cores, to Plex via parameters in the docker setup?
January 2, 20179 yr Is there a way to assign two cores, even specific cores, to Plex via parameters in the docker setup? http://lime-technology.com/forum/index.php?topic=40937.msg492111#msg492111
January 3, 20179 yr Recently I have been unable to update several of my dockers, PMS being one of them. When I run the Update from within unRAID I get the following error message: Pulling image: linuxserver/plex:latest TOTAL DATA PULLED: 0 B Error: Tag latest not found in repository docker.io/linuxserver/plex This error shows up in the docker.log file: time="2017-01-03T08:03:16.898000264-06:00" level=error msg="Handler for GET /v1.22/images/PlexMediaServer/json returned error: No such image: PlexMediaServer" I have attached the diagnostics output from the server. This only started happening a few weeks ago. tower-diagnostics-20170103-1613.zip
January 3, 20179 yr Recently I have been unable to update several of my dockers, PMS being one of them. When I run the Update from within unRAID I get the following error message: Pulling image: linuxserver/plex:latest TOTAL DATA PULLED: 0 B Error: Tag latest not found in repository docker.io/linuxserver/plex This error shows up in the docker.log file: time="2017-01-03T08:03:16.898000264-06:00" level=error msg="Handler for GET /v1.22/images/PlexMediaServer/json returned error: No such image: PlexMediaServer" I have attached the diagnostics output from the server. This only started happening a few weeks ago. Did this start after you upgraded your Unraid version by any chance?
January 4, 20179 yr Does anyone on this docker have the resources folder as per this post? https://forums.plex.tv/discussion/comment/1331055/#Comment_1331055 Ive even tried enabling dlna and restarted the docker in the hope to see the profiles. Cheers
January 4, 20179 yr I upgraded to 6.2.4 long before this started happening. I didn't observe this behavior until December, after running on 6.2.4 since a few days after it's release.
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.