PMS crashes daily with 503 Service Unavailable

Over the last month or so Plex started crashing almost daily.
All playback would become unavailable and the web interface would display a 503 Service unavailable error.

Simply existing the application and launching PMS again fixes it for another day or so.
These crashes seem to be happening while no one is actively watching anything, and I have yet to have it crash on me while i’ve been watching anything.

I downgraded from latest beta to latest public and i’m still having the same results.
This seems to have coincided with the latest batch of cumulative updates and service stack updates from MS, however this might simply be incidental.

I know other people have been experiencing this lately.
Anybody who can help shine some light on this or point me in the right direction ?

Logs attached.

OS Windows Server 2016 Standard on VMware ESXi 6.0.0, 5572656 VM version 11
Server Version#: 1.16.3.1433
Player Version#: NA

<If providing server logs please do NOT turn on verbose lPlex Media Server Logs_2019-08-02_00-46-16.zip (4.2 MB) ogging>

Appears to be buildup of requests that are not being cleared down. Would need /connections list and process dump to go with logs

See this post fpr diagnostics

Thank you.

Here is the connections list and crash dump (in RAR format. Let me know if you need it in ZIP).
Since the external connections arent “mine” i’ve obfuscated IPs, Usernames and PMS server names from external connections.
Let me know if you need the raw dump.

[sa2000]: Removed link to dump

Connections-Obfuscated.txt (658.2 KB)

Also a correction to my earlier post:
OS is Windows Server 2012 R2 Standard 6.3.9600.
Below is a list of installed features and updates:
features.txt (51.5 KB) updates.txt (27.4 KB)

Thanks - can’t find any Plex Media Server logs corresponding to the dmp file.

Links to download dumps best sent privately as dumps may contain sensitive data

For anyone else who has this issue it seems to have been resolved in the last two versions.

which version do you believe fixed this first

I am on 1.16.5.1554 now.
So it would have been the one immediately before that.

I am still having crashes, and also stated to see this immediately after the Windows 10 mandatory updates.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.