Server Version#: 1.22.2.4282
Player Version#:
I’ve seen posts about this issue but no resolution. I updated Plex with 1.22.2.4282 on a Synology NAS 4 or 5 days ago. It crashes ALL the time. Sometimes it stays up for a couple of hours but most of the time it crashes in 10-15 minutes.
Is there a way to fix it? If not, when is a patch available? I can’t watch my media. Plex is supposed to be the best. I’m not feeling it.
Don’t think it is a version issue as last time this issue occurred on my server I upgraded the version and it has come back. Last time I upgraded the version. Cleared cache, and revered database back from a backup.
Debug logging is enabled and logs are provided in my post.
@trumpy81 my bad plex forms refresh took me back to this post, was thinking you were replying to my issue.
I thought the issue was resolved but it crashed agsin immediately after I posted it was running for 24 hours. I’ve attached the zip file you requested.
Plex Media Server Logs_2021-04-21_12-19-30.zip (7.2 MB)
Trying upload again.
I don’t have any network issues. When I look at the DSM control panel, Plex says “Stopped”. I’ll see if something’s going there, but the only thing that has changed was updating to the 1.22.2.4282 release. No changes to the network have been made.
Did not realize verbose was active. Here’s a new zip.
I have 2 identical DS815+ devices, both configured the same and both are running Plex Media Server. Only 1 of them is having an issue. Both were updated to 1.22.2.4282 at the same time.
I got my models incorrect. They are both DS1817+
Because I updated both Media servers on the same day. Both setups are identical. Only one of them is having a problem. If it’s not a crash and nothing at all to do with Plex, I don’t see another explanation.
When you work support, you have to ask “What changed?”. In this case it was Plex and Plex alone that changed.
I’m done.
In case you didn’t already try that:
Try to reinstall Plex Server following the steps from here: Synology FAQ (DSM 5 & 6) - Questions, Answers, and a few How-To's - #14 by ChuckPa
Looks like not properly uninstalling beforehand caused some crash issues with the latest updates, uninstalling helped one user here, I also followed his advice and had no crashes since.
My Plex server on Synology crashes also. For me, it seems to happen whenever there is a server update. Though, after the most recent update, it crashed again (today) with no associated update. Within DSM the Plex service is shown as “Stopped” - DSM also shows that the NAS is “Healthy.” Should I open another thread here in the Plex community?
Plex Media Server Logs_2021-05-19_16-31-20.zip (3.3 MB)
I’ve attached the logs.
Don’t know what this is but it’s sending such a bad stream of replies that it’s knocking the HTTP server offline (going into retry state). The HTTP server will retry after 10 minutes (600 seconds)
The message is received ok (the 200), but can’t parse it whatsoever
May 19, 2021 09:44:08.452 [0x7f1a5ce3e700] DEBUG - HTTP simulating 408 after curl timeout
May 19, 2021 09:44:08.472 [0x7f1a5ce3e700] DEBUG - MyPlex: mapping state set to 'Mapped - Not Published'.
May 19, 2021 09:44:08.474 [0x7f1a5ce3e700] DEBUG - MyPlex: Last published value didn't change, we're done.
May 19, 2021 09:49:58.165 [0x7f1a5eec7700] DEBUG - EventSource: Resolving cc.tv.saab.lol port 32400
May 19, 2021 09:49:58.205 [0x7f1a5f1b5700] DEBUG - EventSource: Resolved cc.tv.saab.lol to 50.220.171.30
May 19, 2021 09:49:58.406 [0x7f1a5eec7700] DEBUG - EventSource: Connected in 110 ms.
May 19, 2021 09:49:58.406 [0x7f1a5eec7700] DEBUG - EventSource: Wrote data, reading reply.
May 19, 2021 09:49:58.580 [0x7f1a5f1b5700] DEBUG - EventSource: Read HTTP reply header.
May 19, 2021 09:49:58.580 [0x7f1a5f1b5700] DEBUG - EventSource: Failure in ParseHeader: HTTP/1.0 200 OK
Cache-Control: no-cache
Content-Type: text/event-stream
Date: Wed, 19 May 2021 13:49:58 GMT
X-Plex-Protocol: 1.0
(0 - Success).
May 19, 2021 09:49:58.580 [0x7f1a5f1b5700] ERROR - EventSource: Retrying in 600 seconds.
May 19, 2021 09:59:58.580 [0x7f1a5eec7700] DEBUG - EventSource: Resolving cc.tv.saab.lol port 32400
May 19, 2021 09:59:58.635 [0x7f1a5f1b5700] DEBUG - EventSource: Resolved cc.tv.saab.lol to 50.220.171.30
May 19, 2021 09:59:58.848 [0x7f1a5eec7700] DEBUG - EventSource: Connected in 119 ms.
May 19, 2021 09:59:58.848 [0x7f1a5eec7700] DEBUG - EventSource: Wrote data, reading reply.
May 19, 2021 09:59:59.035 [0x7f1a5f1b5700] DEBUG - EventSource: Read HTTP reply header.
May 19, 2021 09:59:59.035 [0x7f1a5f1b5700] DEBUG - EventSource: Failure in ParseHeader: HTTP/1.0 200 OK
Thanks for the LIGHTNING fast response!!!
So, in addition to my server, I access a friend’s server - his last name is Saab, so I assume this is related to that? And, for the past few days, his server has been down… would that create these log entries? Anything I can do to troubleshoot?
Oh, and should I open a new thread for this, or are we cool staying here?
If his server is down, it wouldn’t be sending bad replies.
A normal ‘server down’ is a no-reply situation. This is a bad-reply situation.
If he has a proxy in front of PMS, please ask him to turn it off until he gets the server back up. He’s sending junk replies which cannot be parsed.
Ok. His server is back-up. When the server crashes again, I’ll capture the logs and open another thread. I can also send the crash dump, if that helps.
Again, thanks for your support.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
