Synology Diskstation 918+, had no problems on DSM 6 with Plex. Native plex synology package. Every few days I’ll find that the plex package has just stopped.
Server Version#: 1.23.6.4881
Unfortunately, I have no logs, I enable them in plex and I can see the logs happening, but then once the issue occurs and I find Plex off, then start it again from the package manager and go back to the debug logs section then it has been disabled and there are no logs.
Ahhh ok, reassuring that the issue is known, a little disappointing that DSM7 beta was around for a long time and it’s happening still. Would moving to docker make any difference?
I’ll try seeing if there’s anything in the logs for bad files, thanks. I’ve got… a lot of media though, so I hope it’s not that, hah.
So far so good, found errors relating to permission issues with one of my DSM volume shares, fixed those as well as removed a few video/music files that were throwing errors and it hasn’t shut down once yet and it’s been over 2 weeks.
Lol, spoke too soon, it just shut down yesterday. Nothing else really popping up in the logs so I guess I’m just stuck with this and hope that Plex fixes it. Neat.
I am seeing the same issues with each update. Plex will just stop. I am also noticing that while Plex is running the CPU is at 99% even if no users are logged in or media is playing.
Same issue here , Plex shut down without reason since i installed Plex v1.24.2.4973 on DSM7 a few weeks ago.
On a separate note DSM7 issued an error that I had run out of memory on a service and advised to send create and send logs to Synology tech support which I have now done. Maybe its related?
Anyone have any news updates on this long lasting issue?
@ChuckPa I’ve made that tweak to my Preferences.xml a few days ago and then it just happened, turned it back on and downloaded the logs/database, how do I get these to you? I tried sending a PM and it said you’re not receiving messages at this moment.
Does anyone know how to fix this? It’s getting pretty annoying? I believe it stops the service when there is an update detected. That’s the only thing I can see as a cause.