Version 1.18.1 SQlite errors and crashing

Plex Media Server Desktops & Laptops
1

Server Version#: 1.18.1.1973-0f4abfbcc Windows 10
Player Version#: Irrelevant

I had previously been on the beta track, so when the beta (1.18.1.1966-10fc2f8d3 I think) installed I had these errors in Plex Media Server.log:

Nov 03, 2019 17:26:10.789 [26376] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: database disk image is malformed
Nov 03, 2019 17:26:15.788 [11756] ERROR - SQLITE3:0xe81c7807, 11, database corruption at line 79051 of [bf8c1b2b7a]
Nov 03, 2019 17:26:15.788 [11756] ERROR - SQLITE3:0xe81c7807, 11, statement aborts at 14: [select media_items.id as 'media_items_id', media_items.library_section_id as 'media_items_library_section_id', media_items.section_location_id as 'media_items_section_location_id', med
Nov 03, 2019 17:26:15.788 [11756] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: database disk image is malformed
Nov 03, 2019 17:26:20.826 [17956] ERROR - SQLITE3:0xe81c7807, 11, database corruption at line 79051 of [bf8c1b2b7a]
Nov 03, 2019 17:26:20.826 [17956] ERROR - SQLITE3:0xe81c7807, 11, statement aborts at 14: [select media_items.id as 'media_items_id', media_items.library_section_id as 'media_items_library_section_id', media_items.section_location_id as 'media_items_section_location_id', med
Nov 03, 2019 17:26:20.826 [17956] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: database disk image is malformed
Nov 03, 2019 17:26:25.819 [90248] ERROR - SQLITE3:0xe81c7807, 11, database corruption at line 79051 of [bf8c1b2b7a]
Nov 03, 2019 17:26:25.819 [90248] ERROR - SQLITE3:0xe81c7807, 11, statement aborts at 14: [select media_items.id as 'media_items_id', media_items.library_section_id as 'media_items_library_section_id', media_items.section_location_id as 'media_items_section_location_id', med
Nov 03, 2019 17:26:25.819 [90248] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: database disk image is malformed
Nov 03, 2019 17:26:30.856 [11756] ERROR - SQLITE3:0xe81c7807, 11, database corruption at line 79051 of [bf8c1b2b7a]
Nov 03, 2019 17:26:30.856 [11756] ERROR - SQLITE3:0xe81c7807, 11, statement aborts at 14: [select media_items.id as 'media_items_id', media_items.library_section_id as 'media_items_library_section_id', media_items.section_location_id as 'media_items_section_location_id', med
Nov 03, 2019 17:26:30.857 [11756] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: database disk image is malformed
Nov 03, 2019 17:26:35.856 [90248] ERROR - SQLITE3:0xe81c7807, 11, database corruption at line 79051 of [bf8c1b2b7a]
Nov 03, 2019 17:26:35.856 [90248] ERROR - SQLITE3:0xe81c7807, 11, statement aborts at 14: [select media_items.id as 'media_items_id', media_items.library_section_id as 'media_items_library_section_id', media_items.section_location_id as 'media_items_section_location_id', med
Nov 03, 2019 17:26:35.856 [90248] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: database disk image is malformed
Nov 03, 2019 17:26:40.889 [11756] ERROR - SQLITE3:0xe81c7807, 11, database corruption at line 79051 of [bf8c1b2b7a]
Nov 03, 2019 17:26:40.889 [11756] ERROR - SQLITE3:0xe81c7807, 11, statement aborts at 14: [select media_items.id as 'media_items_id', media_items.library_section_id as

I downgraded the server to 1.18.0 and kept the updates on the public track, and this error went away. Now that 1.18.1 is on the public track, I updated my server and again have the same errors.

These errors repeat continuously, creating very large log files until the plex server application crashes. When it crashed, the process ends and when I hover my mouse over the icon in the system tray, the icon disappears.

I see this in Plex Crash Uploader.log:

Nov 03, 2019 20:10:30.372 [33988] INFO - Crash Uploader - Platform: Windows ServerUUID: 46fa825e9eafeb627a2489734fca407bd0de1fc1 UserId: <EMAILADDRESS> Version: 1.18.1.1973-0f4abfbcc
Nov 03, 2019 20:10:30.679 [73492] ERROR - Failed to upload crashdump 20da1aac-f195-4fed-9275-618372d3cb14: 429
Nov 03, 2019 20:10:31.577 [73492] ERROR - Failed to upload crashdump 731d8821-1a2c-4a6a-8f40-21568073ae34: 429
Nov 03, 2019 20:10:32.170 [73492] ERROR - Failed to upload crashdump a0874cc9-3bf3-4bdb-952d-086cb2f02442: 429

(I have the dump files but am reluctant to post them here because I don’t know what’s in them. Apparently my Visual Studio trial expired and no idea what else can read these files.)

I tried removing line 79051 from the media_items table in the database (which was an assumption, since the error log does not show the entire query so I do not know from which table it’s have an issue). That didn’t help. I refreshed metadata and optimized database, no help.

I had to go find some old server version files to downgrade and make the error go away. So it seems like this is a bug with the current version of the plex server software. I don’t want to have to rebuild my entire library to solve this issue. I also don’t want to have to keep skipping updates and stay on the old version.

Has anyone else had this issue? Has anyone solved this issue without having to start from scratch with their plex database? It would take ages to redo everything and I really want to avoid it.

2

It’s also possible that you do have a bad database file and it just didn’t affect 1.18.0, but is affecting 1.18.1. I would suggest trying to repair your database following our guide, https://support.plex.tv/articles/201100678-repair-a-corrupt-database/.

1 Like
3

Same exact issue. Repairing does not fix the issue.

1 Like
4 
sqlite3.exe com.plexapp.plugins.library.db "PRAGMA integrity_check"          
ok

It doesn’t seem corrupt. I went through the rest of the instructions and the problem continues. I downgraded back to 1.18.0 again and it went away. :man_shrugging:

5

Can you PM me your database (zipped)?

6

It’s 177mb compressed and I don’t know what personal information it contains so I would rather not. Do you know if there’s a way to see the entire query?

select media_items.id as 'media_items_id', media_items.library_section_id as 'media_items_library_section_id', media_items.section_location_id as 'media_items_section_location_id', med

Or a way to see what bf8c1b2b7a refers to? Is it a table in the database?

7

Not possible.

That’s the result of the query. This makes sense as the query can’t run do to the bad data somewhere.

Only info on your library. Nothing specifically about you like name, address, etc.

Most of the time, the corrupt data has to do with a date field. Check the date fields, sort them and check the beginning and end for something that is not a date. If you find it, just delete that data. In some cases, you might have to delete the entire row in the table.

8

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