Hi -
Over the last few weeks I’ve been having multiple instances where the plex server process keeps running but becomes unresponsive. I am not even able to connect to localhost to view the connection page with my x-token. I need to restart the process to get it going again. I’ve included the dubug logs and dump as per sa2000 on this thread on a similar deadlock/lockout on Windows. As noted, unable to get to any of the debug pages with my x-token during these unresponsive episodes.
I am running Plex Server 1.12.3.4973 on Windows 10 1709 build 15299.371
Logs attached
Process dump here
Any insights appreciated! Thanks!
Still happening 
Updated my Nvidia drivers to the latest version and on Plex Beta (1.13.0.5003) because I’m already experiencing DAILY crashes so, hey, why not?
Process still running but server unresponsive.
Debug connections webpage output attached (first time it has been reachable in my case).
Attempted connection to http://127.0.0.1:32400/web/index.html gives me a 503 error.
Tautulli not reporting as Server being down but there are a bunch of reachability requests pending as per the debug connections log.
No crash dumps present (folders empty).
Logs from immediately after a restart attached.
Server memory dump available if anyone actually comes to help but I’m losing hope
I would love to find a solution to this. I’m getting rather tired of daily restarts of Plex when it silently goes dark.
Next beta, still same issue. Version 1.13.0.5023
Sometimes I can get to the connections debug pages, other times not.
Here are the logs from crashes on May 4th, 8th and 10th.
Still hoping for some help on getting to the bottom of this…
I’m wondering if it’s the scanner that is causing the problem as I get a whole bunch of
ERROR - Error issuing curl_easy_perform(handle): 7
in the scanner logs.
@yarascavitch said:
Next beta, still same issue. Version 1.13.0.5023
Sometimes I can get to the connections debug pages, other times not.
Here are the logs from crashes on May 4th, 8th and 10th.
Still hoping for some help on getting to the bottom of this…
I’m wondering if it’s the scanner that is causing the problem as I get a whole bunch of
ERROR - Error issuing curl_easy_perform(handle): 7
in the scanner logs.
looks like a deadlock resulting in requests stacking up. We will need to get the diagnostics for that which just adds a process dump - perhaps a couple to the logs and connections output
Diagnostics for a deadlock / lockout (Windows)
- Prepare yourself by finding the server security token string as it will be needed for the connections list request. To find the token string, see this support article https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/ (you already know how to do this)
- When the problem occurs (and please wait for sufficient time before capturing diagnostics 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=xxxxxxxxxxxxxxxxxxxxxwhere 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.exeprocess, select it and right click on it and chooseCreate Dump - Check that the dmp file has been created
- Adding a new step because of recent deadlock investigations into one recent case, wait another 2 minutes and confirm that requests to the server home page (
http://127.0.0.1:32400/web) do not get through and then repeat steps 2 to 5 (so we have 2 sets to compare) - 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
/connectionsoutput text files and the zipped logs
Thanks
1 Like
Thanks. Happened again tonight. I’m PM’ing you the link for the dumps and logs. I’ve included everything by date in subfolders. Not able to grab debug connections tonight (only rarely is it responsive in my situation). I’ve included two dumps in the crash tonight as per your updated instructions.
Many thanks!
@yarascavitch said:
Thanks. Happened again tonight. I’m PM’ing you the link for the dumps and logs. I’ve included everything by date in subfolders. Not able to grab debug connections tonight (only rarely is it responsive in my situation). I’ve included two dumps in the crash tonight as per your updated instructions.
Many thanks!
Thank you - it is good diagnostics.
The lockout happened at 21:14 and was still locked up when the dumps were captured at 22:01 and 22:05
The type of lockout was that no requests would be accepted - not even the special /connections request !
I have referred the diagnostics to the development team for investigation
Thanks
Posting here again as am having the same symptoms as previous with the lockout. Unable to get to the debug connections. All web connections to the server refused. It was good for a couple of weeks though! I’m now on 1.13.2.5102. I will PM you with the log and dump link. It’s still a dropbox folder with all the info by date. Latest crash in 2018-06-03. Thanks.
have sent you a PM with development build 1.13.4.5217 to update to. Changes were made to address this deadlock.
Plex Media Server version 1.13.4.5251 has just been released as beta. It has fixes for two deadlocks following investigations from diagnostics provided in this forum thread
See Release Notice Plex Media Server
- (Playback) Rare deadlock with stopping sessions (#8659)
- (Streaming Brain) Rare deadlock involving bandwidth limits (#8498)
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
