Plex broken after snap update

Plex Media Server Desktops & Laptops
, ,
1

Server Version#: 1.24.5.5173
Player Version#: all

an updated version of plexmediaserver was pushed to my machine today

server:/media/user$ snap changes
ID Status Spawn Ready Summary
16 Done today at 09:13 EDT today at 09:14 EDT Auto-refresh snap “plexmediaserver”

in the logs on the server i can see various errors during the update

Oct 27, 2021 09:14:21.013 [0x7ff68c88f6e8] ERROR - SQLITE3:0x80000001, 11, database corruption at line 67183 of [1b256d97b5]
Oct 27, 2021 09:14:21.013 [0x7ff68c88f6e8] ERROR - SQLITE3:0x80000001, 11, statement aborts at 11: [SELECT idx, start_block, leaves_end_block, end_block, root FROM ‘main’.‘fts4_tag_titles_icu_segdir’ WHERE level = ? ORDER BY idx ASC] database disk image is malformed
Oct 27, 2021 09:14:21.020 [0x7ff68c88f6e8] ERROR - SQLITE3:0x80000001, 11, statement aborts at 10: [delete from fts4_tag_titles_icu] database disk image is malformed
Oct 27, 2021 09:14:21.045 [0x7ff68c88f6e8] ERROR - Exception inside transaction (inside=1) (…/Library/FullTextSearch.cpp:81): sqlite3_statement_backend::loadOne: database disk image is malformed
Oct 27, 2021 09:14:21.057 [0x7ff68c88f6e8] ERROR - Exception inside transaction (inside=1) (…/Library/DatabaseMigrations.cpp:237): sqlite3_statement_backend::loadOne: database disk image is malformed
Oct 27, 2021 09:14:21.063 [0x7ff68c88f6e8] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::loadOne: database disk image is malformed

**after this, i cannot play any content from my server. i have tried through android app, roku and directly from the browser on the local machine. **
**i can play the files locally via VLC without issue **
**tried restarting snap as well as rebooting and remounting the drives. **
still no playback possible

**playback errors: **
on ROKU: Playback Error: please check that this file exists and the necessary drive is mounted
Browser: Playback Error: An error occurred loading items to play.

In the server logs i see three types of errors that i do not see prior to the refresh:

Oct 27, 2021 11:45:28.849 [0x7ff685e3fb38] ERROR - Metadata /system/agents/media/get request failed with code: 500: http://127.0.0.1:35251/system/agents/media/get?guid=com.plexapp.agents.thetvdb%3A%2F%2F72231%2F19%2F15%3Flang%3Den&mediaType=4&url=metadata%3A%2F%2Fseasons%2F19%2Fepisodes%2F15%2Fthumbs%2Fcom.plexapp.agents.thetvdb_46febaac5f305e59960613526d780feff4512c22

Oct 27, 2021 11:45:31.546 [0x7ff686f99b38] ERROR - SQLITE3:0x80000001, 1, no such table: metadata_item_setting_markers in "select metadata_item_setting_markers.id as ‘metadata_item_setting_markers_id’, metadata_item_setting_markers.marker_type as 'metadata_item_setting_markers_marke

Oct 27, 2021 11:45:31.547 [0x7ff686f99b38] ERROR - Soci Exception handled: sqlite3_statement_backend::prepare: no such table: metadata_item_setting_markers for SQL: select metadata_item_setting_markers.id as ‘metadata_item_setting_markers_id’, metadata_item_setting_markers.marker_type as ‘metadata_item_setting_markers_marker_type’, metadata_item_setting_markers.metadata_item_setting_id as ‘metadata_item_setting_markers_metadata_item_setting_id’, metadata_item_setting_markers.start_time_offset as ‘metadata_item_setting_markers_start_time_offset’, metadata_item_setting_markers.end_time_offset as ‘metadata_item_setting_markers_end_time_offset’, metadata_item_setting_markers.title as ‘metadata_item_setting_markers_title’, metadata_item_setting_markers.created_at as ‘metadata_item_setting_markers_created_at’, metadata_item_setting_markers.updated_at as ‘metadata_item_setting_markers_updated_at’, metadata_item_setting_markers.extra_data as ‘metadata_item_setting_markers_extra_data’ from metadata_item_setting_markers join metadata_item_settings on metadata_item_settings.id = metadata_item_setting_markers.metadata_item_setting_id where metadata_item_settings.guid = ? and metadata_item_settings.account_id = ? order by metadata_item_setting_markers.start_time_offset, metadata_item_setting_markers.end_time_offset

1 Like
2

Having the same issue, three hours now
TimeOct 27, 2021 18:58:29.821

LevelError

Thread0x146a17234b38

MessageSQLITE3:0x80000001, 1, no such table: metadata_item_setting_markers in "select metadata_item_setting_markers.id as ‘metadata_item_setting_markers_id’, metadata_item_setting_markers.marker_type as 'metadata_item_setting_markers_marke

Nothing plays.

3

Oct 27, 2021 19:02:12.446 [0x146a169beb38] Error — SQLITE3:0x80000001, 1, no such table: metadata_item_setting_markers in "select metadata_item_setting_markers.id as ‘metadata_item_setting_markers_id’, metadata_item_setting_markers.marker_type as 'metadata_item_setting_markers_marke
Oct 27, 2021 19:02:12.446 [0x146a169beb38] Error — Soci Exception handled: sqlite3_statement_backend::prepare: no such table: metadata_item_setting_markers for SQL: select metadata_item_setting_markers.id as ‘metadata_item_setting_markers_id’, metadata_item_setting_markers.marker_type as ‘metadata_item_setting_markers_marker_type’, metadata_item_setting_markers.metadata_item_setting_id as ‘metadata_item_setting_markers_metadata_item_setting_id’, metadata_item_setting_markers.start_time_offset as ‘metadata_item_setting_markers_start_time_offset’, metadata_item_setting_markers.end_time_offset as ‘metadata_item_setting_markers_end_time_offset’, metadata_item_setting_markers.title as ‘metadata_item_setting_markers_title’, metadata_item_setting_markers.created_at as ‘metadata_item_setting_markers_created_at’, metadata_item_setting_markers.updated_at as ‘metadata_item_setting_markers_updated_at’, metadata_item_setting_markers.extra_data as ‘metadata_item_setting_markers_extra_data’ from metadata_item_setting_markers join metadata_item_settings on metadata_item_settings.id = metadata_item_setting_markers.metadata_item_setting_id where metadata_item_settings.guid = ? and metadata_item_settings.account_id = ? order by metadata_item_setting_markers.start_time_offset, metadata_item_setting_markers.end_time_offset
Oct 27, 2021 19:02:12.447 [0x146a1819db38] Debug — Completed: [10.0.0.10:49466] 500 POST /playQueues?

4

Update, I rolled back the snap package to the previous version and seems to have resolved the issue now.

in terminal type
sudo snap revert plexmediaserver

Should get a message like this
plexmediaserver reverted to 1.24.2.5022-8489a6711

can also confirm with command: snap changes
ID Status Spawn Ready Summary
16 Done today at 09:13 EDT today at 09:14 EDT Auto-refresh snap “plexmediaserver”
20 Done today at 18:51 EDT today at 18:51 EDT Revert “plexmediaserver” snap
21 Done today at 18:51 EDT today at 18:51 EDT Running service command

1 Like
5

If you had some actual database corruption, it’s very unlikely this will be fixed by rolling back to another version. To avoid greater damage you might want to check your database and if needed attempt to repair it.

6

@Plex Ninja how do you repair it in a docker container

docker
docker839×596 27.5 KB

Don’t see it in the help .

7

Never tried that myself. From what I’ve been reading you cannot fix it from within the container (due to the container restrictions). You’ll need to create a dummy PMS install on another system. Run that install’s Plex SQLite executable with the docker container’s DB path. Make sure both Plex Media Servers are stopped when to work on the database!!

8

@ Plex Ninja to late
I followed How do I repair my database when running PMS in a Docker container on an Unraid server

Completely messed it up, had to remove the container and then I installed the Plex Server on windows pc.

It running away re-adding the media, bummer is I have to now mark those films I watched as played. will take a while lol -:slight_smile:

9

autmatic snap update happened again last night and again broke plex. same errors noted in the logs as last time.

Snap ver. 1.25.0.5282

i guess this means I’ll never be able to update plex since it fails every time…?
how do i fix this?

10

May I ask a , perhaps foolish, question?

Why use SNAP when the native package is so much more capable and also has automatic updating via the repository available ?

12

it did appear to be the most popular way to install it, figured it was safe especially considering I’m running it on an Ubuntu distribution and Canonical are the ones that developed snaps but I’m definitely regretting that decision now.

13

Ubuntu only supports SNAP packages from their App Store.

It’s not popular but is what they’re pushing.

It is possible to pull all your Plex metadata out of the SNAP package so you can get away from it.

14

agreed, i had to rebuild my server recently where i was running the native app before and decided to try the snap install so was able to successfully import the database from the previous install to this one. So i’m sure i can figure out how to do the reverse but, question is, will i still have this db corruption issue and therefore have the same problem?

and i guess, perhaps the even larger question is, should plex put out some official statement about not supporting snap installs? There’s like 0 documentation available …

15

Plex does support SNAPs else there wouldn’t be a package.

There are users who are quite happy with SNAPs because their streaming needs don’t require full access to the hardware which transcoding and tonemapping mandates

16

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