Ever since I updated to 2857, I am noticing the Server becomes unavailable at some point in the day. The actual physical computer stays on (Windows 10), and the PMS application stays open. When opening the server locally, it says there is an error and can’t connect.
Right clicking on the PMS icon, Exiting, and then reloading the application fixes for temporary, until it happens the next day.
Is anyone else seeing this?
Logfiles please?
@ChuckPa said:
Logfiles please?
Sure, thanks. See attached zip.
Having the exact same issue
@ChuckPa Were my log files helpful at all? Is there anything else I can provide to help?
It hasn’t happened since I posted this on 10/7, but it has happened 2 times before I mentioned it.
Still going through them. I took some personal time yesterday for myself (been a while) and hung out with friends like normal people 
@ChuckPa said:
Still going through them. I took some personal time yesterday for myself (been a while) and hung out with friends like normal people
Haha good! Everyone needs personal time. Appreciate everything!
I am seeing this:
Oct 07, 2016 07:08:09.469 [0824] ERROR - Metadata /system/agents/media/get request failed with code: 404: http://127.0.0.1:52381/system/agents/media/get?guid=com.plexapp.agents.imdb%3A%2F%2Ftt3416828%3Flang%3Den&mediaType=1&url=metadata%3A%2F%2Fposters%2Fcom.plexapp.agents.localmedia_dc2eb0d342dfe75db72418ab8a745c49ede9920e
along with a number of network up/down events.
Http 404 is a ‘not found’ error implying your Plex Library (presumably not on drive C:) is flaking out / not there / sleeping and not waking up in time.
Can you shed some light on this for me ? I’m a Linux guy, not a windows guy, but most Plex issues like this still have the same root cause.
@ChuckPa said:
I am seeing this:Oct 07, 2016 07:08:09.469 [0824] ERROR - Metadata /system/agents/media/get request failed with code: 404: http://127.0.0.1:52381/system/agents/media/get?guid=com.plexapp.agents.imdb%3A%2F%2Ftt3416828%3Flang%3Den&mediaType=1&url=metadata%3A%2F%2Fposters%2Fcom.plexapp.agents.localmedia_dc2eb0d342dfe75db72418ab8a745c49ede9920e
along with a number of network up/down events.
Http 404 is a ‘not found’ error implying your Plex Library (presumably not on drive C:) is flaking out / not there / sleeping and not waking up in time.
Can you shed some light on this for me ? I’m a Linux guy, not a windows guy, but most Plex issues like this still have the same root cause.
Hmmm … my setup is as follows: I have a Windows 10 (x64) machine running an i7-4790K processor with 16GB of ram. I basically just use that machine to run the PMS. I have my storage on a Synology. I have the drives mapped to the Windows 10 machine and the PMS sees the library like that.
When the library isn’t available (drives not mapped yet upon startup, or Synology is off), it would still open up the Plex “page” locally, but will say can’t find media (or something like that).
The few times this “crashing” issue has occurred, it says “Page not found” and I can’t even see the Plex Interface at all.
Hope this is what you were looking for.
I’ve also started getting crashes … on QNAP NAS …
Mine is crashing as well. Twice in 12 hours. 
Airborne over Siberia, but will look into this further later.
Mac → Synology → PMS 1.2.2.2857
This exact thing was happening to me 3-4 times a day. Becomes unresponsive. Doesnt actually crash with an error and it is still running. But I have to kill it and start it back up.
So far a temp fix that seems to have made it more stable for me is to disable DLNA. But I hope Plex sees this issue and fixes it.
Just putting in my 2c.
I noticed connectivity issues with the current version of PMS as well. I rolled back to the non Plex Pass version 1.1.4.2757 and the connectivity issues stopped. I’ve not had the time to troubleshoot yet, as the PMS is constantly in use by the family, but the next time it’s free, I’ll take a closer look.
I am having the same crash as well with the latest Windows version. I have looked through the logs and it doesn’t show anything for it to be crashing. There also is nothing in the crash dumps folder.
I have debugging and verbose turned on and the only errors I even see in the logs don’t look like something that should be causing it to crash and it doesn’t as it is still running after these occur in the log files.
ERROR - Caught exception trying to stream file: C:\Users\Administrator\AppData\Local\Plex Media Server\Cache\PhotoTranscoder\46\46bbc6be29ff2ade123508eb4a96a8ea55ce8f38.jpg: write: protocol is shutdown
Surely that doesn’t have anything to do with it. There isn’t anything else helpful in the logs as far as I can tell unless they are not marked as errors.
@ChuckPa said:
I am seeing this:Oct 07, 2016 07:08:09.469 [0824] ERROR - Metadata /system/agents/media/get request failed with code: 404: http://127.0.0.1:52381/system/agents/media/get?guid=com.plexapp.agents.imdb%3A%2F%2Ftt3416828%3Flang%3Den&mediaType=1&url=metadata%3A%2F%2Fposters%2Fcom.plexapp.agents.localmedia_dc2eb0d342dfe75db72418ab8a745c49ede9920e
along with a number of network up/down events.
Http 404 is a ‘not found’ error implying your Plex Library (presumably not on drive C:) is flaking out / not there / sleeping and not waking up in time.
Can you shed some light on this for me ? I’m a Linux guy, not a windows guy, but most Plex issues like this still have the same root cause.
Hey, it just happened again (first time in over a week). I have a time if that helps as well. Would more logs help?
Yes. The agent logs (all) in addition to the PMS logs.
So I posted earlier that I made it more stable by disabling DLNA. But in the end I had to revert to the previous nonPlex Pass version because Samsung TVs just didnt work right (got kicked off or buffered). I suspect this would also be the case on the smart TVs. I think that problem is that the clients just dont play nice with the new server options.
That’s a pretty general statement and not been general observation so far but it works just fine with my Samsung (2015 model) as I’m sure it does others.
We need to see if we can tighten down a control case (fixed, known bitrate & format media, etc) and make this so we can repeat it. Once repeatable, the rest will be trivial.
How can we start whittling this down into a sharper point?
It’s happened to me a few times now with 1.2.2.2857. Just happened again right now cutting off two streams of the same show (one local and one remote).
Here’s the end of my log when it becomes unresponsive:
pastebin.com/zjYH9eEv
Windows Server 2016 Datacenter
This is on a brand new install last night. Was happening before on Windows Server Technical Preview 4 just the same though ever since I updated to 1.2.x.
Mac Mini -> OSX Sierra -> PMS Version 1.2.0.2838 . . . (DVR Beta)
Just became non-responsive again. .
Attached logfile.
