Statement aborts messages after doing DB Optimize

Plex Media Server Desktops & Laptops
1

Server Version#: 1.13.8.5395
Player Version#: server only issue

everytime I do an optimize i get a bunch of these messages in my logs:
Oct 05, 2018 10:43:50.396 INFO SQLITE3:0xfd4cc768, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed

Is this normal? I have done a DB repair (it reported OK but I still did the repair) and I still get the messages.

I notice no issues with my DB at all, I am just curious if this normal or if there is something I should be doing.

Thanks!

2

Have you restarted your PMS recently. “schema changes” should automatically be updated and fixed.

3

Yes I have restarted it numerous times and the messages are still there, I get about 20 lines of that same message in the logs

4

Here is a log after I just did another reboot I did a database optimize and then did another one to get the second set of the errors. I don’t know if it will be of any use to you.

Plex Media Server.log (9.7 KB)

5

Are you rebooting your machine? It looks like you are running PMS as a service. Did you set PMS to not automatically start on boot? If not, you’ll have 2 instances of PMS conflicting with each other. You’ll need to turn on debug logging in your PMS settings and try again. There’s not enough info with the current log. Make sure all instances of PMS are stopped, then just start PMS. No need to restart your entire computer.

6

I am not rebooting my system, I have never set plex to run as a service I am pretty sure it is not running at a service, if I check my services I only have the Plex Update Service listed there, I have PMS set to start on login. Also I only have one instance of PMS running.

Here is a log with Debug enabled:
Plex Media Server.log (263.9 KB)

Thank you so much for your assistance with this!

7

Ah sorry. I think I was looking at the wrong log. I am not having a good day today.

Looking at your new log, I see the message about the schema. PMS is suppose to try to fix these on start-up, but I’m not seeing these messages in your log.

You said you tried to repair the database. Did you get any errors during the process?

8

No worries, you seem like a busy person! :slight_smile: there were no errors. I did another repair:

image
image1432×343 29.8 KB

just for S & G’s here is another log after this repair:
Plex Media Server.log (159.9 KB)
Though it shows the same thing as before. messages still showing up and no attempt to try and fix errors at PMS start.

9

Just an update, I am no longer getting these warnings. I am not sure what happened to resolve the issue but it is good now. Thanks!

10

After upgrade these messages are back. any help?

Plex Media Server (4).log (120.7 KB)

11

Can you PM me your database?

12

any update on this? I am still getting errors. thanks,

13

Bump. Still getting these errors:

Oct 29, 2018 10:43:58.627 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.629 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.631 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.632 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.634 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.636 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.638 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.640 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.642 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.644 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.646 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.648 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.650 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.652 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.654 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.656 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.658 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.660 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
Oct 29, 2018 10:43:58.662 [3632] INFO - SQLITE3:0x5348e79c, 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
14

Sorry, haven’t had time to look through your DB yet. I’ll get to it soon.

15

Sounds good, Thank you!

16

This issue is still ongoing… :frowning:

17

Seriously issue still exists. Here is my monthly bump.

18

Sorry. Last I looked I couldn’t find anything wrong with your DB either. Another possibility. Do you have the DVR feature setup? That error could be coming from it’s DB, which is different from the main Plex one.

19

i believe those statements are NORMAL when doing an optimize.

sql is simply stating that the schema has changed because basically the database is being re-created.

https://www.google.com/search?q=database+schema+has+changed

20

We have steps to update the DB to the latest schema so you should not have those errors except on a new install. If you have these errors, then one of the update steps failed. I couldn’t find anything wrong with his DB, which is why I think the error might be coming from another DB. We really should indicate which DB is giving the error, but we don’t do that.