When plex rolled out the new agent/scanner I went and re done all my file naming to match 100% their standards & recommendations. I went 1 step beyond that and added external matching ids from tmdb to every movie and show. Took a while as I have a mid sized library but once done I now NEVER ever need to worry about matching and the scanner runs like a dream.
I am however on linux. Windows is just about as evil as IOS so I am most likely getting performance benifits by running on linux
It’s only during scheduled maintenance. I’ve been renaming, adding movies, etc back into the server all day and not one error. If I run a library scan manually it works just fine.
It’s why I’m so puzzled about it. I just now had an instance where I couldn’t get to my account, but after refreshing the web interface a couple of times it let me in. No errors in event viewer when I ran the Scan, either.
I’ve been working on renaming mythbusters,. I started on that yesterday and only got part of the way through. I’m kind of wondering if there’s a way to scan for corrupt video files? I suspect that I might have some.
Would be happy to look into specific crashes if you can get a crash dump (from current public or beta release) plus debug server logs covering the time of the scanner crash
Would of course need to identify the file (files) that are getting the scanner to crash and would need these files as well
Here is what I have as of now. Hopefully something turns up. As to identifying the files, I honestly don’t know how to go about that. If you have pointers, I’ll work through them.
I’ve gone ahead and increased the maximum log files to 10, but those won’t be a factor until tomorrow. In the meantime, here’s the files I’ve assembled.
Thank you. The scanner crashes are happening during Music Loudness Analysis. I have responded to you in PM to locate the 2 tracks that are causing the crashes and reproduce in a test library with the album(s) so we can get logs to go with the dumps. The increased number of logs did not help and only covered the last 10 loudness analysis scanner jobs
From a serviceability standpoint, could logging also be improved here ? As a suggestion to development, if bad files are detected a message with what file it was be output to the plex logs. Would really help in the situations where bad files are getting processed and would save having to examine dumps.
They do show up in the logs, but if you have a big library they can just roll through and be missed. A Dashboard notification would probably be a good idea.
Plus, from a security standpoint, a crash could be refined into an exploit if someone could figure out exactly what was causing it, and find a way to make the Scanner do what they want it to. I have no idea if if that would’ve been the case, here, but I do certainly appreciate the lengths sa2000 went to to help me narrow it down.
Yes thanks for the files - also had other albums from other users. There were a number of different bugs that were giving crashes. The beta has the fixes for all the ones we identified