All of the latest updates (every 1.19.x version) are crashing my server as soon as they are installed. I have rolled back to several different versions, and they will run fine at first but ever since I tried to install that first 1.19 version, my server has been crashing daily between 6AM-9AM no matter which version I use.
I’ve honestly been too busy to try and look deeper into it so I’ve just been restarting the program every morning when I wake up and it’s worked fine throughout the day, but now I’d like to try and solve this. I’ve had this server running for a long time and have never had any major issues so I’ve never really needed to check logs and probably need a bit of a primer for where to start.
A few log questions in no particular order:
Can I delete everything in the logs folder? This server has been running for years and the Log folder is currently 1.72 GB.
Which log files do I want to focus on? There is an Installer Logs folder but when I’ve seen other people upload logs that’s not included, and I definitely have some older style outdated logs that are from around 2016
Are the 1-5 numbered files just the 5 latest logs?
What is the best practice for uploading logs? Just zip the whole logs folder? I know the server name is included in logs, is there any other identifying information that should be removed?
I’m having the exact same issue. The longer I keep my server running, the more it slows down. I even did a fresh install of my OS thinking that might be the issue. I restart my server every morning when I get up now. I’ve tried rolling back and I can’t figure out where the problem started.
Yes also having an issue with the server crashing at around 3am - restarted today but has already crashed a few times since. Never had this issue until yesterday.
My server is up to date but it crashes about once a day. It would be great if someone could take a peek? Most recent crash was sometime late overnight 5/21-22.
Earlier this week my Plex server started crashing every few minutes after Windows Update rebooted my computer. I found that setting these things to never allows it to keep running:
Today I saw the update to Version 1.19.3.2843 which included a note about fixing a crash when doing the new intro detection on older hardware. My server is about 10 (a Dell Precision 490) so I hoped that might include me.
It did not. When I changed the four settings back to “As a scheduled task and when media is added” PMS crashed within a minute of hitting the SAVE button. I restarted PMS, set them back to never and it has been running fine for the past 90 minutes.
Thanks for the info nurbles. I keep having this same issues on PMS running on windows 7 from the past few updates. Tried reinstalling PMS and a bunch of other things in windows to no avail. Including Logs: Plex Media Server Logs_2020-05-21_23-17-35.zip (953.5 KB)
I will change the settings you have mentioned and report back.
I think this may have something to do with the PMS icon or other local files. Every time I hover over the PMS icon in the taskbar, the server seems to crash. Also it seems like there are too many versions of PlexScriptHost.exe running and they are using more memory than normal. These process stay active even after PMS crashes and ending the PlexMediaServer.exe process manually. Maybe it has something to do with python?
I have the access to the previous two PMS versions through windows restore points and I’m wondering if I should reinstall with one of those to see if that resolves the problem.
When Plex Media Server crashes then a Windows quirk is that you will still see the icon in the tray, but when you hover over the icon it will then refresh and disappear. So the icon is not related to the crash, it’s just the windows tray catching up with the fact that PMS crashed earlier on.
There’s an even newer test version of PMS in this thread that has fixed the crashing issue for some other users; I think it will be generally released on Monday. Apparently some new feature was using an Intel instruction not supported on certain hardware and this was crashing some setups. It might work for yourself.
In my own case it seems that the Intro Detection process is having a major issue with some of my media or hardware at some point and blue screens my aging server. It did it two nights in a row during scheduled analysis since the new Intro feature was introduced. Yesterday I turned off the Intro detection entirely and thankfully there was no BSOD during scheduled analysis last night, so at least I have that fixed. When I’m braver I’ll try turning on Intro Detection again to see if my specific issue has been resolved. I’m also going to see if I can scan for corrupt media files in my library.
@jdbrookes thanks for the link to the other thread! I downloaded and installed the version available there [Version 1.19.5.2847] and it is working great – and the new intro detection is really nice when bingeing old Doctor Who episodes! Let’s hope they release it for everyone soon!
Awesome thanks for the info guys. Nurbles disabling those four options worked for me too and I haven’t had a crash since.
I forgot to say that I am running PMS on windows 7 pro on a probably 10 year old desktop.
Thanks for the link to that testbuild! I’m going to install it now and see if it works properly.
