Plex Keeps Losing Connetivity After recent Update

Server Version#: 4.76.1
Player Version#: Plex, PlexAMP, Consoles, ect

After one of the recent updates, periodically PLEX will just stop responding, and I am forced to go onto the server and kill/restart the Plex software. After restarting the software, connectivity is restored. I noticed this a little while back, but it only happened a few times, so I chalked it up to non-important. Today, it has happened multiple times, so I fear this is a more urgent issue than I presumed.

Adding Log from the latest crash earlier today.

2022-07-26 Plex Crash.txt (22.8 KB)

Sounds like you have the deadlock issue. Take a look at this thread and, if you can, gather the diagnostics requested send them to the developer:

Here are the steps that are needed to diagnose the deadlock in case you don’t want to read back through the entire thread:

Diagnostics for a deadlock / lockout (Windows)

  1. 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 Finding an authentication token / X-Plex-Token | Plex Support
  2. 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
  3. 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
  4. Using this 32-bit Taskmgr.exe find the Plex Media Server.exe process, select it and right click on it and choose Create Dump
  5. Check that the dmp file has been created
  6. Restart the server and capture the zipped logs
  7. Zip the dmp files and upload to Dropbox or similar service
  8. Send @sa2000 by private message link to the zipped dmp files and send the saved /connections output text files and the zipped logs

It really is quite easy to do, rwoffice and I as well as others have sent some data in already; but deadlocks are quite hard to diagnose. I figure that the more data that the developers have the better. Feel free to PM me if you have any questions with the steps.

1 Like

Would need to see more - like the logs after this to confirm if it was a crash or hang

Best to attach the full debug server logs zip as that also identifies the version / platform

Were there any exceptions errors in the Windows Application Event Log at the time Jul 26, 2022 15:46

Would like to see more examples and full server logs zip please

Please Media Server 1.28.2 has just been released as a beta release

It has a fix for a deadlocks issue that was identified last week

  • Server could hang in certain circumstances (#13758)

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