I was running an older version of Plex on my DS214 Play and it worked fine. Foolishly I listened to the upgrade reminders that kept coming from Plex and the note that I need to install manually along with a download URL. So I downloaded the package suggested (it appears to be from Plex) and installed manually. It started up and stopped and would not run.
I uninstalled (did not do full uninstall of all files) and then tried to reinstall the latest version of Plex from the Synology Package Center. (1.29.2.6364.7000) Same problem no matter what I do. I have to manually start after startup and then it stops almost immediately. It’s not a permissions issue as I’ve followed the instructions but didn’t have to change anything as they were set properly. Right after it appears to start to run, I went to the URL to open and saw a message: “” Shortly after, status is “Manually Stopped” - which I didn’t.
I see others have this issue too and I’m wondering if anyone else has encountered these issues.
Thanks for the quick response. The synology log is useless (which says that the system successfully started and stopped the service.) This is from the Plex Crash Uploader log:
Thank you - but perhaps you can help me out as I thought it was what I was following. The yellow link says to look here if the server isn’t running (which it isn’t/can’t).
/volume1/PlexMediaServer/AppData/Plex Media Server
There are five log files produced today and I pasted the contents, which are virtually all identical and that’s it so I thought I’d save all the time of unzipping. There is another directory too - PMS Plugin Logs. That’s not in the instructions. I’ve attached that. If there is anything else, I don’t see it.
Please don’t. Odds are there is information in the logs you are not seeing.
Just because you pull logs from today, doesnt mean that the information we need is going to be there. The error may have happened a couple of days ago. Or what you think is the same info isnt. Trying to cherry pick logs is a waste of everyone’s time.
What version of plex were you running?
What version of DSM are you running?
And yes, Plax is the problem. The one not seen may be a prior name. And there is also a separate Windows machine running a server that pulls files from the same Synology NAS and is working fine.
Sep 21, 2024 15:11:35.186 [0xb6855e6c] ERROR - SQLITE3:0xb77de08c, 1, near ">>": syntax error in "UPDATE metadata_item_setting_markers SET extra_data = extra_data ->> 'url' WHERE extra_data IS NOT NULL and json_valid(extra_data)"
Sep 21, 2024 15:11:35.186 [0xb6855e6c] ERROR - Exception inside transaction (inside=1) (/data/jenkins/server/2976190526/Library/DatabaseMigrations.cpp:289): sqlite3_statement_backend::prepare: near ">>": syntax error for SQL: UPDATE metadata_item_setting_markers SET extra_data = extra_data ->> 'url' WHERE extra_data IS NOT NULL and json_valid(extra_data)
Sep 21, 2024 15:11:35.199 [0xb6855e6c] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::prepare: near ">>": syntax error for SQL: UPDATE metadata_item_setting_markers SET extra_data = extra_data ->> 'url' WHERE extra_data IS NOT NULL and json_valid(extra_data)
Sep 21, 2024 15:11:35.356 [0xb6855e6c] DEBUG - ChangestampAllocator: initialized to 1110441
@ChuckPa Do you have the fix for this book marked?
EDIT: @hinky you cannot down grade from 1.40+ to 1.29 because of database changes.
@ChuckPa - Wow, talk about incredible support… thank you!!! Much impressed and appreciated. Seriously.
That said, to save everyone time and effort, I had a simpler solution since I didn’t have a backup of the old database and I needed to do some housekeeping anyway. I did some research and uninstalled Plex on the NAS and then deleted the Plex Media Server directory on the NAS. I reinstalled, reconnected and will start again with a totally fresh install. I’m going to rebuild the library today on the NAS, which hopefully will also sync up to the numbers I have on the Windows server as they are always off by a count of 2 for some reason.
Anyway, many thanks for the offer and attention. I’ve learned something today and thankfully it wasn’t too much of an inconvenience or a problem in the end.
Thanks - I’ll put up a separate thread on this oddity which occurs when both the Synology Linux version and Windows version use the same dataset on the NAS. Even sorting provides different numbers on the same device. More later and thank you again.
I’m having the same issue where I cannot get my server to continue running. I can send you my info for help if possible. That would be greatly appreciated as I have a very large library
I tried to get it to run to make sure debug logging is enabled but it won’t stay running and the server says “unreachable” on plex windows on my PC
Or you can try my tool. (which will do more for you but still rquire you have “putty” / SSH access to the Syno.
My tool automates most of what the Plex documentation shows and then has extra capabilities (e.g. selecting one of multiple backups if needed automatically)
Please read my README.md and the Synology example here
The choice is yours
My tool usually can fix this with a simple “Auto” repair step (see the documentation)
Sep 27, 2024 21:54:11.936 [139749382015632] DEBUG - Captured session 19.
Sep 27, 2024 21:54:11.940 [139749382015632] ERROR - SQLITE3:0x80000001, 779, index corruption at line 94622 of [a29f994989]
Sep 27, 2024 21:54:11.940 [139749382015632] ERROR - SQLITE3:0x80000001, 779, statement aborts at 41: [update statistics_bandwidth set at = iif(typeof(at) in ('integer', 'real'), at, strftime('%s', at, 'utc'))] database disk image is malformed
Sep 27, 2024 21:54:11.940 [139749382015632] ERROR - Exception inside transaction (inside=1) (/home/runner/actions-runner/_work/plex-media-server/plex-media-server/Library/DatabaseMigrations.cpp:342): sqlite3_statement_backend::loadOne: database disk image is malformed
Sep 27, 2024 21:54:11.944 [139749382015632] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::loadOne: database disk image is malformed
Sep 27, 2024 21:54:11.944 [139749382015632] ERROR - Database corruption: sqlite3_statement_backend::loadOne: database disk image is malformed
Sep 27, 2024 21:54:11.944 [139749382015632] ERROR - Error: Unable to set up server: sqlite3_statement_backend::loadOne: database disk image is malformed (N4soci10soci_errorE)
Sep 27, 2024 21:54:11.944 [139749382015632] DEBUG - [JobRunner] Job running: /volume1/@appstore/PlexMediaServer/CrashUploader --sessionStatus=abnorm
Thank you for your help. I’m a very novice individual when working with servers/synology so whichever will be easiest for a server dummy would be best. Should I still backup the server folder even though it’s damaged? What will I lose if the only backup I have is from over a year ago?
