Thank you - your appreciation has been passed on
@sa2000 said:
The fix for the repeated matching of unmatched music artists has now been released in beta release 1.13.0.5003See Release Note http://forums.plex.tv/discussion/comment/1661803/#Comment_1661803
- (Metadata) Donât rematch things which have been unsuccessfully matched (#8394)
I marked 1.13.0.5003 as the accepted answer.
I also want to thank everyone involved on this. The whole thread was on topic, civilized and productive. Thanks everyone!
I may have spoken too soon. Please see the logs here. It is still constantly scanning. I also have already faced a computer shutdown as well during a scan. Seems to start every few minutesâŠlike previous versions. Nothing is triggering itâŠat least that I am aware of. I have been on .4829 with no issues these past few weeks. So, this behavior is not as it was. Might be better than the few prior releases that I did not try, but .4829 worked, and this one .5003 seems to do it by itself.
I can only comment on what my CPU load looks like (and looked like) before and after this version. So it may not be specifically what the OP is seeing. My CPU loads spiked to 100% every 6 hours. I turned off periodically update libraries, it went away. I down versioned, it went away. I still saw occasional CPU spikes, but never 100% and never on a periodic time basis.
When I up-versioned to the current public release, same pattern presented itself. When I installed the latest beta version, my CPU spikes have never been over 30% and then only at the daily maintenance time. No periodic spiking to 100% CPU utilization. I have noticed no stability problems with the beta version. I up-versioned 3 days ago, and all appears smooth from my experience. I have NOT inspected my logs to see what may be happening. I have the beta version on two servers and similar experiences on both.
@terag1e said:
Since we are always coming here and seemingly griping, I wanted to drop back by and say this most recent beta release does indeed appear to have solved this specific problem. Job well done, devs. And you probably hear too little of that.
Word!
I re-enabled hourly library updates yesterday. My NAS utilisation and Plex server performance are back to normal and both work perfectly fine without constantly trying to match music. Thanks for quickly resolving this issue!
Not sure whatâs up with your server, @âKyle Verryâ. Is it scanning or matching? Maybe a quirk of the Mac version?
@derico said:
@terag1e said:
Not sure whatâs up with your server, @âKyle Verryâ. Is it scanning or matching? Maybe a quirk of the Mac version?
I only just did the update, so I will monitor for two days and see. I am glad itâs working for everyone else. Iâll report back on either good or bad news.
Thanks.
was facing this issue as well, normally dont install the beta versions, but felt i had no choice. drive was constantly spinning (or maybe it was my fan on CPU) and super annoying.
at the moment, post install, it has stopped
So, the constant rescanning does appear to be gone, however the reason I keep seeing tons of activity is it is STILL scanning unmatched items on every single search. So, since a quarter of my 28,000 library is unmatched, it takes FOREVER every single time a new item is added.
Any reason why it wasnât just put back to how it was? I totally get the idea of wanting to scan, but isnât that the purpose of the âRefresh Metadataâ option? That forces it. Why does it have to do this every single time? I really really is an irritant.
Could we not just have this as an option?
I am certain I am coming off unappreciative, and I want to be crystal clear that I AM appreciative! However, it is still a huge issue compared to 4829 where everything was stellarâŠ
@âKyle Verryâ said:
So, the constant rescanning does appear to be gone, however the reason I keep seeing tons of activity is it is STILL scanning unmatched items on every single search. So, since a quarter of my 28,000 library is unmatched, it takes FOREVER every single time a new item is added.Any reason why it wasnât just put back to how it was? I totally get the idea of wanting to scan, but isnât that the purpose of the âRefresh Metadataâ option? That forces it. Why does it have to do this every single time? I really really is an irritant.
Could we not just have this as an option?
I am certain I am coming off unappreciative, and I want to be crystal clear that I AM appreciative! However, it is still a huge issue compared to 4829 where everything was stellarâŠ
Please could you give me the exact steps you go through that triggers this and I would not mind some logs
Thanks
@sa2000 said:
@âKyle Verryâ said:
So, the constant rescanning does appear to be gone, however the reason I keep seeing tons of activity is it is STILL scanning unmatched items on every single search. So, since a quarter of my 28,000 library is unmatched, it takes FOREVER every single time a new item is added.Any reason why it wasnât just put back to how it was? I totally get the idea of wanting to scan, but isnât that the purpose of the âRefresh Metadataâ option? That forces it. Why does it have to do this every single time? I really really is an irritant.
Could we not just have this as an option?
I am certain I am coming off unappreciative, and I want to be crystal clear that I AM appreciative! However, it is still a huge issue compared to 4829 where everything was stellarâŠ
Please could you give me the exact steps you go through that triggers this and I would not mind some logs
Thanks
In a stroke of âGood lordâŠâ I went to get you fresh logs and stuff, shut down Plex, opened it up, and then it scanned in 10 seconds. Ugh! I will capture some logs for you later today when it occurs again.
However, I am going to post a different issue I faced. When I added a new album on this trial run here, it is not updating the metadata for the new album (Last.FM issue? Or is it trying to prioritize the MP3 tags?). I did try to force a Fix Match but it still doesnât display the information like it finds on Last.FM. (In this case, I can tell because it is all caps versus Last.FMâs normal writing). Also, the .5003 seems to have broken Plex for Sonos.
Here is the information for the above two problems I had.
@sa2000 said:
@âKyle Verryâ said:
So, the constant rescanning does appear to be gone, however the reason I keep seeing tons of activity is it is STILL scanning unmatched items on every single search. So, since a quarter of my 28,000 library is unmatched, it takes FOREVER every single time a new item is added.Any reason why it wasnât just put back to how it was? I totally get the idea of wanting to scan, but isnât that the purpose of the âRefresh Metadataâ option? That forces it. Why does it have to do this every single time? I really really is an irritant.
Could we not just have this as an option?
I am certain I am coming off unappreciative, and I want to be crystal clear that I AM appreciative! However, it is still a huge issue compared to 4829 where everything was stellarâŠ
Please could you give me the exact steps you go through that triggers this and I would not mind some logs
Thanks
Here are the logs. Far less time spent on the search, but you can see that it searches a bunch of items that have been in the library for quite sometime.
Also note, another new album was added and it did not pull the information from Last.FM again. In this case, it took the format of the folder name (I have the year in parenthesis) but it grabbed the album art from somewhere. This behavior is different from the past few years (no settings changes in the past few days either) and I have always had the naming structure with the year. âDragonforce - Re-Powered Within (2018)â or âShinedown - Attention Attention (2018)â are the two examples here.
Thanks again.
why one forum topic for the two different issues sonos issue and metadata issue ?
@sa2000 said:
why one forum topic for the two different issues sonos issue and metadata issue ?
Bad etiquette? My bad. I was doing one server issue, multiple symptoms. I shall split them.
Metadata Issue: https://forums.plex.tv/discussion/319591/metadata-not-loading-from-last-fm-server-v1-13-0-5003/p1?new=1
Sonos Issue: https://forums.plex.tv/discussion/319590/server-issues-v1-13-0-5003-metadata-for-music-not-loading-plex-for-sonos-broken/p1?new=1
@âKyle Verryâ said:
@sa2000 said:
@âKyle Verryâ said:
So, the constant rescanning does appear to be gone, however the reason I keep seeing tons of activity is it is STILL scanning unmatched items on every single search. So, since a quarter of my 28,000 library is unmatched, it takes FOREVER every single time a new item is added.Any reason why it wasnât just put back to how it was? I totally get the idea of wanting to scan, but isnât that the purpose of the âRefresh Metadataâ option? That forces it. Why does it have to do this every single time? I really really is an irritant.
Could we not just have this as an option?
I am certain I am coming off unappreciative, and I want to be crystal clear that I AM appreciative! However, it is still a huge issue compared to 4829 where everything was stellarâŠ
Please could you give me the exact steps you go through that triggers this and I would not mind some logs
Thanks
Here are the logs. Far less time spent on the search, but you can see that it searches a bunch of items that have been in the library for quite sometime.
Also note, another new album was added and it did not pull the information from Last.FM again. In this case, it took the format of the folder name (I have the year in parenthesis) but it grabbed the album art from somewhere. This behavior is different from the past few years (no settings changes in the past few days either) and I have always had the naming structure with the year. âDragonforce - Re-Powered Within (2018)â or âShinedown - Attention Attention (2018)â are the two examples here.
Thanks again.
Thanks for the logs.
Regarding the extra unexpected matching of previously unmatched items:
So we have logs covering May 03, 2018 15:23:00 to 16:40:07
Can you please tell me what you did and at what time and what media files this was for and what the result was and I will look into the logs to pick up the related log entries
And again please separate your problems. Again giving times and for the matching issue, what album was added
And I would like to see a directory listing of all files and folders for the new added album and what the library definition is in terms of folders - just want to also see what the root of the library is
So, it appears that I was pre-mature in thinking the issue remained. It appears that the issue has indeed subsided. I have been monitoring it as much as reasonable and I do not see it recurring inappropriately. It seems .5003 has indeed fixed the issue, and I apologize for impatiently stating it was still existent.
@sa2000 said:
And again please separate your problems. Again giving times and for the matching issue, what album was added
Here is the specific forum post for the matching issue. It appears it might just be me, since no one else has chimed in. I am just confused why it is occuring with no change. Odd. I appreciate your help on the matter, if you get a moment.
This is occurring again. Has been on-going from 11:00an PDT (approximatelyâŠthis is the time I noticed it) to current. The logs show the scanning, so just look around the 1pm PDT and you will for sure see it.
I hope there is an explanationâŠbeen scanning for at least 3 hours.
Version 1.13.1.5063
Thanks!
I have followed this thread since I first noticed the symptoms. I confirmed when I saw them. Perhaps mods can look at your logs and see if something unique is happening in your situation, particularly with your large music library or large music addition at one time.
I have two servers running in separate virtual machines, so I get records of how the CPU performs on average across different time periods. When I first noticed this, both servers routinely displayed near 100% CPU utilization on a 24 hour period for more than 1.5 hours each, and the cycle repeated very regularly every 6 hours (matched the setting for the server to update the libraries periodically every 6 hours).
I have continued with updates on both servers through the beta channel. I have not seen the CPU utilization issue that I saw earlier. And both servers are on periodically update every 6 hours.
I certainly hope your problem can be resolved, as I recall how frustrating it was with either living with it, or turning off periodically update (requiring manual update) or down version. Best of luck. I have definitely found sa2000 and ChuckPA to be of considerable help in resolution of this issue (from my perspective). Best of luck.
@âKyle Verryâ said:
This is occurring again. Has been on-going from 11:00an PDT (approximatelyâŠthis is the time I noticed it) to current. The logs show the scanning, so just look around the 1pm PDT and you will for sure see it.I hope there is an explanationâŠbeen scanning for at least 3 hours.
Version 1.13.1.5063
Thanks!
You mention it started at 11am - I would like to see what triggered that. The logs start at 12:51
Could you increase the number of log files - from the default of 6 log files to a large number - suggest 60 and may then able to see what triggers this activity. Also would like to have a look at the database - you could download it and PM the zip file to me
To change the number of log files, have a look at this support article
https://support.plex.tv/articles/201105343-advanced-hidden-server-settings/
You would need to add LogNumFiles and suggest setting it to 60
Once we have a set of logs going back to when the scanning starts then you can change the value back to the default which actually is 5 for 6 log files
To download copy of the database, you can use the web interface
settings / server / help / download database
and please could i have the media info xml for a music track within one of the directories that got scanned eg a track from /Volumes/Drive 2/Current iTunes/Music/Chrome Molly/
https://support.plex.tv/articles/201998867-investigate-media-information-and-formats/
