Playback issues seemingly caused by database changes in 1.24.5.5173 [Fixed by downgrade]

Plex Media Server
, ,
1

Server Version#: 1.24.5.5173
Player Version#: Samsung Smart TV client version 5.25.3, Roku client version 6.9.10.7373-629387567

After upgrading to 1.24.5.5173 I had multiple clients report a generic playback issue (listed above). I set the samsung client to log to my server, and trying to load and play a file gave me this:

Oct 30, 2021 11:53:40.856 [8740] ERROR - Error issuing curl_easy_perform(handle): 28
Oct 30, 2021 11:53:40.856 [0268] ERROR - Error issuing curl_easy_perform(handle): 28
Oct 30, 2021 11:53:40.930 [15300] ERROR - Unknown metadata type:
Oct 30, 2021 11:53:44.485 [17016] ERROR - SQLITE3:0xb4f7ef1b, 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 30, 2021 11:53:44.486 [17016] 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 30, 2021 11:53:44.497 [10084] ERROR - Error issuing curl_easy_perform(handle): 6

I see that 1.24.5.5173 lists “Database changes” in the changelog. Uninstalling PMS and then installing 1.24.4.5081 fixed this playback issue for me. I have other logs and could fairly easily replicate this if needed.

2

Same here. These DB changes corrupted my DB and yes I waited and allowed the libraries to be updated during startup and after uninstalling and repairing with the same update (1.24.5.5173) and even going through the DB repair/restore process it was still corrupted and wouldn’t play anything.

The only fix was to go back to a previous version. If you don’t have a previous version let me know. I have like 30 pervious versions.

3

I pack my error times here to it. With a Samsung TV version 1.24.4 and version 1.24.5 the playback does not work anymore. It always comes the error message “Multimedia file format not supported”.

I have now installed version 1.23.3 again, so the playback works again.

platform=Tizen, platformVersion=2.4, device=16_HAWKM_FHD, model=UE55K6379

4

Have you turned off secure connections for the TV and set the server to Preferred.

5

Yes, this is not the secure connections issue. As noted it was fixed by downgrading (and making no other settings changes). It was also happening on the Roku client, which to my knowledge was not part of the LetsEncrypt root cert expiration issue.

edit: I realize now you may have been suggesting a solution for SaschaK.

6

After updating to 1.24.5.5173, Plexamp crashes the Plex server: the server stops working, the icon in the taskbar disappears, and I need to restart Plex to have everything back online. It happens using Plexamp for desktop and for telephone (Android). Before updating, anything worked perfectly. It happens only with Plexamp, with the “traditional” Plex player everything runs without problems. Any idea? (Using Windows Server 2022 as Plex server, latest patches installed; Windows version of Plex Media Server).

7

I had the same issue, missing the metadata_item_settings_markers table. I fixed it by executing the following SQL statements on the library db:

DROP TABLE IF EXISTS 'metadata_item_setting_markers'

CREATE TABLE 'metadata_item_setting_markers' ('id' INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, 'marker_type' integer NOT NULL, 'metadata_item_setting_id' integer NOT NULL, 'start_time_offset' integer NOT NULL, 'end_time_offset' integer, 'title' varchar(255), 'created_at' integer(8), 'updated_at' integer(8), 'extra_data' varchar(255), FOREIGN KEY(metadata_item_setting_id) REFERENCES metadata_item_settings(id) ON DELETE CASCADE)

CREATE INDEX 'index_metadata_item_setting_markers_on_metadata_item_setting_id' ON 'metadata_item_setting_markers' ('metadata_item_setting_id')

CREATE INDEX 'index_metadata_item_setting_markers_on_updated_at' ON 'metadata_item_setting_markers' ('updated_at')

After this, plex clients started to behave as expected.

8

@peralta how can I do this?
or is it safer for me to just downgrade the plexserver on my nas?

9

Also playback works for me in original quality, but as soon as I want to change quality to a lower es playback stops working

10

To make changes in the Plex database you need a SQLLite management tool as, for example, DBBrowser. At least, that is for Plex installed in a computer, I do not if it works in the same way for a NAS. In any way, the modifications suggested by peralta didn’t work for me because the “metadata_item_settings_markers” table was already in the database, and it was empty.
If it can help, I ran a database optimalization from the Plex administration in my server (the button “Optimize Database” in the “Troubleshooting” section), and that solved one part of the problem: if I start Plexamp, the server doesn’t crash anymore. But all the special sections of Plexamp, such as “Stations”, are stil not working at all…

11

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