Server Version#: 1.32.7639
Player Version#: 4.116.1
I’ve been running PMS reliably on my Synology DS1621+ for a couple years now. I updated to v1.32.8.7639 four days ago and now I consistently see a status in Synology DSM of “Manually stopped” for PMS a few hours after PMS startup and I cannot connect to PMS from any client. During the window where PMS is running, it seems to operate normally.
I tried reverting back to the previous version of PMS (1.32.7.7621), but I get an error saying that I’m unable to roll back to the previous version.
I’m not familiar with the log formats/content for PMS, so I’m not sure exactly where to look for why PMS is crashing. I do see in the “Crash Uploader” log that there are crashdumps being uploaded to https://o17675.ingest.sentry.io
Where should I look to figure out what’s causing the crash?
Pull the server log files (Settings → Troubleshooting). Unzip. Look in Plex Media Server.log (and .1.log to .5.log) for ERROR entries that mention the database is malformed or corrupt.
If the problem lies elsewhere, then upload the ZIP with the logs and someone can take a look.
Regarding reverting to a previous release, Synology does not permit direct downgrades. Uninstall Plex Media Server, selecting the “Uninstall Only” option. Then install the desired version. Initial startup may take longer due to database adjustments between releases. If you see a “503 server maintenance” message when trying to login to the server, wait a few minutes and try again.
Thanks for the link to the other thread. My goggle-fu apparently failed me when searching for similar issues. The other thread is very helpful - seems like mine may have the same root cause. I also use the DVR/LiveTV functionality.
I tried the “Optimize Database” option on the Troubleshooting menu this morning, AFTER downloading a copy of the logs AND the database, of course. So far, it’s been up all day.
I’ll look at some of the older logs to see if there are indications of a database error.
Worst case, I have the previous version saved and can uninstall/reinstall if necessary - glad to know that’s an option.
[documenting for others who might find this thread…]
I looked through all my logs and I found no references to the words malformed or corrupt in any error lines that contained the word error. The only mentions of database were:
ERROR - Waited over 10 seconds for a busy database; giving up.
ERROR - Waited over 10 seconds for a busy database; giving up.
ERROR - Failed to begin transaction (/data/jenkins/server/xxxxxxxxxxx/MediaProviders/MediaSubscriptionDesiredSetManager.cpp:105) (tries=1): Cannot begin
transaction. database is locked
FWIW, I tried the “Optimize Database” option from the troubleshooting menu and PMS then ran for 4 days before crashing again.
Since it’s crashing again and the symptoms look like the signature from New update 1.32.8.7639 crashing randomly on synology nas, I’m just going to revert to the previously-working verion (1.32.7.7621) and await a fix for #14691(as mentioned in that thread) before updating to a newer version.
