"Held transaction for too long" and "database schema has changed" during database optimization

Server Version#: 1.23.4.4712
Player Version#:1.33.0.2444-a220eae4

Hello!

I’m running my Plex server on Unraid using the binhex/plexpass docker image.

I recently migrated from Ubuntu 20.04.1.

I noticed that optimizing my database was taking longer than it used to, so I took a look at the logs and found some lines that worried me a little.

I’m seeing several warnings about “Held transaction for too long”.

Jul 04, 2021 00:14:29.813 [0x146dc5718b38] Warning — [Database optimization/com.plexapp.plugins.library.db] Held transaction for too long (../Library/DatabaseFixups.cpp:213): 0.120000 seconds

As well as a block of the same warning “database schema has changed”.

Jul 04, 2021 00:14:46.453 [0x146dc5718b38] Info — [Database optimization/com.plexapp.plugins.library.db] SQLITE3:0x80000001, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed

I’ve copied the logs from the console to Pastebin.

Is there something wrong with my database?

No.

Held transaction too long is an indicator the system is a bit loaded. Occasional ones are of no concern. If nearly every other statement is this – then a problem

Schema message is normal.

When the database is optimized, the table indexes are removed.

First access after after optimization generates that message because PMS will create the index again.

No harm there

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