Server Version#: DSM 6.2.4-25556
Player Version#:
I installed the latest package update, and also changed my Plex password, as requested related to the data breach.
Now, I am unable to start the plex package on my Synology NAS, and there is nothing in the log center that indicates what the issue might be. Sometimes I get a “Failed to start the package service” notification.
Using FileStation,
Navigate to Plex / Library / Application Support / Plex Media Server
Right-click Logs → Compress to Logs.zip
Download that ZIP file and attach here please.
I will look at it
Will do.
I wasn’t sure where the plex logs were, but since you pointed me to them, I saw this in the media server log, and looks like a bad sign 
Aug 26, 2022 12:27:07.274 [0x72525c50] DEBUG - [JobRunner] Job running: “/volume1/@appstore/Plex Media Server/CrashUploader” “–directory=/volume1/Plex/Library/Application Support/Plex Media Server/Crash Reports/1.28.1.6104-788f82488” --version=1.28.1.6104-788f82488 --platform=Linux “–platformVersion=DSM 6.2.4.25556-0” --serverUuid=0f32d13ab67eb3c7cd490afd707833d586e936da --userId=xxxxxxxxxxxx --sentryUrl=https://sentry.io/api/1233455/minidump --sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx --vendor=Synology --model=armv7l --device=DS218j --allowRetries=0
Aug 26, 2022 12:27:07.275 [0x72525c50] DEBUG - [JobRunner] Jobs: Starting child process with pid 22023
Aug 26, 2022 12:27:07.374 [0x72db1c50] DEBUG - Jobs: ‘/volume1/@appstore/Plex Media Server/CrashUploader’ exit code for process 22023 is 0 (success)
Aug 26, 2022 12:27:07.588 [0x75c49c50] ERROR - SQLITE3:(nil), 11, database corruption at line 66843 of [1b256d97b5]
Aug 26, 2022 12:27:07.589 [0x75c49c50] ERROR - SQLITE3:(nil), 11, database corruption at line 66993 of [1b256d97b5]
Aug 26, 2022 12:27:07.589 [0x75c49c50] ERROR - SQLITE3:(nil), 11, statement aborts at 1028: [ANALYZE] database disk image is malformed
Aug 26, 2022 12:27:07.634 [0x75c49c50] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::loadOne: database disk image is malformed
Aug 26, 2022 12:27:08.843 [0x75c49c50] DEBUG - ChangestampAllocator: initialized to 1124357
Aug 26, 2022 12:27:08.976 [0x75c49c50] ERROR - SQLITE3:(nil), 11, database corruption at line 66843 of [1b256d97b5]
Aug 26, 2022 12:27:08.976 [0x75c49c50] ERROR - SQLITE3:(nil), 11, database corruption at line 66993 of [1b256d97b5]
Aug 26, 2022 12:27:08.976 [0x75c49c50] ERROR - SQLITE3:(nil), 11, statement aborts at 21: [update activities set finished_at=started_at where finished_at is null] database disk image is malformed
Aug 26, 2022 12:27:08.977 [0x75c49c50] ERROR - Database corruption: sqlite3_statement_backend::loadOne: database disk image is malformed
Aug 26, 2022 12:27:08.977 [0x75c49c50] ERROR - Error: Unable to set up server: sqlite3_statement_backend::loadOne: database disk image is malformed (N4soci10soci_errorE)
Logs.zip (2.1 MB)
YEP… that’s a bad sign.
The database doesn’t pass basic integrity check.
Do you have some basic SSH (keyboard command line) skills ?
I did. Very, very stale at this point. I used to be a Unix admin, but that was a long time ago.
Am I looking at following the instructions here to repair it?
I got all the way through the steps in that support article for repairing a corrupt database, except that the owner is not plex, and when I try to chown to set the correct user, it tells me that the operation is not permitted. I’m guessing I need to execute that as root…tried sudo root, but I have no idea what the root pw is.
I figured it out, and the db recovery seems to have worked. I’m able to start the Plex Media Server now, and I can access it via the client. Nothing is obviously missing/wrong. Is there anything I should look for specifically that would have been lost in the database recovery process?
Sorry for not being available today… It’s been 
You’ll just have to keep an eye open for things which might be missing / outdated.
Normal scheduled tasks should get it all back in line naturally if anything is missing
Ok, sounds good.
I did find that when I tried to access Plex on my Nvidia Shield, it wants me to “claim the server”, however I can’t find any way to do that. The option within the app does not work, and I can’t find the option within the web app, which it recommends as an alternative.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
