I’ve recently installed a Plex server on a Windows Server 2012, it runs very well for a few hours but then seems to stop - although the processes are still running - the server is reported as “unavailable” from a web app, player running on the server, player running on a computer on the same network (wifi) or a smart TV on the same network (wifi).
It come back to life if I restart the hardware - but that doesn’t seem to fix it for long. I’ve attached the log files - any thoughts?
There are also some messages in the server log files that seem to indicate that something called the SSDP hasn’t come back for about three hours - but the server stopped responding days ago …
Nov 07, 2018 10:09:57.651 [10760] DEBUG - NetworkServiceBrowser: Parsing SSDP schema for http://192.168.1.17:50000/
Nov 07, 2018 10:09:57.651 [10760] DEBUG - HTTP requesting GET http://192.168.1.17:50000/
Nov 07, 2018 10:09:59.663 [10760] DEBUG - HTTP 200 response from GET http://192.168.1.17:50000/
Nov 07, 2018 10:09:59.664 [10760] DEBUG - NetworkServiceBrowser: found 1 SSDP devices via http://192.168.1.17:50000/
Nov 07, 2018 10:09:59.664 [10760] DEBUG - NetworkServiceBrowser: SSDP arrived: 192.168.1.17 (AMID05099E193A4)
Nov 07, 2018 10:10:04.639 [7132] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 10755.054327 seconds: 192.168.1.17 (AMID05099E193A4)
Nov 07, 2018 10:10:04.640 [7132] DEBUG - NetworkServiceBrowser: SSDP departed after not being seen for 365876.221156 seconds: 192.168.1.17 (AMID05099E193A4)
I’ve installed the latest beta version of the Plex Media Server and it seems to behave in the same way, - works fine (a little slow, but maybe it’s updating the library) - but by the next morning (10 hours later) it is, once again, unavailable.
I’ve attached the latest logs (manually gathered as I can’t access the server settings page to use the download feature).
The last request that got processed was at 04:52 - but it does not look like a deadlock but simply tcp ip requests stopped coming in which makes me think of the windows mswsock issue that was present in windows server 2012 and was fixed in windows server 2012 r2
I do see the version number showing as Windows version: 6.2 (Build 9200) which is not the R2 release. There were extensive investigations into this tcp ip windows bug years ago. Please update to the R2 release and then we can see if there is any residual issues
I think the bug was to do with the Anywhere built in vpn functionality in windows server 2012. Can’t remember the exact name. I can if you wish search for the old forum topics on this - but it is a nasty bug that causes tcp to stop working