Jun 01, 2019 19:15:07.256 [0x152ca5670700] ERROR - SQLITE3:(nil), 11, database corruption at line 79998 of [bf8c1b2b7a]
Jun 01, 2019 19:15:07.256 [0x152ca5670700] ERROR - SQLITE3:(nil), 11, database corruption at line 68430 of [bf8c1b2b7a]
Jun 01, 2019 19:15:07.256 [0x152ca5670700] ERROR - SQLITE3:(nil), 11, statement aborts at 9: [SELECT (SELECT max(idx) FROM 'main'.'fts4_tag_titles_segdir' WHERE level = ?) + 1] database disk image is malformed
Jun 01, 2019 19:15:07.257 [0x152ca5670700] ERROR - Failed to commit transaction (../Library/MetadataItem.cpp:6079) (tries=1): Cannot commit transaction. database disk image is malformed
Jun 01, 2019 19:15:07.764 [0x152ca5670700] ERROR - SQLITE3:(nil), 1, statement aborts at 1: [COMMIT] cannot commit - no transaction is active
Having the same kind of issue on my UnRaid instance running latest UnRaid (6.7.0) and Plex docker versions.
Some libraries work while others don’t. Seeing the same SQLITE3:(nil), 11, database corruption lines in my log files. Does plex automatically back up the database that I can use to restore from or was that something I should have been better on top of?
Also experiencing database corruption with unRAID 6.7.0 and Plex version 1.15.8.1163 on linuxserver/plex:latest Docker image. Database restore steps didn’t help, restored from an old backup of the /config Docker volume, dashboard showed unexpected error again within 8 hours.
Logs:
Jun 03, 2019 13:25:55.925 [0x1505c93e9700] Error — SQLITE3:(nil), 11, database corruption at line 79051 of [bf8c1b2b7a]
Jun 03, 2019 13:25:55.925 [0x1505c93e9700] Error — SQLITE3:(nil), 11, statement aborts at 7: [select distinct metadata_items.id from metadata_items where metadata_items.library_section_id in (1) and ((metadata_items.metadata_type=2 or metadata_items.metadata_type=18) and (metad
Jun 03, 2019 13:25:55.926 [0x1505c93e9700] Error — Soci Exception handled: sqlite3_statement_backend::loadRS: database disk image is malformed
I initially configured this server with unRAID 6.7.0 so I don’t want to downgrade to 6.6.7 (which sounds so far like the only fix) so I’m just going to disable Plex and follow the forums until there is a fix.