Server Version#: 1.29.2.6364-6d72b0cf6
Docker Container: linuxserver/plex
Player Version#: N/A
Tuner Make/Model: HDHomeRun FLEX 4K
Guide/Lineup name:
Using XMLTV?: No
When running the refresh guide, the debug logs show that the database cannot be swapped out due to an error. This is on a fresh install of Plex using the docker container image:
See below.
Dec 11, 2022 11:01:44.935 [0x7f2115a80b38] ERROR - [Req#11cf] SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Dec 11, 2022 11:01:44.935 [0x7f2115a80b38] ERROR - [Req#11cf] SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
Dec 11, 2022 11:01:44.935 [0x7f2115a80b38] ERROR - [Req#11cf] SQLITE3:0x80000001, 11, statement aborts at 10: database disk image is malformed
Dec 11, 2022 11:01:44.935 [0x7f2115a80b38] ERROR - [Req#11cf] SQLITE3:0x80000001, 11, database disk image is malformed in “PRAGMA cache_size=2000”
Dec 11, 2022 11:01:44.937 [0x7f2115a80b38] ERROR - [Req#11cf] SQLITE3:0x80000001, 11, database corruption at line 66843 of [1b256d97b5]
Dec 11, 2022 11:01:44.937 [0x7f2115a80b38] ERROR - [Req#11cf] SQLITE3:0x80000001, 11, database corruption at line 66993 of [1b256d97b5]
Dec 11, 2022 11:01:44.937 [0x7f2115a80b38] ERROR - [Req#11cf] SQLITE3:0x80000001, 11, statement aborts at 10: database disk image is malformed
Dec 11, 2022 11:01:44.937 [0x7f2115a80b38] ERROR - [Req#11cf] SQLITE3:0x80000001, 11, database disk image is malformed in “select * from metadata_items limit 1”
Dec 11, 2022 11:01:44.937 [0x7f2115a80b38] ERROR - [Req#11cf] EPG: We caught an exception trying to swap out the database: sqlite3_statement_backend::prepare: database disk image is malformed for SQL: PRAGMA cache_size=2000
Sorry I forgot to mention that this is the output from a clean install. I have also went through the process of database repair to no avail. Every time I refresh the guide, it gives this error.
If the database is still corrupted, then something is wrong with the installation.
If there is a pre-existing database, then use the repair utility.
Depending on how things are configured, uninstalling Plex Media Server does not necessarily remove the Plex Data Folder, where the database is located.
It is possible a pre-existing db was corrupt, but Plex could still run.
When updating to a new release, Plex may also update how the db is organized. If the db was already corrupt, the update may fail, and cause additional problems or Plex may even refuse to run.
Basically, there are degrees or db corruption. If only slightly corrupted, it may not yet be noticeable. However, updating to a new release may push things over the edge, necessitating the db repair process.
I’ve went through these processes before. The one difference I can think of from a previous install is that I’m storing the plex database on a Samba share. My previous installation used a path on the local virtual machine. I’ll test this to see if it makes a difference.
You might be able to use iSCSI, since it appears as a local drive to the system. I’ve no experience with iSCSI, so don’t know how well it works (or doesn’t).
This was 100% my problem. I switched the mount point to a local path on the VM and it works perfectly. I wasted 3 days trying to figure this out. Too bad Plex doesn’t use a different database instead of SQLITE. Thanks for your micro-journey helping me figure this out.