Server Version#: 1.18.0.1944-f2cae8d6b
Hi,
I hope someone can help. Updated to the latest release on my QNAP TS-453A (running latest 4.4.1.1081 firmware), which has worked perfectly up till now. However, my NAS is now running at 97% CPU utilisation. When I stop the PMS app, CPU returns to 16%…
Does anyone else have experience of this, or even better, a fix?
TIA,
Adam.
Upgrading from 1.17 or lower to 1.18 will get you Plex’s brand new unified music agent named Plex Music, and it will automatically scan all your music files and gather new sorts of online metadata to include because you have a plex pass.
Do you have a lot of music?
Thanks Nibbles.
I do have quite a lot of music, but it’s not my priority content. Is there any way to turn off the metadata refresh for the new music agent?
TIA,
Adam.
Must’ve been a bug, as I’ve just had an update notification which looks like exactly the same version number, which seems to have fixed the problem!
She’s breathing! 
A strong qnap that girl.
False alarm. It’s doing it again. Must be something to do with the new Plex Music agent when it started running again during the night. I’m sure it would finish eventually, but it will never match all my music, so I’d rather it didn’t bother. I certainly don’t want it running periodically, and effectively making my NAS unable to do anything else…
Can I disable it somehow?
1.17 worked fine. I wonder how much testing this went through. I can’t be the only person who has a large music library with mixed quality ID3 tagging!
If I may add here,
There is a bit of overly energetic music scanner activity.
The fingerprinting part of the scanner is currently checking every song of the album to verify a 100% absolute match.
This isn’t necessary. Yesterday, Engineering made a change to reduce that load without compromising match integrity. It has the direct benefit of also lowering CPU loading.
If I understand correctly, this will be updated in the next PMS release. (if I read the notes correctly).
That makes sense. Let’s hope they release it quickly!
Again, if I read it correctly, REALLY quickly.
I’m not 100% convinced it’s the music agent, unless it’s running in the background - nothing showing in Activity. Meanwhile my QNAP is running at 99%.
Experiment FAILED, Plex. Roll back to 1.17 functionality NOW, please!
Reinstall PMS 1.17.0 or whatever version you have if it’s that urgent to you.
I’ve been handling many of these issues.
They all began with the new music agent in 1.18.0
Music fingerprinting does not show in the logs.
Engineering did find a way to lighten the CPU demand already (they saw this pre-release of 1.18.0). This improvement will be released in 1.18.1 ( a couple days if I read it correctly).
If it’s the finger printing, You will see the [Plex Media Fing] (Fingerprinter) process running for each music track. It will run for only a few seconds and then move to the next track.
Since it takes a few seconds, if you have 10,000 tracks , you’re looking at 30-40,000 seconds to complete the task.
Is this what you’re seeing?
Logs would also be helpful just to rule out any other issues.
I’ve definitely seen the [Plex Media Fing] process running in the Process Monitor. I’ve got somewhere north of 30,000 tracks, and I suspect my CPU will fry if I let it run…
TBH, I wouldn’t have the first clue how to get you the logs!
Happy to downgrade until 1.18.1 comes out. Where can I get the QPKG file?
Not sure if this is the version you want/need, but there’s a link in the thread below to the Plex version I rolled back to on my QNAP TVS-473 NAS when I had problems with the 1.18 update:
And this article explains how to get
Hi Chuck,
Any sign of the update yet?
PMS is STILL scanning my music files 10 days later!
TIA<
Adam.
Confirm for me your Library settings?
Correct?
If yes, then I need to know how many music files you’ve given it to Index.
If no, meaning you have it running on a timer, Cancel the scan, make the setting change, restart the scan.
It should not take 10 days.
I did mine, two libraries in a couple hours with 12,670 files in one, 20001 in another.
Hi Chuck,
I did have Periodic ON… Not sure if that’s the default, or if I changed it in the distant past!
Will see what happens.
Appreciate your help.
Adam.
Adam,
The default is with none enabled. With the new scanner, because it takes a more thorough approach, Periodic can cause it to restart before ever completing the first scan when large libraries are involved if not set to a large enough interval.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
