CHBMB Posted December 17, 2016 Share Posted December 17, 2016 It won't see your movies, you have no folders mapped. Sent from my LG-H815 using Tapatalk Quote Link to comment
Archivist Posted December 17, 2016 Share Posted December 17, 2016 Hi CHBMB, Sorry, I guess that could be the problem, but my Config is "/mnt/user/Apple/MK4-MKV_Movies" so I thought that constituted the "path". Quote Link to comment
Squid Posted December 17, 2016 Share Posted December 17, 2016 Hi CHBMB, Sorry, I guess that could be the problem, but my Config is "/mnt/user/Apple/MK4-MKV_Movies" so I thought that constituted the "path". Technically that does work. Tell Plex to find the media within /Config. *BUT* I really have to advise against that type of organization (storing appdata within your media shares) My opinion is that Plex has the god-given right to do whatever it wants to within its appdata path. And that includes deleting any files which it thinks does not belong (your media) if and whenever it chooses. EDIT: Should have mentioned to change the mapping for /config to be something like /mnt/user/appdata/plex Add another mapping of say /apple mapped to /mnt/user/Apple/MK4-MKV_Movies and point Plex's libraries to /apple Beyond that, I very rarely use Plex so don't know why it won't find your server. But I think you can go to your account and delete old servers that are present that may be mucking things up. Quote Link to comment
Archivist Posted December 17, 2016 Share Posted December 17, 2016 Hi CHBMB, Sorry, I guess that could be the problem, but my Config is "/mnt/user/Apple/MK4-MKV_Movies" so I thought that constituted the "path". Technically that does work. Tell Plex to find the media within /Config. Hey Squid, Great to hear from you. I know you don't really use Plex (and/or CrashPlan), but it probably relates to my mis-understanding of how my Docker(s) should be configured properly. In the case of Plex my Config = /mnt/user/Apple/MK4-MKV_Movies so when trying to set the "path" within Plex I guess I'm lost. When I go into Plex the program, since it can't find a "Server" it does not give me the option to set a path. Dave *BUT* I really have to advise against that type of organization (storing appdata within your media shares) My opinion is that Plex has the god-given right to do whatever it wants to within its appdata path. And that includes deleting any files which it thinks does not belong (your media) if and whenever it chooses. Add another mapping of say /apple mapped to /mnt/user/Apple/MK4-MKV_Movies and point Plex's libraries to /apple Beyond that, I very rarely use Plex so don't know why it won't find your server. But I think you can go to your account and delete old servers that are present that may be mucking things up. Quote Link to comment
Squid Posted December 17, 2016 Share Posted December 17, 2016 Hey Squid, Great to hear from you. I know you don't really use Plex (and/or CrashPlan), but it probably relates to my mis-understanding of how my Docker(s) should be configured properly. In the case of Plex my Config = /mnt/user/Apple/MK4-MKV_Movies so when trying to set the "path" within Plex I guess I'm lost. When I go into Plex the program, since it can't find a "Server" it does not give me the option to set a path. Dave Volume mappings in docker are a kind of "shortcut" You tell docker to map /config to /mnt/user/appdata/plex and /apple to /mnt/user/Apple/MKV.... The plex docker has no concept of the underlying filesystem at all. All it knows is the paths (shortcuts) that you've given it In this case /config and /apple. /config is where plex stores all of its program data, etc and actually shows up on your server within the appdata share (/mnt/user/appdata/plex) you tell plex when you create a library to look for your media within /apple. Docker then translates that shortcut and looks for the media on your array in the Apple share (/mnt/user/Apple/MKV...) Quote Link to comment
Archivist Posted December 17, 2016 Share Posted December 17, 2016 Hey Squid, Thanks, I finally got the Plex Server up and its loading my Movies . Interesting the default to /Apple found a sub-directory for Bond Series first and I had to go back into Plex and add another /Apple/MK4-MKV Movie path to find all of the others which I thought was a bit odd. Dave Quote Link to comment
trurl Posted December 17, 2016 Share Posted December 17, 2016 Possibly you have more than one share with the same name, except for upper/lower case. Post a screenshot of your User Shares page, or just post your diagnostics. Quote Link to comment
Archivist Posted December 18, 2016 Share Posted December 18, 2016 Hi Trurl, Thanks, will do (see below). Plex started to identify ~ 140 Movies w/artwork, then proceeded to Lock-UP not only Plex but my entire UnRaid Server. I could not even access the Server via telnet or directly from the GUI interface attached to the Server. I had to force power down Tower and restart. Of course I got the CA error from Fix Common Problems and Parity is being checked (not corrected). I do not ever recall having UnRaid "lock-up" in this fashion at any other time. Now it's back to the Plex Server not found again. I even tried to restart Plex Media Server and re-login to my Plex (webloc) link w/o success (grrrrr). Dave Quote Link to comment
trurl Posted December 18, 2016 Share Posted December 18, 2016 Not at all what was asked for Post a screenshot of your User Shares page, or just post your diagnostics. Quote Link to comment
Archivist Posted December 18, 2016 Share Posted December 18, 2016 Sorry Trurl, In a "rush", got called to hospital for a case. I did try to get a log file but it was too big to include. User Shares/diags attached. Parity re-check still in process. My bad, Dave tower-diagnostics-20161218-0539.zip Quote Link to comment
Archivist Posted December 18, 2016 Share Posted December 18, 2016 Too Large for both - Screen shot below: Quote Link to comment
Katherine Posted December 18, 2016 Share Posted December 18, 2016 My Plex Media Server won't start after the latest updates. Not sure what is causing the problem. I would appreciate any advice. Log: ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| 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 # # plex token found in the preference file # ##################################################### [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. 6 3000 /config/Library/Application Support d 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 br0.IPv4 with address 192.168.0.101. New relevant interface br0.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.0.101 on br0.IPv4. Server startup complete. Host name is NAS.local. Local service cookie is 3078254584. Joining mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1. New relevant interface virbr0.IPv4 for mDNS. Registering new address record for 192.168.122.1 on virbr0.IPv4. 2016-12-18 09:11:25,885 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : INFO (core:349) - Starting framework core - Version: 2.6.3, Build: b38628e (Thu Dec 15 21:34:00 UTC 2016) 2016-12-18 09:11:25,886 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (core:361) - Using the elevated policy 2016-12-18 09:11:25,886 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (core:450) - Starting runtime component. 2016-12-18 09:11:25,889 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (core:450) - Starting caching component. 2016-12-18 09:11:25,890 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (core:450) - Starting data component. 2016-12-18 09:11:25,890 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (core:450) - Starting networking component. 2016-12-18 09:11:25,891 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (networking:284) - Loaded HTTP cookies 2016-12-18 09:11:25,892 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (networking:452) - Setting the default network timeout to 20.0 2016-12-18 09:11:25,893 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (core:450) - Starting localization component. 2016-12-18 09:11:25,894 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : INFO (localization:409) - Setting the default locale to en-us 2016-12-18 09:11:25,894 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (core:450) - Starting messaging component. 2016-12-18 09:11:25,895 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (core:450) - Starting debugging component. 2016-12-18 09:11:25,895 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (core:450) - Starting services component. 2016-12-18 09:11:25,896 - com.plexapp.plugins.unsupportedappstore (2afca9be0700) : DEBUG (networking:166) - Requesting 'http://127.0.0.1:32400/system/messaging/clear_events/com.plexapp.plugins.unsupportedappstore' 2016-12-18 09:11:25,896 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (core:450) - Starting myplex component. 2016-12-18 09:11:25,898 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (core:450) - Starting notifications component. 2016-12-18 09:11:26,131 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (accessor:68) - Creating a new model access point for provider com.plexapp.plugins.unsupportedappstore in namespace 'metadata' 2016-12-18 09:11:26,140 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (networking:166) - Requesting 'http://127.0.0.1:32400/:/plugins/com.plexapp.system/resourceHashes' 2016-12-18 09:11:26,460 - com.plexapp.plugins.unsupportedappstore (2afca9be0700) : DEBUG (services:265) - Plug-in is not daemonized - loading services from system 2016-12-18 09:11:26,460 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (runtime:1117) - Created a thread named 'load_all_services' 2016-12-18 09:11:26,462 - com.plexapp.plugins.unsupportedappstore (2afca9be0700) : DEBUG (networking:166) - Requesting 'http://127.0.0.1:32400/:/plugins/com.plexapp.system/messaging/function/X0J1bmRsZVNlcnZpY2U6QWxsU2VydmljZXM_/Y2VyZWFsMQoxCmxpc3QKMApyMAo_/Y2VyZWFsMQoxCmRpY3QKMApyMAo_' 2016-12-18 09:11:26,463 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (runtime:1117) - Created a thread named 'get_server_info' 2016-12-18 09:11:26,464 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (core:150) - Finished starting framework core 2016-12-18 09:11:26,464 - com.plexapp.plugins.unsupportedappstore (2afcaa0e2700) : DEBUG (networking:166) - Requesting 'http://127.0.0.1:32400' 2016-12-18 09:11:26,464 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (core:560) - Loading plug-in code 2016-12-18 09:11:26,884 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (core:566) - Finished loading plug-in code 2016-12-18 09:11:26,885 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (runtime:640) - Adding a prefix handler for 'UnSupported AppStore' ('/video/unsupportedappstore') 2016-12-18 09:11:26,923 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : INFO (datakit:93) - Loaded the dictionary file 2016-12-18 09:11:26,924 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (__init__:520) - UnSupported Appstore version: unknown 2016-12-18 09:11:26,925 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (networking:166) - Requesting 'http://127.0.0.1:32400' 2016-12-18 09:11:26,932 - com.plexapp.plugins.unsupportedappstore (2afcaa0e2700) : DEBUG (core:538) - Machine identifier is 521d8d882805e4fc688ccb9ef112db33c24541fd 2016-12-18 09:11:26,950 - com.plexapp.plugins.unsupportedappstore (2afcaa0e2700) : DEBUG (core:539) - Server version is 1.3.3.3148-b38628e 2016-12-18 09:11:27,125 - com.plexapp.plugins.unsupportedappstore (2afca9be0700) : DEBUG (services:362) - Loaded services 2016-12-18 09:11:27,135 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (services:438) - No shared code to load 2016-12-18 09:11:27,137 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (core:521) - Attribute 'platformVersion' set to '4.4.30-unRAID (#2 SMP PREEMPT Sat Nov 5 12:09:05 PDT 2016)' 2016-12-18 09:11:27,137 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (__init__:520) - Platform: Linux 4.4.30-unRAID (#2 SMP PREEMPT Sat Nov 5 12:09:05 PDT 2016) 2016-12-18 09:11:27,137 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (__init__:520) - Server: PMS 1.3.3.3148-b38628e 2016-12-18 09:11:27,138 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (preferences:258) - Loaded preferences from DefaultPrefs.json 2016-12-18 09:11:27,139 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (preferences:178) - Loaded the user preferences for com.plexapp.plugins.unsupportedappstore 2016-12-18 09:11:27,140 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (__init__:520) - Running auto-update. 2016-12-18 09:11:27,141 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (runtime:1117) - Created a thread named 'BackgroundUpdater' 2016-12-18 09:11:27,142 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : INFO (core:611) - Started plug-in 2016-12-18 09:11:27,143 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (socketinterface:160) - Starting socket server 2016-12-18 09:11:27,142 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (networking:166) - Requesting 'https://github.com/mikew/ss-plex.bundle/commits/stable.atom' 2016-12-18 09:11:27,145 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (runtime:1117) - Created a thread named 'start' 2016-12-18 09:11:27,145 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : INFO (socketinterface:184) - Socket server started on port 43972 2016-12-18 09:11:27,146 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : INFO (pipeinterface:25) - Entering run loop 2016-12-18 09:11:27,146 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (runtime:717) - Handling request GET /:/prefixes 2016-12-18 09:11:27,149 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (runtime:814) - Found route matching /:/prefixes 2016-12-18 09:11:27,151 - com.plexapp.plugins.unsupportedappstore (2afca122c480) : DEBUG (runtime:924) - Response: [200] MediaContainer, 515 bytes 2016-12-18 09:11:27,575 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (__init__:520) - SS Plex: Up-to-date :: Version 031566c062 2016-12-18 09:11:27,603 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : INFO (datakit:131) - Saved the dictionary file 2016-12-18 09:11:27,604 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (networking:166) - Requesting 'https://github.com/mikedm139/UnSupportedAppstore.bundle/commits/master.atom' 2016-12-18 09:11:27,929 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : CRITICAL (runtime:1128) - Exception in thread named 'BackgroundUpdater' (most recent call last): File "/usr/lib/plexmediaserver/Resources/Plug-ins-b38628e/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/components/runtime.py", line 1126, in _start_thread f(*args, **kwargs) File "/config/Library/Application Support/Plex Media Server/Plug-ins/UnSupportedAppstore.bundle/Contents/Code/__init__.py", line 485, in BackgroundUpdater GetRSSFeed(plugin=plugin, install=True) File "/config/Library/Application Support/Plex Media Server/Plug-ins/UnSupportedAppstore.bundle/Contents/Code/__init__.py", line 429, in GetRSSFeed mostRecent = Datetime.ParseDate(commits.xpath('//entry')[0].xpath('./updated')[0].text[:-6]) File "/usr/lib/plexmediaserver/Resources/Plug-ins-b38628e/Framework.bundle/Contents/Resources/Versions/2/Python/Framework/code/sandbox.py", line 108, in <lambda> _getitem_ = lambda x, y: x.__getitem__(y), IndexError: list index out of range 2016-12-18 09:12:31,977 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (runtime:717) - Handling request GET /:/plugins/com.plexapp.plugins.unsupportedappstore/reloadServices 2016-12-18 09:12:31,994 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (runtime:814) - Found route matching /:/plugins/com.plexapp.plugins.unsupportedappstore/reloadServices 2016-12-18 09:12:31,994 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (services:15) - Reloading services 2016-12-18 09:12:31,995 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (services:265) - Plug-in is not daemonized - loading services from system 2016-12-18 09:12:31,995 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (networking:166) - Requesting 'http://127.0.0.1:32400/:/plugins/com.plexapp.system/messaging/function/X0J1bmRsZVNlcnZpY2U6QWxsU2VydmljZXM_/Y2VyZWFsMQoxCmxpc3QKMApyMAo_/Y2VyZWFsMQoxCmRpY3QKMApyMAo_' 2016-12-18 09:12:32,127 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (services:362) - Loaded services 2016-12-18 09:12:32,128 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (runtime:924) - Response: [200] bool, 0 bytes 2016-12-18 09:12:33,236 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (runtime:717) - Handling request GET /:/plugins/com.plexapp.plugins.unsupportedappstore/reloadServices 2016-12-18 09:12:33,237 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (runtime:814) - Found route matching /:/plugins/com.plexapp.plugins.unsupportedappstore/reloadServices 2016-12-18 09:12:33,237 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (services:15) - Reloading services 2016-12-18 09:12:33,238 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (services:265) - Plug-in is not daemonized - loading services from system 2016-12-18 09:12:33,238 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (networking:166) - Requesting 'http://127.0.0.1:32400/:/plugins/com.plexapp.system/messaging/function/X0J1bmRsZVNlcnZpY2U6QWxsU2VydmljZXM_/Y2VyZWFsMQoxCmxpc3QKMApyMAo_/Y2VyZWFsMQoxCmRpY3QKMApyMAo_' 2016-12-18 09:12:33,438 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (services:362) - Loaded services 2016-12-18 09:12:33,439 - com.plexapp.plugins.unsupportedappstore (2afca9ee1700) : DEBUG (runtime:924) - Response: [200] bool, 0 bytes Quote Link to comment
CHBMB Posted December 18, 2016 Share Posted December 18, 2016 What version? Post your docker run command, from what I can tell in the logs it is starting I think. Looks like it didn't find the preferences.xml file which contains your plex token. Normal resides in /appdata/plex/Library/Application Support/Plex Media Server/ Quote Link to comment
andrewpercival Posted December 19, 2016 Share Posted December 19, 2016 hey guys, trying to setup plex dvr. i am a plexpass subscriber but cant seem to get the plexpass version to show up. I have the version set as plexpass but on my docker screen still shows latest. Quote Link to comment
CHBMB Posted December 19, 2016 Share Posted December 19, 2016 hey guys, trying to setup plex dvr. i am a plexpass subscriber but cant seem to get the plexpass version to show up. I have the version set as plexpass but on my docker screen still shows latest. From the readme... And the tag :latest after the docker image is referring to the docker image, not the Plex version. That's why it appears after all the docker containers not just Plex. Quote Link to comment
talmania Posted December 19, 2016 Share Posted December 19, 2016 Interesting reading the past couple of responses here---especially yours Archivist. I've recently had trouble (like the past week or two) with my system as well. I'm finding that with the Plex docker running and doing a directory scan etc it will cause the webui to lock up and the only thing i can do is ping the server. No telnet, webgui, or fileshares. I've been trying different combinations of dockers to see what was causing it and i have it nailed down to plex and plex alone (i only run 3 and one of those is off 80% of the time). Have ran 24-hour plus memtests, reinstalled plex, reinstalled/recreated docker etc. Have run sqlite on the database to check for corruption and it comes back clean. Still more to investigate but it's looking like Plex is the culprit IMO. Quote Link to comment
Archivist Posted December 20, 2016 Share Posted December 20, 2016 Interesting reading the past couple of responses here---especially yours Archivist. I've recently had trouble (like the past week or two) with my system as well. I'm finding that with the Plex docker running and doing a directory scan etc it will cause the webui to lock up and the only thing i can do is ping the server. No telnet, webgui, or fileshares. Still more to investigate but it's looking like Plex is the culprit IMO. Hi Talmania, I concur. After re-booting my server and doing a complete Parity Check (w/o issues), I've concluded that when Plex initiates, it seems to tie up the Server's resources. Interestingly after completing the Parity Check and reinitializing Plex (incl restart), I had to log out of my Webloc link and back in to find the "Server" (still do occasionally). It then seemed to find all of my movies, so apparently Plex continued to work in the background despite locking up regular access (either that or while it was checking Parity). I've subsequently added several more movies to my sub-directory w/o incident. It would be interesting if others are seeing this pattern. Are you using MakeMKV-RDP and if so have you had problems "ripping blu ray discs"? Dave Quote Link to comment
talmania Posted December 20, 2016 Share Posted December 20, 2016 Interesting reading the past couple of responses here---especially yours Archivist. I've recently had trouble (like the past week or two) with my system as well. I'm finding that with the Plex docker running and doing a directory scan etc it will cause the webui to lock up and the only thing i can do is ping the server. No telnet, webgui, or fileshares. Still more to investigate but it's looking like Plex is the culprit IMO. Hi Talmania, I concur. After re-booting my server and doing a complete Parity Check (w/o issues), I've concluded that when Plex initiates, it seems to tie up the Server's resources. Interestingly after completing the Parity Check and reinitializing Plex (incl restart), I had to log out of my Webloc link and back in to find the "Server" (still do occasionally). It then seemed to find all of my movies, so apparently Plex continued to work in the background despite locking up regular access (either that or while it was checking Parity). I've subsequently added several more movies to my sub-directory w/o incident. It would be interesting if others are seeing this pattern. Are you using MakeMKV-RDP and if so have you had problems "ripping blu ray discs"? Dave Nope just using regular Plex. I've found it starts up just fine and then runs through getting metadata from the most recently added films (sometimes requesting same title 4-5 times in logs). It only seems to occur when I do a rescan on a library and then try to use the unraid webgui. That's the trigger I've found--and it's not like my CPU is taxed, memory is close to being fully allocated or the docker.img is anywhere close to being full either. It's happened almost a dozen times at this point with the only solution being a hard powerdown. The only thing I can think of at this point is the fact that one of my drives is showing a SMART issue reported (hasn't been kicked out of pool yet) with reallocated sector count of 9 (threshold 36). I'll be replacing that drive tonight once the parity check (like the 5th or 6th one at this point--cancelled the others). Quote Link to comment
Archivist Posted December 20, 2016 Share Posted December 20, 2016 Hi Talmania, I use web access vs the Plex webgui in UnRaid to access my Movies, but still had that problem. I also have a drive with less than stellar SMART status, but this was happening before adding it to the Array, so ? Thus far only 1x for me w/the Lockup not 12x ! Hopefully one of our Gurus will see this and figure out what is happening, my Server runs on a Xeon w/20 GB of Ram and twin 250GB of Cache (SSDx2) so I doubt if there is much problem there as well. Dave Quote Link to comment
talmania Posted December 20, 2016 Share Posted December 20, 2016 Very similar to you--legacy Supermicro X7 series motherboard with Xeon, 16GB RAM, dual 256gb SSD cache but I've got about 5k media files across 3 or 4 libraries with just over 20% capacity left on the entire array. I hope so too! I'll report back once the array is rebuilt here in a few days--crossing my fingers but not counting on it solving the problem. Quote Link to comment
talmania Posted December 21, 2016 Share Posted December 21, 2016 Rebuilt successfully and on my first attempt to scan a Plex library and then navigate WebGui it became unresponsive again. Waited a few minutes then walked away in frustration. Came back maybe 45 minutes later and the webgui acted like nothing had ever gone wrong. Strange... Quote Link to comment
Techn0mancer Posted December 22, 2016 Share Posted December 22, 2016 I've had issues with accessing unRAID webui if I didn't use the --cpuset-cpus attribute to limit the cores my Plex container uses. Have you tried setting it to use all but one or two cores? Quote Link to comment
talmania Posted December 22, 2016 Share Posted December 22, 2016 I've had issues with accessing unRAID webui if I didn't use the --cpuset-cpus attribute to limit the cores my Plex container uses. Have you tried setting it to use all but one or two cores? Thank you VERY much for this! I was excited to see that previous guaranteed lockup behavior wasn't causing the lockup once I set this parameter. Then all of a sudden after repeated testing it locked up again---looking at the cores from the webgui dashboard page I saw that core 6 was reporting 100% (almost no activity on the other cores) and I had specified Plex to use 0-5....which leads me to the point I had configured Crashplan to use 6&7 and enabled it after extensive testing. So reality is I'm looking at a crashplan issue and would have never arrived there without your assistance. I know I had lockups with Plex being the only active docker previously but with this --cpuset-cpus variable I'm able to avoid having the lockups that plagued me as long as I don't have Crashplan running at the same time. Plex cpu0-5 and nothing else: no lockups Crashplan 6-7 and Plex 0-5: 100% on core6 and lockup Thanks! Quote Link to comment
trurl Posted December 22, 2016 Share Posted December 22, 2016 I've had issues with accessing unRAID webui if I didn't use the --cpuset-cpus attribute to limit the cores my Plex container uses. Have you tried setting it to use all but one or two cores? Thank you VERY much for this! I was excited to see that previous guaranteed lockup behavior wasn't causing the lockup once I set this parameter. Then all of a sudden after repeated testing it locked up again---looking at the cores from the webgui dashboard page I saw that core 6 was reporting 100% (almost no activity on the other cores) and I had specified Plex to use 0-5....which leads me to the point I had configured Crashplan to use 6&7 and enabled it after extensive testing. So reality is I'm looking at a crashplan issue and would have never arrived there without your assistance. I know I had lockups with Plex being the only active docker previously but with this --cpuset-cpus variable I'm able to avoid having the lockups that plagued me as long as I don't have Crashplan running at the same time. Plex cpu0-5 and nothing else: no lockups Crashplan 6-7 and Plex 0-5: 100% on core6 and lockup Thanks! Maybe you need to let unRAID have a core. Quote Link to comment
talmania Posted December 22, 2016 Share Posted December 22, 2016 I've had issues with accessing unRAID webui if I didn't use the --cpuset-cpus attribute to limit the cores my Plex container uses. Have you tried setting it to use all but one or two cores? Thank you VERY much for this! I was excited to see that previous guaranteed lockup behavior wasn't causing the lockup once I set this parameter. Then all of a sudden after repeated testing it locked up again---looking at the cores from the webgui dashboard page I saw that core 6 was reporting 100% (almost no activity on the other cores) and I had specified Plex to use 0-5....which leads me to the point I had configured Crashplan to use 6&7 and enabled it after extensive testing. So reality is I'm looking at a crashplan issue and would have never arrived there without your assistance. I know I had lockups with Plex being the only active docker previously but with this --cpuset-cpus variable I'm able to avoid having the lockups that plagued me as long as I don't have Crashplan running at the same time. Plex cpu0-5 and nothing else: no lockups Crashplan 6-7 and Plex 0-5: 100% on core6 and lockup Thanks! Maybe you need to let unRAID have a core. I'm guessing I can't assign unRAID a core as per the extra parameters and rather the process would be to just leaving one unassigned is enough correct? Quote Link to comment
Recommended Posts
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.