Hello, Since I activated sonic for the analyzes of my albums, the server crashes every time the analysis is finished. i have to restart it every time. Is a server update scheduled to resolve the problem? If not can you give me a solution?
I also have noticed this since I enabled the new Sonic Analysis feature on my Synology DS718+. Plex has been running smoothly for a long time, but now crashes (seemingly randomly) but frequently. My own logic seems to think it’s related to Sonic Analysis as the logs are either vague or undecipherable - for instance:
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.24.4.5081-e362dc1ee/PLEX MEDIA SERVER/65c46396-4fbd-466c-a4458da6-d917eafa.dmp
I then try and open said file, but it is several MB in size and often contains incomprehensible text / characters.
In my efforts to understand what was happening, I stumbled across this post, which I tried but did not resolve the issue as I’ve experienced a couple of random Plex Server crashes since - again for context, I tried the following:
This did not really do anything for me, and rebuilding indexes did not seem to do anything (I essentially rescanned my music library after the above).
I don’t want to disable Sonic Analysis, but I may have to if this is the only way to stop my Plex Server from crashing (plus I hope it does actually fix it)…
EDIT: Updated with some info
Looking at my crash dumps (located in /config/Library/Application Support/Plex Media Server/Crash Reports), it looks like I had zero *.dmp files until PMS was updated to version 1.24.3.5033-757abe6b4 where I started to get random crashes in the PLEX MEDIA SERVER folder where several *.dmp files are now found. In all previous versions (starting at version 1.17.0.1841-d42cfa161 have no *.dmp files, so I’m guessing this is related to the introduction of the Sonic Analysis feature.
I’m still a bit confused as to how it happens, maybe automated scans kicked off from dumping new music in?
I don’t have automated scans, I only run sonic analysis after a scan, and I’ve never seen the issue, so this might imply a way to workaround the bug.
Ok, good to know. So maybe turn off “Run a partial scan when changes are detected” and just scan manually after adding new media, or let the scheduled scans pick stuff up?
@elan, does the latest release (v. 1.24.5.5173) fix this issue? I looked at the release notes, and it only mentions:
(Library) Sonic distances were incorrectly displayed in some cases.
It doesn’t sound like it’s related to the above, but it would be good to know. And if it’s not the fix, could the release make it clear that it fixes the server crash (if that is indeed what it was)?