503 Service Unavailable

Plex Media Server Desktops & Laptops
81

On **1.9.0.4252 ** Windows while optimizing some movies, Plex throws 503 error still.

82

@joeofportland said:
On **1.9.0.4252 ** Windows while optimizing some movies, Plex throws 503 error still.

Yes - there appears to be another bug so the released fix did not resolve the issue completely.

This is with the development team and we have dumps and logs already

83

Good News - Version 1.9.1.4272 is out now and available from https://plex.tv/downloads

It has a fix for the deadlocks

  • (Transcoder) Deadlocks when performing concurrent static and streaming transcodes (#7554)

Thanks to @br3nn88 for giving it a good intensive test and feedback is that this transcoding deadlock is now fixed

The release is initially available to Plex Pass

84

hi
i hit til link, and got to the same version i already got.
any direct link til the new update ?

2 Likes
85

use version Version 1.11.3.4803 , the only one working ok for meā€¦

86

@chillumsen said:
hi
i hit til link, and got to the same version i already got.
any direct link til the new update ?

Not sure why you are posting in a 2017 forum thread for a deadlock that was resolved in September 2017. There have been many deadlocks fixes since then

The current beta release is 1.13.2.5102-4898d7d96

87

@chillumsen said:
hi
i hit til link, and got to the same version i already got.
any direct link til the new update ?

I have gone through the deadlock diagnostics provided and have responded here
http://forums.plex.tv/discussion/comment/1675015/#Comment_1675015

88

im geting 503 Service Unavailable alot these days -

89

Yep, somehow it came back.
Got 3 times 503 Service Unavailable on my server past week.

90

@PLEXarinn said:
im geting 503 Service Unavailable alot these days -

@Madshark said:
Yep, somehow it came back.
Got 3 times 503 Service Unavailable on my server past week.

Would need to know what url connection the 503 is being returned for

If it is on requests to the server, eg http://127.0.0.32400/web then that would indicate exhausting resources after a deadlock that happened earlier and the load on the server of queued requests has now exceeded 1000. If it is this then would need to capture diagnostics for the deadlock

This forum post outlines the diagnostics for a deadlock on a windows plex media server
http://forums.plex.tv/discussion/comment/1668490/#Comment_1668490

If it on requests to https://plex.tv then that I would need to refer that to the relevant support team. Would need to know the time and also what nslookup plex.tv returns for you

91

Same thing for me, on Version 1.13.4.5251
I believe been happening since 1.13.0.5023ā€¦ I get complaints that itā€™s down, but process is still running. I check localhost:32400 and I get the 503 Service Unavailable error.
Towards the end of the log, all I see is this being repeated:

> Jul 13, 2018 22:37:21.487 [4976] DEBUG - EventSource: Got event [data] '<Message host="snipped" port="443" command="startRelay"/>'
> Jul 13, 2018 22:37:21.487 [4976] DEBUG - Relay: already have an active relay connection for this server
> Jul 13, 2018 22:37:24.140 [1416] DEBUG - Auth: authenticated user 12345 as snipped
92

A number of bugs giving rise to deadlocks have been fixed already with two separate fixes going into 1.13.4.5251 - I am aware that there is still a deadlock bug in 1.13.4 and we are waiting for the diagnostics so it can be investigated and fixed.

Deadlocks can only be investigated from process dumps together with logs with debug logging enabled and also a list of connections at the time.

The snippet of log you found would be for actions that are not impacted by a deadlock

Please could you follow the steps outlined below so that the problem can be identified and fixed

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 https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
  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 me by private message link to the zipped dmp files and send the saved /connections output text files and the zipped logs
2 Likes
93

Thanks, I will do this next time I have a chance. It seems to occur approximately once a week.

94

Thanks for this. I have been experiencing this as well. It seems to happen every few days. The next time it happens I will get a set of log and dmp files as you instructed. I am running PMS version 1.13.8.5395 on Windows 2016 server.

95

Now, is there a way to send me an alert when this happens? I have set Tautulli to alert me, but it seems that Tautulli is not aware the server is unavailable whenever this happens. So I never get an alert.

96

The point when 503 errors are returned is some time after the start of problems - where client app requests would timeout and showing server unavailable. 503 is returned when we reach a point of over 1000 queued requests. Normally users establish there being a problem much before that

97

So I guess that means thereā€™s no way to alert me when the server begins to fail this way? Iā€™m guessing a Powershell script that if it gets ā€œhttp ok 200ā€ response, then itā€™s ok, but when it gets a 503 it sends me a text message?

98

That should be fine - do make sure you do not make the interval between test requests too short.

99

Thank you. I will give that a shot. I have some programming skills. Maybe I will set the script to check every 10 minutes or so.

100

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.

See Release Notice

  • (Transcoder) Resolved a rare deadlock (#9332)