ERROR - SQLITE3:(nil) database corruption (Docker)

Should I be worried about these?

Apr 21, 2019 19:26:24.678 [0x7f05437fe700] ERROR - SQLITE3:(nil), 11, database corruption at line 64757 of [bf8c1b2b7a]
Apr 21, 2019 19:26:24.678 [0x7f05437fe700] ERROR - SQLITE3:(nil), 11, database corruption at line 64798 of [bf8c1b2b7a]
Apr 21, 2019 19:26:24.678 [0x7f05437fe700] ERROR - SQLITE3:(nil), 11, statement aborts at 12: [DROP TABLE IF EXISTS ldata_2_wc1;] database disk image is malformed
Apr 21, 2019 19:26:25.005 [0x7f05437fe700] ERROR - SQLITE3:(nil), 11, database corruption at line 64757 of [bf8c1b2b7a]
Apr 21, 2019 19:26:25.006 [0x7f05437fe700] ERROR - SQLITE3:(nil), 11, database corruption at line 64798 of [bf8c1b2b7a]
Apr 21, 2019 19:26:25.006 [0x7f05437fe700] ERROR - SQLITE3:(nil), 11, statement aborts at 12: [DROP TABLE IF EXISTS ldata_2_wc1;] database disk image is malformed

They only seem to appear as the PMS is starting.

Thanks,

Paully

Server Version#: Plex Media Server v1.15.4.919-8e2884e4b - Ubuntu PC x86_64 - build: linux-x86_64 debian

I’m having the same problem. The Discovery - All Libraries is giving me the “There was an unexpected error loading the dashboard” In checking the logs I see same SQLITE3:(nil), 11, database corruption at line 64798 of [bf8c1b2b7a]

Also, all streaming devices are also missing the On Deck discovery

How do we fix these errors?

Pannos

May I suggest you utilize the most recent database backup when you follow this procedure as it appears the previous database migrations did not happen correctly.

https://support.plex.tv/articles/201100678-repair-a-corrupt-database/

I think that made things worse. Now the app won’t start. The Last 2 lines just keep repeating:

Jun 5 23:16:17 Server syslog-ng[10]: EOF on control channel, closing connection;
*** Running /etc/rc.local…
*** Booting runit daemon…
*** Runit started as PID 16
Jun 5 23:16:17 Server cron[21]: (CRON) INFO (pidfile fd = 3)
Jun 5 23:16:17 Server cron[21]: (CRON) INFO (Skipping @reboot jobs – not system startup)
6 10000 /config/Library/Application Support
10000

I retried the sqlite3 import from the dump. Only this time I included a -echo in the command. Seemed to be going well until the end:

CREATE TRIGGER fts4_metadata_titles_before_update BEFORE UPDATE ON metadata_items BEGIN DELETE FROM fts4_metadata_titles WHERE docid=old.rowid; END;
CREATE TRIGGER fts4_metadata_titles_before_delete BEFORE DELETE ON metadata_items BEGIN DELETE FROM fts4_metadata_titles WHERE docid=old.rowid; END;
CREATE TRIGGER fts4_metadata_titles_after_update AFTER UPDATE ON metadata_items BEGIN INSERT INTO fts4_metadata_titles(docid, title, title_sort, original_title) VALUES(new.rowid, new.title, new.title_sort, new.original_title); END;
CREATE TRIGGER fts4_metadata_titles_after_insert AFTER INSERT ON metadata_items BEGIN INSERT INTO fts4_metadata_titles(docid, title, title_sort, original_title) VALUES(new.rowid, new.title, new.title_sort, new.original_title); END;
CREATE TRIGGER fts4_tag_titles_before_update BEFORE UPDATE ON tags BEGIN DELETE FROM fts4_tag_titles WHERE docid=old.rowid; END;
CREATE TRIGGER fts4_tag_titles_before_delete BEFORE DELETE ON tags BEGIN DELETE FROM fts4_tag_titles WHERE docid=old.rowid; END;
CREATE TRIGGER fts4_tag_titles_after_update AFTER UPDATE ON tags BEGIN INSERT INTO fts4_tag_titles(docid, tag) VALUES(new.rowid, new.tag); END;
CREATE TRIGGER fts4_tag_titles_after_insert AFTER INSERT ON tags BEGIN INSERT INTO fts4_tag_titles(docid, tag) VALUES(new.rowid, new.tag); END;
PRAGMA writable_schema=OFF;
ROLLBACK;

It would have helped a great deal to know you’re using Docker.
I don’t know docker or how to support this.

I will retag and hope someone does.

I suspect you’ll have to recreate the container.

Sorry I thought this thread was about Docker. I’ve made a little more progress. The problem resided in the TV Shows folder. I created a TV Shows2 folder, indexed it, Deleted the TV Shows folder and renamed Tv Shows2 to just Tv Shows. So now Discovery comes up, but I can’t mark any shows as “Watched”

UPDATE: I was able to track down the offending show. I was able to mark the entire show as “Unwatched” and then I was able to mark episodes as watched. So far it seems to be working

2nd UPDATE: Looks like the problem is back:
Jun 07, 2019 13:19:14.352 [0x7fe0bec77700] Error — SQLITE3:(nil), 11, statement aborts at 134: [select distinct metadata_items.id as ‘metadata_items_id’, metadata_items.library_section_id as ‘metadata_items_library_section_id’, metadata_items.parent_id as 'metadata_items_parent_
Jun 07, 2019 13:19:14.352 [0x7fe0bec77700] Error — SQLITE3:(nil), 11, statement aborts at 134: [select distinct metadata_items.id as ‘metadata_items_id’, metadata_items.library_section_id as ‘metadata_items_library_section_id’, metadata_items.parent_id as 'metadata_items_parent_
Jun 07, 2019 13:19:14.353 [0x7fe0bec77700] Error — Soci Exception handled: sqlite3_statement_backend::loadRS: database disk image is malformed
Jun 07, 2019 13:19:14.353 [0x7fe0bec77700] Error — Soci Exception handled: sqlite3_statement_backend::loadRS: database disk image is malformed

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