Updated to the latest version. Same problem.
All you need to do is start optimizing a few movies… it will crash 100% …
Have not looked at the logs - but the 503 error and the loads of authentication log entries mentioned by @astrofisher earlier are indicative of a deadlock where a Plex Media Server process thread locked out everything else. For such problems, one needs to get the output from http://127.0.0.1:32400/connections?X-Plex-Token=xxxxxxxxxxxxxxx and dump the Plex Media Server.exe process and provide the zip of the dmp file, output of the connections request (if successful) that together with zip of all the logs.
See this article for how to find your server access token string
https://support.plex.tv/hc/en-us/articles/204059436-Finding-an-authentication-token-X-Plex-Token
when a deadlock occurs, requests start to queue up and the logs would show them coming in and then after a while only the authentication log entries are made and when a certain threshold is reached, all new requests get bounced with Error 503.
The culprit thread that caused the deadlock needs to be identified and the process dump together with the rest of the info and logs should help with that
Looks like I am in the same boat. It’s been happening for a few weeks. As soon as it happens again I’ll try to get the inform sa2000 is recommending.
Been happening for a while now. Thought it was just me…
Has there been any update on this… I run plex off a iMac with a few Hard Drives connected… I can not access my server at all right now. Any thoughts?
@scottmifsud said:
Has there been any update on this… I run plex off a iMac with a few Hard Drives connected… I can not access my server at all right now. Any thoughts?
Have you had logs looked into ? Cannot assume it is the same issue unless the logs showed it as being the case
There is no update as I am waiting for the diagnostic information requested earlier - only from users where the logs did show the deadlock issue
Had this a few days ago… will provide dmp, connection output and logs next time.
I’ve also had this a few times over the past few weeks as well, only killing the exe from task manager and relaunching Plex works. The requested information is attached as 7z. Thanks.
Windows Server 2012R2
Plex Version 1.7.5.4035
PlexPass Channel, if that matters.
Thanks!
@pettcomputers said:
I’ve also had this a few times over the past few weeks as well, only killing the exe from task manager and relaunching Plex works. The requested information is attached as 7z. Thanks.Windows Server 2012R2
Plex Version 1.7.5.4035
PlexPass Channel, if that matters.Thanks!
Thank you very much. Hopefully the culprit will now be found
I haven’t had a deadlock since my last post. If it does happen again, how do I get that dump that’s requested for the .exe? I’m sure more logs wouldn’t hurt if I happen to get one.
@celegorm13 said:
I haven’t had a deadlock since my last post. If it does happen again, how do I get that dump that’s requested for the .exe? I’m sure more logs wouldn’t hurt if I happen to get one.
and the output from http://127.0.0.1:32400/connections?X-Plex-Token=xxxxxxxxxxxxxxxx at time of deadlock
@celegorm13 said:
I haven’t had a deadlock since my last post. If it does happen again, how do I get that dump that’s requested for the .exe? I’m sure more logs wouldn’t hurt if I happen to get one.
The way I got mine was to open Task Manager on my Plex Server, find the Plex Media Server.exe and right click and click on “Create Dump File”. It’ll take a little bit, but when finished shows the path it dumped the file. I had to use 7Zip to compress it all down enough to fit within the forums file size limits.
Hope this helps.
@pettcomputers said:
I’ve also had this a few times over the past few weeks as well, only killing the exe from task manager and relaunching Plex works. The requested information is attached as 7z. Thanks.Windows Server 2012R2
Plex Version 1.7.5.4035
PlexPass Channel, if that matters.Thanks!
For some reason can’t see any stack information for Plex threads. Will have to repeat the exercise - last time it only took 27 minutes to bring the problem on.
Server was launched at 23:05:36
Requests started to get stuck and not complete as from 23:30:52
Process Dump taken at 23:32:38
Requests bounced with Error 503 as from 23:42:24
So hopefully you can easily to get it to fail in same way.
This time i want you to use SysInternals Process Explorer instead and to create a full dump
- shutdown and relaunch Plex Media Server
- launch Process Explorer with right click option
Run As Administrator - Within Process Explorer view, Locate the
Plex Media Server.exeprocess and select it
(The option we will to use later is Right Click,Create Dump,Create Full Dump) - Prepare a browser tab for the
http://127.0.0.1:32400/connections?X-Plex-Token=xxxxxxxxxxxxxxrequest - Test once to see syntax is correct
- Do whatever you do to reproduce the deadlock
- When you get the deadlock, get the
/connectionsoutput and save to text file - Create a Full Dump for the Plex Media Server.exe process using Process Explorer
- Get the Plex Media Server log files as before
The diagnostics may now be bigger than what the forum allows - so you may need to upload to Dropbox / google drive etc and send me link by private message
Hopefully we will get a usable complete set of diagnostics - and thank you again for your help
I’ll see what I can do! Thanks for looking at the logs.
i got everything ready to go for the next deadlock. i was on vacation and when it deadlocked i couldn’t check it and get logs just had someone reboot the server to get it up.
@pettcomputers said:
I’ll see what I can do! Thanks for looking at the logs.
Thank for the new full dump produced by process explorer - it looks OK to me and I have passed it to the development team together with the /connections snapshot and logs
I do not understand the initial error you got with process explorer
I am having this same issue now, I have been fortunate to have my phone so I can reboot the server with chrome remote desktop when it happens but I should not have to do that.
If you want to crush it, just put 5 movies on optimize …sooner o plater it will crush.
what is interesting is that ending plex.exe task and relaunching it will not solve the problem, you have to end python tastks and launch plex after that…
yeah you have to kill everything. Ok so mine died last night. i didn’t get the 503, but it was stuck so its hard to tell if it was the same error. i was able to get the token and the logs, but the proc wouldn’t take the dmp for some reason. I restarted everything and restarted proc to see if next crash i get the full thing.
@jorgisimo said:
yeah you have to kill everything. Ok so mine died last night. i didn’t get the 503, but it was stuck so its hard to tell if it was the same error. i was able to get the token and the logs, but the proc wouldn’t take the dmp for some reason. I restarted everything and restarted proc to see if next crash i get the full thing.
same problem and there were 503 errors being generated
Jul 12, 2017 05:28:14.639 [7320] DEBUG - Completed: [192.168.1.87:63976] 503 GET / (1037 live) TLS GZIP 1ms 372 bytes
and dash protocol was being used for transcoding - so looks like it is the problem that has now been identified and is awaiting a fix to be written and tested and released
It is strange the creating dumps is being locked out
