That steep rise in (xx live) count is indicative of a deadlock
Mar 26, 2019 14:25:16.315 [0x7f7a6e5be700] DEBUG - Request: [178.197.232.167:54913 (WAN)] GET /activities (192 live) TLS GZIP Signed-in Token ()
Mar 26, 2019 14:26:29.278 [0x7f7a6e5be700] DEBUG - Request: [69.162.124.237:9961 (WAN)] GET / (260 live) TLS Signed-in
There is a standard set of diagnostics needed for deadlocks
- List of connections.
- Process Dump
- Debug logs
Connnetctions List: That would be obtained through a specifc url in a browser. You would need the server security token for the request and you can prepare it by going through the steps here https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
In the event of a deadlock, open browser and go to this url to get the list of connections on the server
http://192.168.1.4:32400/connections?X-Plex-Token=xxxxxxxxxxxxx
put the server security token instead of the xxxxxxxxxxxx
Note down the time and copy the displayed output into a text file - with time of request part of the filename
Wait 5 minutes and confirm it is still locked out by trying out http://192.168.1.4:32400/web
and if it is, repeat the /connections request and save the output again
Force a process dump by finding out the PID of the Plex Media Server process and doing a kill -SEGV <pid>
This should result in a crash report being written to /volume1/Plex/Library/Application Support/Plex Media Server/Crash Reports/1.15.2.793-782228f99/PLEX MEDIA SERVER
Restart the server and wait few minutes. With crash reporting enabled, the dmp file should get uploaded
Capture server logs zip and attach with zip of the 2 connections lists captured.
If there are difficulties uploading the dmp file, it will remain there until it is successful - an attempt is made after each launch of the server
