Ever since Updating to the latest version of Plex Media Server, my Plex server has become largely unstable

[Buddyl33]

Server Version#: 1.15.3.876
Player Version#:

Ever since I updated to this latest version my server has to be restarted near daily as it becomes constantly unresponsive. I have rebooted the entire server 3 times today. It’s getting ridiculous. Is anyone else having this issue and if so how in the hell do you fix it? Prior to this update my server would run for entire months, only rebooting for Windows patching.

I would be happy to provide logs I just don’t know which of the many log files to attach or copy/paste.

Update 1: So the server crashed today at 12:54pm CDT. I am going to provide as much log data as I can.

Tautulli Log:

12:54:32: Failed to access uri endpoint /status/sessions. Is your server maybe accepting SSL connections only? HTTPConnectionPool(host=‘127.0.0.1’, port=32400): Max retries exceeded with url: /status/sessions (Caused by ReadTimeoutError(“HTTPConnectionPool(host=‘127.0.0.1’, port=32400): Read timed out. (read timeout=15)”,))

12:54:32: Tautulli Pmsconnect :: Unable to parse XML for get_current_activity: ‘NoneType’ object has no attribute ‘getElementsByTagName’.

12:54:32: Unable to retrieve data for get_activity.

12:54:32: Failed to access uri endpoint /status/sessions. Is your server maybe accepting SSL connections only? HTTPConnectionPool(host=‘127.0.0.1’, port=32400): Max retries exceeded with url: /status/sessions (Caused by ReadTimeoutError(“HTTPConnectionPool(host=‘127.0.0.1’, port=32400): Read timed out. (read timeout=15)”,))

12:54:32: Tautulli Pmsconnect :: Unable to parse XML for get_current_activity: ‘NoneType’ object has no attribute ‘getElementsByTagName’.

PMS Log

At near the same time of 12:50:49 I get this error: [CompanionPlayer] We already have a handler, overwriting.

That error, or rather, warning, repeats every minute after that.

Windows System Log

12:44:55 - The Volume Shadow Copy service entered the running state.
12:57:23 - The shadow copies of volume P: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied. *note P is the SSD that the Plex DB and transcoding exists on.
12:54:32 - A fatal alert was generated and sent to the remote endpoint. This may result in termination of the connection. The TLS protocol defined fatal error code is 10. The Windows SChannel error state is 1203.

Windows Application Log:

12:47:58 - Volume Shadow Copy Error: VSS spent more than 120 seconds trying to open and flush all the volumes in the shadow- copy set. This caused volume \?\Volume{f030c9dd-be40-4142-8147-9110b678ba7c}\ to timeout waiting for the hold-writes phase of shadow-copy creation. Trying again when disk activity is lower may solve this problem.

Operation:
Executing Asynchronous Operation

Context:
Current State: flush-and-hold writes
Volume Name: \?\Volume{f030c9dd-be40-4142-8147-9110b678ba7c}\

[jkarim]

I feel like the same thing is happening to me. Running plex server on mac, and since the latest update I get stuttering on playback, and I can’t access my preferences…the server disappears, says I don’t have access to “.” server. Also it shows I have two dashboards for the same server, and double the current transcoding sessions.
Reinstalled, checked my drive, still have the issue.

[flaspartan_gmail_com]

Have similar problem. I’m a newbie moving away from Kodi. Have server on Windows 7 PC serving Mac and several Fire Sticks. Server goes down sporadically but has yet to stay up 12 hours.

On a side note, where do I get skin info that’s not PHT?

[Mini_Server_1]

This is a known issue, lots of people reporting several of this type of behavior, hopefully they will release a hotsite fix for this, the cookie issue and the excessive upload bandwidth issue they acknowledged in one of my posts they removed.