@sa2000 I have been informed tonight that while I was out Plex (Current build 1.23.6.4881) become inaccessible again, however when I got home it seems to have recovered itself, after looking through the Logs I can see the problem starting at 20:40:13.559 with 16 Connections and then starts climbing for the next almost 20 mins (20:58:16.485) to max at 74 connections.
It sat at above 50 connections until just after 21:00 (21:00:40) when it drops down to just 10 connections and has been there since.
I have been told by My kids that they started to watch a film at about 20:00 and it stopped playing and they couldnāt get back on to plex about 45 mins later, which lines up with the times in the log file, when I got home at 23:00 Plex was accessible and seems to work.
So I am betting we are slow getting there but there is still clearly something going on, as in the past and on previous builds it would not recover at all even after a few hours at some points, so recovering after I would say about 30 mins is an improvement, however it is very clearly being triggered by content viewing.
I started trying out Overseer and Iāve since stopped using it since the Full scans initiated from Overseer are causing plex to spike my cpu and cause in many cases Plex to crash. Iāve since found Petio, and somewhat better but the full scan still causes high CPU usage from Plex when it does a full scan as well and shows updating metadata whenever it does. I also noticed that only the full scans causes Plex to āupdate Metadataā the partial or recently added scans are usually quick, Also I donāt see this behaviour with TV shows, perhaps itās something wrong with my movies library, but Iām doubtful since this issue only happens if Overseer runs. Petio seems to not complete the full scan for some reason. Iām running everything though docker and Unraid BTW. Running Version 1.23.6.4881 Plex and latest for Overseer and Petio.
Over the last few months and testing a number of things I have confirmed that the last āGOODā Build for me where this issue never happened was 1.22.0.4145, all builds after have had this connection deadlocking issue at some point, some once others a number of times but each single build since has 100% had this problem, the most recent build has in fact increased the frequency of the problem to the point that I am starting to get anxious by it again!!
The fact that this has been ongoing for 6 months is not only beyond a joke but should not be allowed especially from a company that has recently secured more investment so its not like they donāt have the resource to look into it.
In the last week I have sent in 4 sets of diagnostics out of 6 cases, and have a feeling only one single set will be looked at, which I strongly believe wont actually help much as that will be just a grain of sand on the beach compered to the bucket I have supplied!!
I donāt meant to come across rude, I am just getting to the end of my tether and really donāt want to become ill again due to a stupid peace of software!!
The latest 1.23.6.4881 kept crashing too often for me, so Iāve gone back to 1.23.5.4862 it has been the most stable for me, even compared to 1.22.0.4145.
Yeah 1.22 I only get a memory issue that was actually fixed in later builds, but 1.23.6 is really bad, and TBH I am fed up with having to downgrade all the time cos of this stupid problem.
It could be that the Overseerr behaviour in terms of how many parallel requests it sends is crippling Plex Media Server. Whilst I have referred this to the Plex Media Server development team, I recommend that you do the same for this add-on and ask the Overseerr developers to do some stress testing and reduce the number of parallel requests
I have had it happen again in the last 30 mins, this time I had all external Apps like Petio off and it still happened. So this one tells me that Petio has not been the trigger as I turned it off about 6 hours ago.
My firestick keeps freezing (buffering on a direct local connection)
Seems to happen about every 30 mins or so
No subtitles
not transcoding
I have to exit the video, and restart it, resume from X minsā¦
only one time did it have to start back from the beginning. just fast forwarded to just before where it froze.
PMS Version 1.23.6.4881
Firestick OS 6.2.8.1 (NS6281/3385)
TV Home Version 6322095.1
Plex Client Version 8.20.1.26670
Not sure that is related to this issue, as this is about a Deadlocking issue with the server where the actual server is no longer working.
What your describing sounds more like a firestick issue, good chance its WiFi related or the age of the firestick cos there actually not the best of devices.
If your server is also unresponsive when this happens then Please follow the guide thats I have linked in my OP and get the relevant diagnostic information to @sa2000 so the team can look at it, if the server is fine when this happens then please do create a separate post seeking help for your issue
