Hi there,
I’ve have been having issues since March 16th when I installed the above version.
Essentially PMS becomes unavailable after around 10 hours following a computer restart. Despite the unavailability PMS is still running and I am actually unable to force kill it. This has also led to the OS refusing to shut down cleanly.
I have enabled logging Dropbox - File Deleted
Please help! 
@foz1977 said:
Hi there,I’ve have been having issues since March 16th when I installed the above version.
Essentially PMS becomes unavailable after around 10 hours following a computer restart. Despite the unavailability PMS is still running and I am actually unable to force kill it. This has also led to the OS refusing to shut down cleanly.
I have enabled logging Dropbox - File Deleted - Simplify your life
Please help!
Looks like a deadlock leading to requests being queued up and after a while bounced with error 503 once we have more than 1000 queued
The 503’s started at 20:59:58
Before going into the advice on what diagnostics would be needed for a deadlock, I would like first to establish if the P Drive is a network drive or local drive. Having the app data on a network drive would not be supported and is known to give rise to issues and potential database corruptions
If it is a local drive, then lets get some diagnostics for this deadlock. See the steps outlined in my post here under Diagnostics for a deadlock / lockout (Windows
http://forums.plex.tv/discussion/comment/1610084/#Comment_1610084
And when providing logs, please zip all log files and not just the ones you attached here
P drive is a dedicated SSD. I shall check out your post now and got ya on the logs.
503’s hadn’t yet started but internal web access was just stuck waiting and externally was showing offline.
Everything requested is in this one file (extra folder added in zip file).
@foz1977 said:
503’s hadn’t yet started but internal web access was just stuck waiting and externally was showing offline.Everything requested is in this one file (extra folder added in zip file).
Thanks - removed your link as links to dumps ought to be sent by private messsage
Not reached 503’s yet but unavailable again. (I assume needs to reach 1000), queue is at 794.
Also is it normal for that queue to reset? It went down sub 100 and is working it’s way back up again
Waited for the 503 error this time. New set of logs will be PM’d
@foz1977 said:
Also is it normal for that queue to reset? It went down sub 100 and is working it’s way back up again
Depends what happens to the thread that was causing the deadlock. Normally they do not get cleared up without a restart of the server.
Interestingly the server had not restarted at the point that I noticed that
I recently finished watching something (home network), just tried to browse to something else but am unable to.
Have been monitoring connections all morning, hardly above 35 but is now climbing up over 100.
Is it to early to create a dump or should I wait until I get the 503 error?
No need to wait for the 503 - still procesing the original evidence
ok thank you
@sa2000 I think I might have something similar. Could you check crashreports coming from me? Should be a few the last hours… (Infuse beta testing could be the issue)
@DuffHQ said:
@sa2000 I think I might have something similar. Could you check crashreports coming from me? Should be a few the last hours… (Infuse beta testing could be the issue)
I am not following this. This topic is about a hang and not about crashes and crash reporting. Any dumps for this issue are being manually trigged by forcing a process dump
If you have a problem please raise a forum topic and to start with provide the zipped logs (assuming you have debug logging enabled) and description of problem and when it arose
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
@foz1977 said:
I recently finished watching something (home network), just tried to browse to something else but am unable to.Have been monitoring connections all morning, hardly above 35 but is now climbing up over 100.
Is it to early to create a dump or should I wait until I get the 503 error?
one issue has been identified from one of the two dumps provided. For the other, would need more examples. A couple of process dumps captured with the other diagnostics a few seconds apart
Will provide these at the next possible opportunity
Still waiting for the above opportunity
Same issue’s
