Devs are probably already aware, but I am experiencing stability issues with PMS 1.13.6.5339 for Windows. I run two separate windows boxes with PMS, one runs Windows Server 2016 (fully updated) and the other runs Windows 10 (fully updated). On both of these boxes, after the update to 1.13.6.5339, plex began crashing intermittently, and frequently. Logs are inconclusive and I have my servers setup to automatically restart PMS if it crashes so I haven’t been able to grab crash reports since they are deleted once uploaded.
Downgrading to 1.13.5.5332 fixes the issue, and checking back on my monitoring logs, the issue began immediately after the automatic update to 1.13.6.5339. The issues to not affect PMS for Mac. My Mac Pro is still running 1.13.6.5339 with no crashes or issues.
Just wanted to mention this in case the devs weren’t aware.
I have had the same version of Plex Server for Windows (1.13.6.5339) crash twice in the last 12 hours. I have enabled debug logging and will upload the logs if/when it crashes again.
have looked at the logs - the crashes are arising when detecting the dvr on http://10.0.1.127:80 - an issue with the sqlite3 database.
Need to establish if seeing airtame.com via ssdp is relevant to the crash
As per my private message, please let me have a zip of the databases folder and also also some detail of your network setup and what ip is airtame.com device on
I don’t use any airtime device. I have an HD Homerun on the network. I haven’t ever heard of airtime.com until this post. My network isn’t even on a 10.0.1.* subnet.
As I said in my PM, I don’t think Airtame is the cause of the errors. They are Chromecast-like HDMI display devices and since your messages, I have disabled SSDP on them. But those SSDP errors have been there since I installed the airtames a couple years ago.
The HDHomeRun is the network-based version, and I use it with one of my windows servers and my Mac Pro, but not with the other Windows server… which still crashed on 1.13.6.5339, so it seems like that might not be the issue.
The one thing that both of the Windows servers that crash do have in common is that I have multiple NICs on them. However, I also have multiple NICs on my Mac Pro as well… although I realize that if the bug is related to multiple NICs, it wouldn’t necessarily affect the Mac as well since the architecture is so different.
I downgraded both my Windows servers to 1.13.5.5332 since I needed PMS to run stably… so I can’t really test if anything fixes the issue without upgrading to the broken version again. But if you have a fix you think will work, let me know and I can upgrade again and attempt the fix.
