Have been having issues in the last few server releases for the DSM7 on Synology. Crashes occur once a day, and require a manual restart to get Plex running again. I have attached a log from the system.log, which I believe could be contributed to the issue with a Python TypeError being thrown in the parsekit. com.plexapp.system.log (36.0 KB)
Just for what its worth: I also have been seeing this. I log in to my DS1817+ and Plex is not running…I have to start it manually. This ONLY began happening on DSM7 with the latest 3-4 server versions downloaded through the Plex site.
It does not crash when actively using Plex (i.e. Its not media related for me)…just randomly within 1-2 days.
I ran Plex for many many years on DSM6 and never had it crash a single time.
Hi, I’m also seeing frequent crashes from Server Version 1.24.0.4930, from DSM 7.0 on a Synology DS218+.
When I go to restart the package, it has reported ‘Stopped Manually’. Though it wasn’t. Here is the last entry caught before I restarted the server just now. Looks like it uploaded a crash dump.
Aug 17, 2021 21:08:42.374 [0x7ffbe4854b38] DEBUG - [Transcode] Session 2djmqlieejkxj6qkrqregroc (3) is unthrottling
Aug 17, 2021 21:08:42.375 [0x7ffbe4bdcb38] DEBUG - [Transcoder] Throttle - Getting back to work.
Aug 17, 2021 21:08:42.783 [0x7ffbe7208b38] DEBUG - Completed: [94.2.152.20:58504] 206 GET /video/:/transcode/universal/session/2djmqlieejkxj6qkrqregroc/base/02447.ts (19 live) TLS 475ms 1197936 bytes (pipelined: 353) (range: bytes=0-)
Aug 17, 2021 21:08:42.783 [0x7ffbe7208b38] DEBUG - Removed transcode data consumer, active count 1 => 0
Aug 17, 2021 21:08:42.802 [0x7ffbe5447b38] DEBUG - [Transcode] Transcoder segment range: 2095 - 2467 (2467)
Aug 17, 2021 21:08:42.803 [0x7ffbe4854b38] DEBUG - [Transcode] Transcoder segment range: 2095 - 2468 (2467)
Aug 17, 2021 21:08:43.170 [0x7ffbe4bdcb38] DEBUG - [Transcode] Transcoder segment range: 0 - 0 (0)
Aug 17, 2021 21:08:43.173 [0x7ffbd6990b38] DEBUG - Content-Length is -1 (of total: -1).
Aug 17, 2021 21:08:43.194 [0x7ffbd6990b38] WARN - Failed to set up two way stream, caught exception: write: Connection reset by peer
Aug 17, 2021 21:08:43.559 [0x7ffbe4fa1b38] DEBUG - [Transcode] Session 2djmqlieejkxj6qkrqregroc (3) is throttling
Aug 17, 2021 21:08:43.560 [0x7ffbe5447b38] DEBUG - [Transcoder] Throttle - Going into sloth mode.
Aug 17, 2021 21:08:43.562 [0x7ffbd6990b38] DEBUG - [JobRunner] Job running: ‘/volume1/@appstore/PlexMediaServer/CrashUploader’ ‘–directory=/var/packages/PlexMediaServer/shares/PlexMediaServer/AppData/Plex Media Server/Crash Reports/1.24.0.4930-ab6e1a058’ ‘–version=1.24.0.4930-ab6e1a058’ ‘–platform=Linux’ ‘–platformVersion=DSM 7.0.41890-0’ ‘–serverUuid=9a71313a4718b4ca0de78c91eea858b2827267ef’ ‘–userId=jason@askpcs.co.uk’ ‘–sentryUrl=https://sentry.io/api/1233455/minidump’ ‘–sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx’ ‘–vendor=Synology’ ‘–model=x86_64’ ‘–device=DS218+’ ‘–allowRetries=0’
Aug 17, 2021 21:08:43.571 [0x7ffbd6990b38] DEBUG - [JobRunner] Jobs: Starting child process with pid 28862
Same for me, says “Stopped manually” (which is not true) but starts right back up when I click run. That happens almost daily. I disabled the port forward rule I had to make sure nothing funky going on outside. Time will tell.
Someone said earlier that just because you didn’t see this happening doesn’t mean it wasn’t happening on DSM 6. My counter-argument to that is who the heck was starting it back up then? Since I’m the only one that has access to it and it went literally for years without having an issue like that. So yes it may have been stopping but what I want to know is what was starting it back up so I can get it to start it back up automatically on dsm7 as well because they didn’t seem to include that feature. Within Microsoft Windows the services have the option to attempt to start on backup after they crash, that would seem to be a good feature to have for dsm7 as well.
PMS randomly stopped overnight, had to manually start it. Now it’s random spinning circles with the “Failed to stream media, client probably disconnected” nonsense in the log. Working one second, not working the next… a lot of this repeated in the logs while this is happening: “We’re going to try to auto-select an audio stream” and “We’re going to try to auto-select a subtitle”
A full restart of the Diskstation forces it to work.
Plex really is a shitshow I’m afraid, it’s just one thing after another with MANY bugs stretching back YEARS without any fixes.
Told my son to play his stuff on Kodi, I can’t be doing without this crap on a Saturday night that’s for sure.
As always, I’m feeling my money has been well spent on Plex…
I tried everything on my side, not a techinal expert so i come for help ;
I’d say since DSM7 or lil after, server crash/shut down everyday on the Nas Syno, its rly annoying, since my whole family uses my plex/plexamp, which is not reliable anymore
Sorry not sure what youre asking ? i gave u all the logs i got already (i have a crash report folder but everything is empty in this one)
BTW, i’d like to point out that i tried to do a fresh install 2 days ago, by making a backup of the PMS folder then desinstall/reinstall.
I couldnt launch PMS anymore, had to copy an old (few days) copy (snapshot replication, thanks Syno) of PMS, which should be the exact same folder of the one i tried to re-use