theliuman, laffer98 and jnorbut: It sounds like the OP and brokenlibrarian both ran into this with empty library sections (no files to analyze). How about you?
theliuman, laffer98: Does unchecking the "Upgrade media analysis during maintenance" option correct things?
theliuman, laffer98 and jnorbut: It sounds like the OP and brokenlibrarian both ran into this with empty library sections (no files to analyze). How about you?
Mediaconoclast, I ran into this issue with populated library sections. Let me know how I can help further.
The last time Butler (which I assume is a maintenance system) never even got to the RefreshLocalMedia task, it got wedged on "UpgradeMediaAnalysis". And I'm not seeing any CPU problems, and there's no wedged threads in Process Explorer.
If I run "C:\Program Files (x86)\Plex\Plex Media Server\Plex Media Scanner.exe --analyze --no-thumbs --item 2336,2484,2247,2310" manually in a command prompt from within the Plex Media Server folder, I get the following:
and the process appears to finish properly. I have no idea if this means anything at all.
I'm going to leave "Upgrade media analysis during maintenance" disabled for the time being. If there's any other information I can provide to figure out exactly what's going on, let me know and I'll do my best.
I'm running 0.9.11.1.678-c48ffd2 and have had a similar experience to that of brokenlibrarian's. That is:
Plex Media Server starts burning a core shortly after startup
The UpgradeMediaAnalysis job kicks off but never finishes
Manually running the same cmd line for Plex Media Scanner appears to run without issue
When in this state exiting via the tray icon kills the child processes, but Plex Media Server.exe remains and must be killed manually.
Disabling "Upgrade media analysis during maintenance" fixes the issue.
Please let me know if I can provide any further information/logs.
Mediaconoclast, I ran into this issue with populated library sections. Let me know how I can help further.
So to summarise, we have 2 users now indicating that this happens when 'Upgrade Media Analysis' is selected.
thank you. wouldn't have noticed if it weren't for the killawatt showing 50w more draw than usual
Indeed, many thanks brokenlibrarian for your investigation.
I only noticed it because I had just built my current machine a few days earlier and was keeping a close eye on cpu temps. I noticed higher idle temperatures, then fired up task manager and saw my cpu was consistently hovering around 4.2GHz when it normally idles down to 800Mhz.
I have run Plex Media Server on a Macbook Pro on and off for a couple years and always get the process going to 100% after about 10 minutes, both with and without checking "Upgrade media analysis". I subsequently gave up on using the macbook and run it on Windows 7 where it doesn't exhibit this problem. I'd like to run it on the Macbook so I'm looking into the problem again. I'm currently upgrading to Yosemite and I'll run PMS again after it's done.
Noticed my CPU temp going higher than normal tonight as I've recently installed a new cooler and have been keeping a careful eye on it to ensure it is installed well etc
Checked Task Manager to find that Plex Media Server was running constantly at between 17 and 23 % usage with the scaled CPU timings at the upper 3.7GHz range constantly (so not just CPU usage %)... I have a tiny library (about 200 files total) and no streaming was happening, no new files been added for over a month etc etc etc
It's concerning because I thought I would be fine with the server app running constantly in the background and only using minimal CPU when idle and a limited amount during streaming.
I'm running Windows 7 64bit on server 0.9.11.1 with 12GB RAM.
I've checked to see if any of those options were on and they were already off. I have stopped the server and restarted but it always goes back to this CPU usage of at least 17% at 3.7GHz...
Not sure what is going on..
EDIT:
Went into the settings, ticked and unticked all those options again. Saved. Stopped the server and restarted and now CPU usage is 0% and holding steady. Also memory footprint is 14MB instead of 22MB, which it was when the weird CPU stuff was happening. Core speed is staying low as it should and temps returning to normal idle etc..
Yup, see my edit i just made. It’s weird but it’s like it forgot my settings and I had to tick, untick and save them again followed by restarting the server.
Just to confirm, removing of files with AVI index issues resolved the CPU usage issue.
It would be good to look at the Plex Media Scanner code and handle this case properly, maybe add an option to skip files with bad AVI index and possibly notify the user that file is problematic.
I experienced the same issue with the “Upgrade media analysis during maintenance” option enabled on my recently installed Plex, one CPU core was maxed out. A restart without that option is working as expected so far, no unexpected CPU usage.
As my Plex environment is only a few days old, I will turn it back on and see if it eventually scans all the media and goes into idle naturally over a week or so or if it hangs on a certain file eventually.
Same issue.
Running the most recent official Docker Image and CPU load has been on 100% for a long time. I just tested it with an empty library - same thing.
I started the container with docker run -d --restart=always --name=plex --network=host -v /opt/plex/config:/config plexinc/pms-docker where /opt/plex/config was an empty folder.