@ChuckPa I have tried the steps you outlined in the closed topic and I’m hoping that you can help me figure out what is going on with my system.
Continuing the discussion from "Failed to run the package service":
Server Version#:
Player Version#:
Logs.zip (2.7 MB)
You have a corrupt database.
Mar 13, 2020 00:11:09.778 [0x7f7e8927c700] INFO - Linux version: DSM 6.2.2.24922-4, language: en-US
Mar 13, 2020 00:11:09.779 [0x7f7e8927c700] INFO - Processor Intel(R) Celeron(R) CPU J3455 @ 1.50GHz
Mar 13, 2020 00:11:09.779 [0x7f7e8927c700] INFO - /var/packages/Plex Media Server/target/Plex Media Server
Mar 13, 2020 00:11:09.663 [0x7f7e938bd740] DEBUG - BPQ: [Idle] -> [Starting]
Mar 13, 2020 00:11:09.780 [0x7f7e938bd740] DEBUG - FeatureManager: Using cached data for features list
Mar 13, 2020 00:11:09.901 [0x7f7e938bd740] DEBUG - Opening 20 database sessions to library (com.plexapp.plugins.library), SQLite 3.26.0, threadsafe=1
Mar 13, 2020 00:11:10.642 [0x7f7e88ca0700] DEBUG - Job running: '/volume1/@appstore/Plex Media Server/CrashUploader' '--directory=/volume1/Plex/Library/Application Support/Plex Media Server/Crash Reports/1.18.8.2527-740d4c206' '--version=1.18.8.2527-740d4c206' '--platform=Linux' '--platformVersion=DSM 6.2.2.24922-4' '--serverUuid=2ef2130faffde7bdaab39d00290a6d090c404dc1' '--userId=derrickerr@gmail.com' '--sentryUrl=https://sentry.io/api/1233455/minidump' '--sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' '--vendor=Synology' '--model=x86_64' '--device=DS718+'
Mar 13, 2020 00:11:10.749 [0x7f7e88ca0700] DEBUG - Jobs: Starting child process with pid 24403
Mar 13, 2020 00:11:16.635 [0x7f7e88f8e700] DEBUG - Jobs: '/volume1/@appstore/Plex Media Server/CrashUploader' exit code for process 24403 is 0 (success)
Mar 13, 2020 00:11:19.569 [0x7f7e88f8e700] DEBUG - Shutting down with signal 15 (Terminated)
Mar 13, 2020 00:11:19.569 [0x7f7e88f8e700] DEBUG - Ordered to stop server.
Mar 13, 2020 00:11:19.569 [0x7f7e88f8e700] WARN - Timed out waiting for server to finish.
Mar 13, 2020 00:11:25.635 [0x7f7e88f8e700] DEBUG - Server is already in shutdown mode, ignoring this signal...
Mar 13, 2020 00:11:30.229 [0x7f7e938bd740] INFO - SQLITE3:(nil), 283, recovered 873 frames from WAL file /volume1/Plex/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db-wal
Mar 13, 2020 00:11:36.191 [0x7f7e88f8e700] DEBUG - Server is already in shutdown mode, ignoring this signal...
Mar 13, 2020 00:11:37.682 [0x7f7e938bd740] DEBUG - Running migrations. (EPG 0)
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Running forward migration 20200131193503.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 0.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 1.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 2.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 3.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 4.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 5.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 6.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 7.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 8.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 9.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 10.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 11.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 12.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 13.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 14.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 15.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 16.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 17.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 18.
Mar 13, 2020 00:11:37.683 [0x7f7e938bd740] DEBUG - Captured session 19.
Mar 13, 2020 00:12:01.190 [0x7f7e88f8e700] DEBUG - Server is already in shutdown mode, ignoring this signal...
Mar 13, 2020 00:12:06.809 [0x7f7e88f8e700] DEBUG - Server is already in shutdown mode, ignoring this signal...
Mar 13, 2020 00:12:12.095 [0x7f7e88f8e700] DEBUG - Server is already in shutdown mode, ignoring this signal...
Mar 13, 2020 00:12:24.082 [0x7f7e938bd740] ERROR - SQLITE3:(nil), 11, database corruption at line 64817 of [bf8c1b2b7a]
Mar 13, 2020 00:12:24.083 [0x7f7e938bd740] ERROR - SQLITE3:(nil), 11, statement aborts at 9: [UPDATE metadata_items SET extra_data = replace(extra_data, 'at%3AreadOnly=', 'pv%3AreadOnly=') WHERE extra_data LIKE '%at^%3AreadOnly=%' escape '^'] database disk image is malformed
Mar 13, 2020 00:12:49.079 [0x7f7e938bd740] ERROR - Exception inside transaction (inside=1) (../Library/DatabaseMigrations.cpp:209): sqlite3_statement_backend::loadOne: database disk image is malformed
Mar 13, 2020 00:12:49.110 [0x7f7e938bd740] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::loadOne: database disk image is malformed
Mar 13, 2020 00:12:56.274 [0x7f7e88f8e700] DEBUG - Server is already in shutdown mode, ignoring this signal...
Mar 13, 2020 00:13:01.509 [0x7f7e88f8e700] DEBUG - Server is already in shutdown mode, ignoring this signal...
Mar 13, 2020 00:13:06.566 [0x7f7e88f8e700] DEBUG - Server is already in shutdown mode, ignoring this signal...
Since that thread, I’ve captured a few steps
What if I don’t have any backups of my DB? I have backups of the com.plexapp.plugins.library.blobs.db just not the com.plexapp.plugins.library.db. I was able to remove the .wal and .shm files and renamed the com.plexapp.plugins.library.blobs.db to -damaged. I tried to open the PMS web interface but I am not able to access the server, just an error “No soup for you!
You do not have access to this server” I appreciate the humor and reference but it wasn’t very helpful lol.
The blobs (binary large objects) don’t do you any good without the primary linkages in the main db.
The Seinfeld ref is old and not helpful at all.
It means there server is compromised and locked down (which will happen with the empty database it created at startup after the main was removed)
This is the “erase all and start over” moment. Sorry
When you setup again, please do make certain to leave Database Backups enabled in the Scheduled Tasks and that the server is on during the interval so they may complete.
Thank you. What would be the easiest way to start over from scratch?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
