Synology 916+ running Plex 1.11.0.4666. Since upgrading to this version, the Plex process keeps stopping. I can log into the Synology DSM and restart the process, but each day it stops. I have not narrowed down to any particular time or even, as no one has been using it at the time it stops. I find it when I connect to plex client and it defaults to another running service like cloud and the 916 server is red. I also run an older Synology 415+ server with same software build and mirrored content and its Plex process is not stopping. Any suggestions?
Iâve relocated your post to the Synology forum where youâll get better support.
- Can you pull the log files (immediately after it restarts) from Settings - Server - Help - Download Logs and post that ZIP file here?
- You can also download the Public version 1.10.1 and keep it handy as a backup. (1.11.0 is considered beta and might have issues)
Iâm having the same problem with the same general hardware (synology 418play) and software version (1.11.0.4666)
Logs attached.
Iâve downloaded the 1.10.1, but synology wonât let me install it saying downgrading is not permitted. If I uninstall the server, will I lose all the libraries Iâve set up?
Thank you for any guidance!
1 Like
Synology is odd about that.
- Uninstall PMS in App Center
- Reinstall whichever version you wish.
Your data is held safe because itâs stored in a different location. The installer locates and links to your library as part of installation
Thanks ChuckPA. Iâve installed the previous version and the server is back up and running with my libraries intact. I will report back if any further issues arise.
Thank you for this post. Same thing happened to me. PMS 1.11.0.4666 would crash after playing any video for about 10 seconds. I would restart it on the Synology DS916+ running DSM 6.1.4, but it would crash again after playing any video for about 10 seconds. I couldnât figure out how to safely downgrade PMS until I read this post. PMS 1.10.1.4602 is installed now and seems to be running fine again.
Ok, so after posting this issue Plex did not fail for days, then failed once while I was unable to collect logs remotely, and has just failed now, so much less often than previously. Here we go I attach the log file. I realize it is effectively beta, thatâs part of running beta to identify issues to resolve before GA, so I am happy at this point to stay on beta, in case you need more logs. Thank you for you assistance.
Thank you. I passed it on to the team member whoâs focused on finding that problem
Iâll report back here when I have an update
##To all reading here. Especially @dpryke and @bolderplex
Iâve been working with the team and have feedback.
There is a fix coming. Until it is released to public, limit what you have done in Scheduled Tasks.
Until i have the definitive list.
a) Turn off deep analysis and other automated analysis
b) Turn off database optimizations. (Perform this manually after adding media)
Thank you @ChuckPA I look forward to the update. FYI I just had another hang, this time when I restarted the service, even though Synology shows the process running PMS would not respond on 32400. I had to manually stop the process and restart for it to respond. I have dumped the logs if this would help. If you already have the solution, no problem. but just in case, Iâll load them here. If your looking for time stamp, I restarted and no response around 5:17pm on 2018-01-17 Thanks for all you do, this is an awesome product.
Thanks.
As I understand it.
Also turn off ABR (Automatic Bit Rate) in Plex/web. ABR is dependent on Deep Analysis (which is now turned off)
a) Turn off deep analysis and other automated analysis
b) Turn off database optimizations. (Perform this manually after adding media)
What a great community. It has been doing the same for me as well.
I have a DS415+ and it has been rock solid for years except for the last month. Every once in a while I cannot connect to Plex so I look at the NAS and, low and behold, the Plex server is not running. I will restart it fine but in an indeterminate number of days it will fail again. I will deselect those tasks as noted above for now.
I did capture logs (regular and not verbose) of the most recent time yesterday. Do you want those or are you good with this already?
Is this related to not being able to use Plex web (TV apps seem fine) i.e. Home, TV, Movies screens wouldnât load? It seems to happen any time I am doing any work in Plex like adding something. It says:
âThere was an unexpected error loading this library
Please visit our forums if you continue to experience problemsâ
Also I deselected a few boxes in âTasksâ and clicked save - it said it could not be saved although the boxes stayed blank. The processes may be running at the moment does that mater? I went back and selected them>then saved>then deselected them again>then saved and it said saved each time (just to be sure). I deselected these:
- Optimize database every week
- Refresh local metadata every three days
- Upgrade media analysis during maintenance
- Update all libraries during maintenance
- Refresh metadata periodically
- Perform extensive media analysis during maintenance
did I miss any?
@trumpy81 said:
The most common cause of Plex stopping as you described, is damaged media files. See Q17 and Q28 on the Synology FAQâs page, link in my signature.The settings you mentioned can be restored/enabled if you are using Plex version 1.10.1.
I donât suppose there is a Mac version is there? 
I am on 1.11.0.4666. Does that matter?
Also noticed it is not just web interface but my Xbox1 also that wonât load home page. I guess I donât often watch while adding.
FYI (for others too)- NAS 8%CPU and 40%RAM - doesnât seem like it is pinning anything.
Sorry - web interface in browser: https://app.plex.tv/desktop#
I borrowed a PC work laptop - will try the videocheck
Synology says Plex running, and it loads basic setup/frames/words on left/links to settings at top in browser but not the âmedia material/cover artâ in the middle area. It will show same âUnable to Load selected libraryâ error if I click the âMoviesâ or other libraries on the left. As similar error shows on other apps etc. not just web interface.
I found if I stop the service/app on the NAS, then start it again (takes a few minutes) it will run OK until I have to add more media.
@trumpy81 said:
Thanks for that. What you describe sounds like a database issue.Try one of these procedures:
Repair Database: https://support.plex.tv/hc/en-us/articles/201100678-Repair-a-Corrupt-Database
Restore Database: https://support.plex.tv/hc/en-us/articles/202485658-Restore-a-Database-Backed-Up-via-Scheduled-Tasks-Also, you should perform these tasks whenever you add/remove a lot of media (wait until Plex has completely finished itâs tasks before you run these though):
- Optimise Database
- Empty Trash
- Clean Bundles
From the first link instructions, would my installation be Linux? (Synology NAS 415+)
Also, does that .bat file look in subdirectories?
Thank You - I will try and find a quiet time to shut it down and do this.
Question - Videocheck Error log - I have a couple so far but there is no information about the error in the log. They just list the item. I didnât change anything but the path and file type. Is the ending supposed to look funny with a bracket ) on the next line etc.?
FOR /r âH:\Convert Videoâ %%I in (*.avi) DO (
Echo %%I >>error.log
ffmpeg.exe -v error -i â%%~fIâ -f null - >>error.log 2>&1
)
I would think the shell bash or (csh on Unix) should do just fine IIRC my Unix corectly.
Recursion requires two scripts or 1 script and 1 command
the script
#!/bin/sh
# Run ffmpeg, through the output to a dummy file, capture the error code
ffmpeg -i "$1" --- other options here > /tmp/dummy.put_extension_here
if [ $? -eq 0 ]; then
# file is ok
else
# file failed
fi
invoke with
find /top/media/dir -name \*.avi -print -exec /path/to/script {} \;
The {} passes the name of the found file to the script
Checked database - it said it was OK, ran repair steps anyway (not the restore ones).
Thanks. I like this, it feel âcleanâ 
Still scanning videos, so far 3 with errors/many hundreds. All added years ago but had no problems of Plex shut-down before.
Is there a good way/site to simply and âfixâ them. Not hyper concerned about a bit of quality lossâŠRun them through handbrake or something? :*
Many hits of the same thing:
[null @ 000001a521a58000] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 4229 >= 4229
-or-
Error while decoding stream #0:0: Invalid data found when processing input
[h264 @ 000002686cdb4940] Invalid NAL unit size (1613907857 > 5640).
[h264 @ 000002686cdb4940] Error splitting the input into NAL units.
[ac3 @ 000002686c9869c0] exponent 25 is out-of-range
[ac3 @ 000002686c9869c0] error decoding the audio block
[ac3 @ 000002686c9869c0] frame sync error
Ed,
Thanks for that info. You unfortunately have some very damaged media files. AVI files were terrible for that.
As a very first step, I would like to suggest getting them out of the AVI container. This is a Remux step, not an Encode step
Same find/script structure except the script is new:
#!/bin/sh
dir="`dirname "$1"`"
newname="`basename -s avi "$1"`mkv"
ffmpeg -i "$1" -c copy "$dir/$newname"
# Add conditional test to see if container change successful
if [ $? -eq 1 ]; then
# could not convert
rm -f "$dir/$newname"
else
echo Converted "$1" correctly
rm -f "$1"
fi
Please do verify this is what you want. It will delete the output file (if container change unsuccessful) but also delete the input file if it was successful!
Cool. I am getting that freshly formatted HDD feeling.
When the scanning is done I will copy all of them into a separate folder and fix from there. I looked and they are all .m4v (from handbrake many years ago).
Does that change any techniques?
