Thanks for the logs. The 503 responses get returned when the number of queued requests reaches a very high level. This followed a deadlock situation where a thread locked out other threads within the Plex Media Server. This happened around 8:55 pm
Deadlock investigations require a process dump as well as the logs and the output from a specific request that one can make in a browser to get the list of the connections.
Please follow the following steps to capture diagnostics for the next deadlock
Diagnostics for a deadlock / lockout (MacOS)
- 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 can also find out by hovering mouse on theDownload Logsbutton within Help and right clicking and selectingCopy Linkand pasting the url in a text file and extracting theX-Plex-Token=string from it to use later - 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 get a
sample processof thePlex Media Serverapplication throughActivity Monitor- see https://support.plex.tv/articles/201373203-gather-a-process-dump-or-sample-process/ - Restart the server and capture the Plex Media Server zipped logs
- Attach all zips and process sample dump captured to a forum post here
- Send the text file containing the output from the
http://127.0.0.1:32400/connections?X-Plex-Token=xxxxxxxxxxxto me by Private Message
(Test out that you can get the connections list in advance so when the time comes you are fully aware of the syntax and approach)
Thanks