I’ve been having periodic server crashes at night and got the same error codes as the OP. Can’t really make sense of them though…
Here is the crash log: Sep 21, 2021 02:14:21.443 [7724] INFO - Crash Uploader - Platform: Windows Serve - Pastebin.com
Here is the server log: Sep 21, 2021 02:11:59.306 [10124] DEBUG - Jobs: 'C:\Program Files (x86)\Plex\Ple - Pastebin.com
(Pastebin seems to removing the longer one so let me know if it goes dead…)
hi no its topped for a couple of months now im getting it twice a day now.
Plex Media Server Logs_2021-12-22_20-52-24.zip (6.8 MB)
Could you get me zip of the database - send it in private message. I will have a look on Friday
hi the database is 146mb it wont let me send it.
zipped size ?
If it is - try to upload to dropbox / google drive etc and send me a link for download
Thanks for the logs and the database zip
Can see a crash at 18:39 on 22nd December
Unfortunately I cannot locate the corresponding crash report for this on our crash reporting system. I found a crash report from 18th December at 13:54 but I do not have the logs for it
Can you see if there are any dmp files in this directory for Plex Media Server
C:\Users\djkev\AppData\Local\CrashDumps
Dumps would get saved there by Windows if windows registry is adjusted to get windows to capture the crashes
See this article which mentions the edits
Crash Logs: Plex Media Server | Plex Support
I will refer what I have to the developement - which is a dump with no logs for the 18th December and logs without a dump for the 22nd
In the meantime suggest doing the registry edits and on next failure = see if there is a dmp file in the CrashDumps directory in %LocalAppData% and let me have zip of then dump (link for uploaded fo;e sent privately) plus logs zip
Hi
Further to my earlier reply - we do copy the crash dumps to %TEMP% after processing
Could you please look into this directory
C:\Users\djkev\AppData\Local\Temp
for any file with a name
a9197e04-1ce8-4081-913b-24e6ea28ca3d
It may have a .dmp extension (or it may not)
If you find it, please zip it and send me the zip by PM
Thanks @Swiftserver for looking for the dump file and finding it
I have analyzed it and passed it to the development team
Not sure where I should post this, but I was having issues with my database running out of memory and crashing the application, but I believe I’ve found a decent workaround for the issue.
I have a fairly large library, my com.plexapp.plugins.library.db file is 980MB and com.plexapp.plugins.library.blobs.db is 2.3 GB. However, these files (Along with all other plex metadata) are placed on a 2 TB Samsung 960 PRO NVME drive, so disk access speed shouldn’t be an issue. The system is running on a 10th gen i7 processor with 64 GB of ram, so I didn’t think there are any performance bottlenecks.
After digging through my logs, I was seeing a lot of the following:
Dec 24, 2021 14:35:01.817 [3108] WARN - SLOW QUERY: It took 13640.625000 ms to retrieve 30 items.
I noticed that the extremely slow (5+ seconds) queries were only occurring when users went to the “Home” page of plex. I had enabled recommendations, ex: “More in (Genre)”, “More from (Network)” a while ago, and also had increased the settings for “Weeks to consider for Continue Watching” (10) and “Maximum number of continue watching items which will appears” (15). These changes were probably made about 6 months ago.
Additionally, I had enabled the memory logging for the database, and whenever the extremely slow (5+ second) queries happened at the same time – ex: Multiple users hitting the “Home” page at the same time, the memory usage would VERY quickly spike, going from 100 MB to 1500~MB, then crashing the application once it hit the 32 bit limit.
I modified the settings for Movies/TV Shows to disable most of the recommendations:
I also reduced the “Weeks to consider” to 4 weeks, and the “Maximum number” to 6. After making these changes, I rarely see any queries go over 50ms and the application has been crash-free for around 5 days when I was seeing 1-3 crashes every day before.
i gonna give that a try,im not sure what the problem is its stop crashing for a while then its started back up a couple of weeks ago.i run emby and jellyfin smooth with now issues.
na didnt work its still doing it,it has crashed 5 times today.
Hi - The crash is a timing issue with loading of the Continue Watching hub. I have an alpha 1.25.3 build with the fix if you wish to have it - or wait for the 1.25.3 beta release
You could see if your issue is that massive number of extras / trailers one which led to massive databases and memory allocation failures and related crashes
See this post for how to determine if it is this issue
yeah ill have to try that see if that fixes it.
sent you alpha build 1.25.3.5368-3c4492180
its hasn’t made a difference it has crashed 3 times today.
Would need dump and logs
See if you can find in %TEMP% 3 files created the same time as the 3 crashes and get me one of them with server logs covering time of the crash
Thanks for the logs - we are not crashing any more but there is evidence of a deadlock leading eventually to hung requests and requests failing with error 503 Service Unavailable
See 503 Service Unavailable - #92 by sa2000 for diagnostics for deadlocks on windows
I already looked into that before my post above – I removed 7 entries that had 30k+ associations. I’ll check it again, but I haven’t had a single crash since I removed the recommendations/changed “on deck” configuration…
