Unable to start Plex service on Synology NAS - Failed to run the package service

Plex Media Server NAS & Devices
1

Server Version#: 1.41.0.8994-60008994

I am unable to start my media server after restarting the service this morning, due to my Plex home page (using plex.tv) suddenly not loading correctly (it was not showing the typical row of Recently Added Movies in my home page).

Upon restarting the service in Synology, I am met with a “Failed to run the package service” error. I can confirm the server was up and running last night, and no new media was added yesterday.

I searched the log files and found a line indicating a corrupt database:
Oct 01, 2024 14:00:39.649 [140706943523472] ERROR - SQLITE3:0x80000001, 11, database corruption at line 71990 of [a29f994989]
Oct 01, 2024 14:00:39.649 [140706943523472] ERROR - SQLITE3:0x80000001, 11, statement aborts at 4: [select max(max(metadata_items.changed_at),max(metadata_items.resources_changed_at)) from metadata_items] database disk image is malformed
Oct 01, 2024 14:00:39.649 [140706943523472] ERROR - Database corruption: sqlite3_statement_backend::loadOne: database disk image is malformed
Oct 01, 2024 14:00:39.649 [140706943523472] ERROR - Error: Unable to set up server: sqlite3_statement_backend::loadOne: database disk image is malformed (N4soci10soci_errorE)

I am unsure of what table/reference is meant by [a29f994989] so I am unable to go into the DB myself to repair the issue.

Does anyone have any insight into what is going on here, or if there’s simply a bad data row I need to fix? I can follow the steps to restore from a backup if needed.

2

Logs.zip (803.4 KB)
Logs are attached here.

3

I have since decided to restore from a backup, since the only collateral damage was losing Watch History of the past 2 days.

Even so, would love to know what happened or went wrong here.

4

@BobbyHertz

Your database got damaged

Oct 01, 2024 13:56:20.591 [140661063821968] ERROR - SQLITE3:0x80000001, 11, database corruption at line 71990 of [a29f994989]
Oct 01, 2024 13:56:20.591 [140661063821968] ERROR - SQLITE3:0x80000001, 11, statement aborts at 4: [select max(max(metadata_items.changed_at),max(metadata_items.resources_changed_at)) from metadata_items] database disk image is malformed
Oct 01, 2024 13:56:20.591 [140661063821968] ERROR - Database corruption: sqlite3_statement_backend::loadOne: database disk image is malformed
Oct 01, 2024 13:56:20.591 [140661063821968] ERROR - Error: Unable to set up server: sqlite3_statement_backend::loadOne: database disk image is malformed (N4soci10soci_errorE)
Oct 01, 2024 13:56:20.591 [140661063821968] DEBUG - [JobRunner] Job running: "/volume1/@appstore/Plex Media Server/CrashUploader" --sessionStatus=abnormal --sessionStart=1727805380 --sessionDuration=0 --version=1.41.0.8994-f2c27da23 --userId=rmbyrnes795@yahoo.com --sentryUrl=https://o17675.ingest.sentry.io/api/1233455/ --sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Oct 01, 2024 13:56:20.591 [140661063821968] DEBUG - [JobRunner] Jobs: Starting child process with pid 13593

if you don’t mind using SSH to get into the Syno, you can usually repair it

1 Like
5

Could the logs indicate any reason as to why? I didn’t perform any updates nor add any additional content between the day before and today.

I can easily connect to the server and run the repair if it happens again, but at this point I’ve already moved forward with a rollback, so I guess the cause will remain unknown for now.

6

If you’ve restored from a backup then that’s enough.

What you normally can do with my tool is have it do is a REPLACE (rollback from database backups which are existing.

If you have them, and the tool is able to validate them as undamaged, it’s usually a lot quicker to do this method.

A common cause for the failure is abrupt power off – OR – PMS needing longer to shutdown than DSM is allowing (rare but it happens)

7

Sounds good. For future reference, where can I find details about this said tool?

8

Also linked above :slight_smile:

1 Like
9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.