Hi, am currently running Plex on server 2012 (was running on win 10 on a VM still had same issue). Every day at some point my plex server crashes. The icon is still in the tray down the bottom right, there are multiple proccesses running the process log, but when trying to access plex I get a 503 error. I have tried optimizing the database, moving plex install to another machine, and doing a fresh install of plex. I do have up to 10 - 15 users using at one time, but this has never been an issue up until recently. Any help you could give we be great. I have attached the log files from the last two times I have had to do a restart on the PC. Also the output from http://127.0.0.1:32400/connections?####### before I did the restart, when plex was locked.
Plex Version 1.13.5.5291
I am also running plexpy on another PC, with the IP of 192.168.1.99.
Sorry for long time before replying. Your post got missed (you could bump every few days)
I have looked at the logs which lead to the two deadlocks
Logs for August 11 from 17:10 up to 19:54 with server locking out at about 19:42
Logs for August 12 & 13 from 22:55 to 07:47 with server locking out at about 00:55
For deadlocks which is what this was, we need also process dumps as well as the /connections output and logs
You mentioned you captured the http://127.0.0.1:32400/connections on the server but I do not see any such requests getting to the server in the periods covered by the logs as mentioned above. I need to know the time of the request and would need to see it is the log
Also you mentioned 503’s - which does arise on deadlocks after a while. The logs did not show any 503s being returned.
I will summarize below the diagnostics for a deadlock - I would recommend running on latest beta if you do not mind
When the problem occurs (and please wait for sufficient time before capturing diagnostics or restarting eg 10 minutes of requests to the server not getting through) , get the output from a specific browser request on the server. In a browser, go to this url http://localhost:32400/connections?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxx where you put the server token string instead of the xxxxxxxxxxxxxxxx. Copy the displayed output to a text file and save
Next is to force a process dump for the Plex Media Server.exe process. We can do this with Windows Task Manager - but on a 64-bit windows and with Plex Media Server.exe being a 32-bit application, you would need to load the 32-bit x86 version of windows task manager. So load this program instead of the default task manager C:\Windows\SysWow64\Taskmgr.exe
Using this 32-bit Taskmgr.exe find the Plex Media Server.exe process, select it and right click on it and choose Create Dump
Check that the dmp file has been created
Restart the server and capture the zipped logs
Zip the dmp files and upload to dropbox or similar service
send me by private message link to the zipped dmp files and send the saved /connections output text files and the zipped logs
With the release of a fix for deadlocks in 1.14.0.5468 beta - i am closing this topic, For any new deadlocks which lead eventually to 503 Service Unavailable errors being returned by the server, a new forum topic should be raised.
Plex Media Server 1.14.0.5468 has just been released as Beta. It has a fix for the deadlock seen in diagnostics provided in this forum thread.
