Server Version#: 1.14.1.5488
Player Version#: 1.37 (11125)
Since the update to 1.14.1.5488 I am seeing regular crashes where the plex client becomes unresponsive and unable to connect to the server. When I check the plex service in synology os, it is stopped and I have to restart it. This has happened twice in 24 hours.
Anyone else seeing this? Logs attached.
Thanks Trumpy!
Yeah the shared folder has R/W permissions for the plex user and I see the .ts files within their respective show folder in that directory. I did have a failed recording for whatever reason however the other two episodes of that particular show recording without error. I did grab the files as soon as I saw this latest crash (and it appears to have recorded that in the crash log, at least reporting it to plex), but I also could not see anything obvious in the logs.
Hello!
I am new with Synology and Plex (i started to use it last week so i am lost).
I kind of have the same problem.
I have a synology ds918+, i use it every day but after a few hours it stops to run on the Synology OS. Then i have to access the OS and go to the apps and click “Run” every time that i want to use Plex. I do not log out or change the settings.
So the questions is: Do i need to click Run every time that i will use Plex or is it possible to let it always running?
Thank you for your help!
Plex runs as a Service application.
It should run always.
When it stops responding again.
Please start it.
wait 60 seconds for it to stabilize again.
Settings - Server - Troubleshooting - Download Logs
Attach the ZIP file.
Well due to the crashes I was seeing with 1.14.1.5488 I downgraded to Version 1.14.0.5470 and so far no crashes in 48 hours. I also was experiencing slugishness navigating the plex client interface with 5488 (ie; long load times in the settings menu’s which seemed to get gradually worse until the service utimately crashed ) and that has also gone away with 5470.
So if your having issues with 5488 I would certainly try 5470.
Certainly understand where your coming from trumpy81 but I rely on the plex server to serve TV to all my local TV’s and a few remote users, and to have it crash continuously like that was a deal breaker. Perhaps your right and its specific to my setup, after all I had already waded through the plex forums specifically looking for problems with that version and simular issues and could not find any.
You had alluded to the possibility of it potentially being related to livetv, well I am running XteVe (a virtual HDHR tuner, also running in a docker container on the DS918+) which uses a custom XMLTV file, to pipe my IPTV channels in to Plex (SPK 64 bit)… Related? Maybe, However I didn’t experience any issues with that previous version.
Network Connectivity is fine, the DS918+ also serves out various other services which were uneffected it’s connected to a Ubiquiti UniFi Switch 24 POE-250W in an aggregated NIC config which is uplinked to a Ubiquiti EdgeRouter. I had checked the obvious offenders such as HD Hibernation and potentially corrupt media files, all which are known to crash the plex service like that but everything looked clean.
Sure I am game to try the newer builds (hopefully they contain the fix for the very annoying “failed to record livetv” errors when playing a channel which was fixed in 5488. Do I lose anything by installing these newer builds? My focus is on LiveTV.
Appreciate the support 
Hardware: Synology DS918+
Version: 1.15.0.659
Client: 1.38 (11485)
So no issues at all with 1.14.0.5470 since I downgraded to it, but given that the new builds have now been merged with the beta channel, I upgraded the DS918+ to build 1.15.0.659 by installing the 64 bit Plex Pass Beta SPK package from plex.com. It ran for about 4 days but today had a hard crash while I was watching livetv. Again just like 5488 the plex server was stopped and I had to manually restart it. I Immediately grabbed the logs which I have attached, hoping you can see anything which may point towards the cause. Crash reports are enabled.
I also tagged @ChuckPa in this message as he seems to do a lot of work on the NAS builds. I REALLY do not want to have to downgrade again, as this version has fixed a few annoying bugs!
Appreciate all your time guys!
Thanks Trumpy!. No, Plex is running natively on the ds918+, it is pulling its XML guide data from a tuner proxy (Xteve) which is running in a docker container on the NAS. It was happily streaming live TV and then suddenly the plex client on the Apple TV exited back to the home screen, I went back in to the plex client and tried to play the channel again and all of a sudden no plex client could find the server (tried AppleTV, iPhone Plex Web). Checked the plex service in package center and it was stopped. Note this does not happen with version 1.14.0.5470 which was running the same DSM version (6.2.1-23824 Update 4)
Only the NAS itself has a Lets Encrypt Cert.
Server: Version 1.15.3.876
I’m having a similar problem: Plex keeps stopping on my 1019+. It’s happened a few times this week; no seeming rhyme or reason (or pattern that I can see). I did re-start it and tried to grab the logs as quick as I could after it was up - hopefully there’s something in here that shows what’s going on?
I had a similar issue this week on a DS916+. It was related to fs.inotify.max_user_watches (was resetted to 8192).
Adding as “on boot” task this command
sh -c '(sleep 90 && echo 204800 > /proc/sys/fs/inotify/max_user_watches)&'
PMS now works.
Why not update /etc/sysctl.conf and be done with it?
It gets overwritten. /etc/init/s2s_daemon.conf sets fs.inotify.max_user_watches back to 8192 after a reboot. I changed it in that script:
changed env MaxWatches=8192
to env MaxWatches=65536
You can check if this is applicable to you:
admin@SUSHI:~$ sudo synoservice --status s2s_daemon
Service [s2s_daemon] status=[enable]
required upstart job:
[s2s_daemon] is start.
Phil
Thats right. My apologies.
It’s been a long week.
I wanted to close the loop on this: Plex is no longer crashing on me. I crashed once after deleting all the contests of the “caches” folder, but as I’ve removed all VC-1 MKV files and transcoded them to MP4, the crashing has stopped - so it was likely an invalid VC-1 file.
Thanks again for the help trumpy81! You are a treasure in these forums. 
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
