Sorry, I have several servers. They all crash, but I wrote a test script which resides on one VM which allows me to trigger the butler task (and thus crash Plex) on demand. I will trigger a crash and send everything for the same server. I didn’t realize I flipped them. I should have it here in a few minutes.
Thanks - the crash is arising because a music track or number of tracks do not have an album entry in the database. We do not know at this point why the database for some albums is absent
The database from the other server that is from the 24th December does not show any missing album entries - did that server crash before the 24th ? There are tracks relating to themes which do not have album entries but I would not expect these to be involved
PM sent with new logs, dump, db, and blobs.db.
I sent you alpha build 1.30.2.6492 - which should fix the crashes on the Over The Top server
The database you sent me from the 24th December from the other server does not show the presence of the issue that would lead to a loudness scheduled task crash = if it was crashing before the 24th December db backup file was generated then I would need to see logs and dump file(s)
1 Like
Installed 1.30.2.6492 alpha and triggered butler test for LoudnessAnalysis. Alpha build does not crash, so that regression is fixed.
1 Like
Sorry I posted it in the wrong thread. I sent you a pm as well 
Would be so good to have that fixed 
I got your database. It does not show the issue that I referred to - the one that leads to crashes when scheduled tasks run music loudness analysis
So your issue is different an I would need the debug server logs to start an investigation and identify which dmp files to look for
I tried all the other suggestions, but the only way I can keep my Plex server up consistently is to delete my Music library. I deleted it 3 days ago and this is the longest my server has been up for 2 months.
Can anyone tell me where I find the alpha release? I can’t find it for download, and the crashes are creating a lot of problems for me. I’m using Qnap [ARMv7 (TS-x31+, TS-x31P, TS-x31P2, TS-x31X och TS-x31XU-series)]. A previous release is also ok.
1 Like
@sa2000 Do you have enough information to roll on a fix, or do you need my database as well? I have disabled “Analyze audio tracks for loudness” and I have not experienced a crash since.
Happy to help in any way I can, but would also prefer to keep my server alive whenever possible.
I am sending out the alpha release to users that I receive server debug logs from showing the specific crashes issue that is fixed in that release. If identified, I am also requesting a zip of the database to investigate
I have come across two different crash manifestations that are both covered the fix in the 1.30.2.6492 alpha release - which I expect to be released as beta sometime next week.
One - which is the one seen from most users - is due to music tracks not having an album entry in the database. We don;t know how that arises and a copy of the database would identify how recently the related tracks were added to see if it is an old issue surfacing now or new issue.
Thanks for the logs. Although the crash is the same as the other loudness analysis ones seen by other users - the cause appears to be different, The database does not appear to have any missing album entries
The fix in 1.30.2.6492 alpha will stop your crashes as well and I will be discussing your specific manifestation of the crash with the development team
“Butler: Scheduling loudness analysis for album 365586”
See my thread, seems to be the same problem - an album which is not in the database trying to be scanned
I now have your database and logs - you are not running on the 1.30.1 version that is crashing for loudness analysis
Your server is running on 1.30.0.6486
OK, but it does crash every night. And it didn’t crash last night after I disabled loadness analysis. So it should have something to do with it. I can try for a few more nights, but I think it will crash again if I enable loudness analysis.
Running 1.30.1.6497. Same issue - crashing every night at 2AM when scheduled tasks start. Disabling loudness seems to have fixed it.
1 Like
Here too, my Plex Server 1.30.1.64 on a Synology Nas type 1819+ with DSM 7 crashes everey night since the last update.
Now it’s been four nights without any crash with 1.30.0.6486, since I disabled loudness, so this version has to bee affected as well. Before disabeling loudness, it crashed EVERY night.
Do I need a crash before database submission?
