Latest PMS update broken? - PMS 1.14.1.5488

Plex Media Server Desktops & Laptops
21

So they don’t get lost on my Destkop over the holiday, would you mind hanging on to them?

We can then ask Engineering how next to proceed.

22

Sure thing Chuck. Have a pleasant holiday!

23

Yes i can… i didn’t share the steps because if your corruption is in another table this has potential to make things worse. Please proceed with caution. First things 1st. Always make a backup of your database, you should never do any work on the live copy of your database. I recommend starting with the database you had before any repair work. Standard disclaimer, i am not responsible for anything that happens passed this point :slight_smile:

To start load the database:
sqlite3 com.plexapp.plugins.library.db

from there check to see if the taggings data is corrupted:
select * from taggings

if this doesn’t return an error that the database disk image is malformed you should stop here, as the rest of the steps will not improve your situation. If you do error out the steps would be as follows:

  • .output taggings.sql
  • .dump taggings

open the file taggings.sql in a text editor. Look for any line that has /****** CORRUPTION ERROR *******/ and delete it, and then i also deleted the last line Rollback;
Note: i am not sure these steps were neccessary

then do the following in sqllite :

  • drop table taggings
  • .read taggings.sql
  • commit;

At this point your table should have a new taggings table minus the corrupted data. You can test this by typing :
-select * from taggings

if you don’t receive any errors you should in theory be back in business. Put the updated database file in the plex database server and start your server.

Good luck.

24

Having the same issue, had to revert to version 1.14.1.5487-1-01 and recover a library backup. Very disappointed that this also happened with an update a few months ago was also library-destroying, but I had to completely start from scratch then. Is anyone testing code before it’s pushed? I’ve extremely hesitant to update at all after this, again.

25

I hope you had a good holiday season! I haven’t had a chance to try dacmcbibs’ database instructions yet, because reading through them, I decided I need to learn a lot more about databases before I start messing around. Has there been any progress from your side? I appreciate that you’re likely very busy.

26

Is there any update on this? I would like to update PMS but I don’t want to wreck my database. :frowning:

27

Please do try 1.15.0, which is now Plex Pass. A lot of bug fixes have been put into 1.15.0

28

Thanks Chuck. I gave it a try (just now) and it still doesn’t work. The logs have a whole bunch of errors like:

Feb 13, 2019 19:22:39.249	ERROR	SQLITE3:(nil), 1, no such table: media_stream_settings in "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_l

I’ll PM you my logs. [edit] … or not? Apparently I can’t PM you. Should I send them to Dr. Zoidberg again?

29

Does PMS stop immediately after that?

That message normally shows when the database is performing migration (updates) as versions change.

You should look for a backup database /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Plug-in Support/Databses

Stop PMS,
copy one of the backups to be com.plexapp.plugins.library.db

Be 100% certain the new “active” DB ^^ is owned by user plex:plex

30

PMS does not stop; it keeps running, but the dashboard and library sections fail to load properly, and I can’t play any videos.

There are no backups in the Databases directory; Plex has not generated any automatic backups since time out of mind.

I’m 100% certain the DB is NOT owned by plex:plex; everything is owned by canadrian:canadrian, which is what I have set in /etc/systemd/system/plexmediaserver.service.d/override.conf :

[Unit]

Requires=cloud-drive.service

[Service]

User=canadrian
Group=canadrian
31

Ok, so you changed the username Plex runs as. Then ownership should be a non-issue.

Due to being overwhelmed by unsolicited PMs. I had to disable free inbound.
I will PM you

32

By the way, I did this and received no errors, so likely the issue isn’t the taggings table in my case. Thanks for the writeup, and sorry to take up your time.

33

For those who arrive from Google:

I managed to fix this, despite not really understanding databases, and despite not really understanding why the steps I took worked. Here’s what I did (minus a lot of failed/aborted/superfluous experimentation):

  1. Follow Steps 1-5 only in the Run a Repair section of the KB article on repairing a corrupt database.
  2. Do not perform Step 6; for some reason, Step 6 takes forever and produces a database with a file size of zero bytes. I tried removing the ROLLBACK statement at the end of the dump.sql, but with the same result.
  3. Open dump.sql in Notepad++
  4. Use the Find function of Notepad++ to search for CORRUPTION (and do yourself a favour - tick the box to be case-sensitive so you don’t just find a bunch of movie descriptions). The database dump is huge, so each time you hit the Find button, it will take a long time. There will be one or more instances of the following:
/****** CORRUPTION ERROR *******/
  1. Delete each line that matches the above.
  2. Scroll all the way to the end of the dump.sql and the last line looks like this:
ROLLBACK; -- due to errors
  1. Delete that line also.
  2. Save and close the file.
  3. So now can you import the dump.sql into a database using the command-line instructions from Plex? Apparently not. It still creats a zero byte database. Why? Who knows. Instead, go download DB Browser for SQLite. Install it and open it.
  4. In the DB Browser, click File > Import > Database from SQL File…
  5. Choose your newly-modified dump.sql
  6. The program prompts for a filename for the new database you’re going to create. Use com.plexapp.plugins.library.db
  7. When the database import completes, go over to the “Execute SQL” tab, paste in PRAGMA integrity_check, and click the Run button. It will take forever.
  8. Assuming the integrity check returns OK, save & close the database.
  9. Place the new com.plexapp.plugins.library.db back where it’s supposed to go in the Plex folder structure, and fire up the Plex services again.
  10. Profit.

Why does this work? Are there steps here that aren’t necessary? Does this work for me and not for you? I have no idea. Good luck.

2 Likes
34

It worked for me!
Thankyou!!!

1 Like
35

replace ROLLBACK; with COMMIT;

36

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