Plex and Mojave issues

Server Version#: 1.16.6.1592
Player Version#:

I’ve been using Plex for an absolute age without any issues at all but after ‘upgrading’ to Mojave on my Mac a few days ago i’ve started having issues - the last two movie files i put in my movie folder wouldn’t show up at all, despite attempts and chahing file names / paths then I noticed that when I deleted what was already in the movie folder, it wouldn’t leave Plex itself (obvs couldn’t play the files any longer) - i’ve tried refreshing metadata etc but to no avail… any helpers out there?

Without addressing OS update side effects if any, as we don’t have debug logs yet,
let’s have you set those paths back to what they’ve always been working, then
you can try each of these steps in succession, allowing each step to finish completely
before you start the next.

  • Use Finder to move the two films out of where plex looks. Put 'em in Downloads for now.
  • In a Plex player click on your Home then More > which is at the bottom of the left column below your libraries
  • Clicking More > brings you to the Pinned screen where you click the vertical ••• for More Options next to the name of your PMS server. (there’s a + and a •••)
  • From that menu, choose and let each step complete before the next:
    1 - Empty Trash
    2 - Clean Bundles
    3 - Optimize Database
  • Use Finder to move the films back into your Library.
  • Then Scan Library Files from the same server ••• menu you used above.

Let us know if it find the films correctly. If not, get us debug Log Files that you zip and attach.

thanks for the swift respone - however, embarrassingly - i can’t seem to find the More that you speak of. I’m looking at my Plex now, but on the left hand column, on my home screen, underneath libraries there is only the standard ‘playlists - tv programmes’, just ‘online content’ beneath that…

sorry - just saw your mention of vertical dots… doh.

Plex Media Server Logs_2019-09-22_09-17-21.zip (2.8 MB)

Great thanks. It’s a little roundabout trying to find that “More” menu, but it’s the best menu because it operates on the all libraries, and it’s the only place you’ll find the Empty Trash

The steps I listed above are called The Plex Dance. It’s how you get Plex to scan items again from scratch like it never saw them.

I’ll have a look at the logs.

EDIT:

Okay so it looks like database corruption errors from SQLITE3 that fill your log.
Click the triangle to expand the list.

in "Plex Media Server.log"
Sep 22, 2019 09:16:40.162 [0x7000008e9000] DEBUG - Updating metadata item (save) (original2.MOV00234) with ID 6198186
Sep 22, 2019 09:16:40.177 [0x7000008e9000] ERROR - SQLITE3:0x10d29afb0, 11, database corruption at line 79051 of [bf8c1b2b7a]
Sep 22, 2019 09:16:40.177 [0x7000008e9000] ERROR - SQLITE3:0x10d29afb0, 11, statement aborts at 11: [SELECT idx, start_block, leaves_end_block, end_block, root FROM 'main'.'fts4_metadata_titles_segdir' WHERE level = ? ORDER BY idx ASC] database disk image is malformed
Sep 22, 2019 09:16:40.177 [0x7000008e9000] ERROR - Failed to commit transaction (../Library/MetadataItem.cpp:961) (tries=1): Cannot commit transaction. database disk image is malformed
Sep 22, 2019 09:16:40.608 [0x7000008e9000] ERROR - SQLITE3:0x10d29afb0, 1, statement aborts at 1: [COMMIT] cannot commit - no transaction is active
Sep 22, 2019 09:16:40.609 [0x7000008e9000] ERROR - Failed to commit transaction (../Library/MetadataItem.cpp:961) (tries=2): Cannot commit transaction. cannot commit - no transaction is active
Sep 22, 2019 09:16:41.471 [0x7000008e9000] ERROR - SQLITE3:0x10d29afb0, 1, statement aborts at 1: [COMMIT] cannot commit - no transaction is active

Sep 22, 2019 09:16:46.291 [0x7000008e9000] ERROR - SQLITE3:0x10d29afb0, 1, statement aborts at 1: [ROLLBACK] cannot rollback - no transaction is active
Sep 22, 2019 09:16:46.291 [0x7000008e9000] ERROR - Failed to roll back transaction (../Library/MetadataItem.cpp:959): Cannot rollback transaction. cannot rollback - no transaction is active
Sep 22, 2019 09:16:46.291 [0x7000008e9000] ERROR - Exception analyzing media file '/Users/jayrobinson/Pictures/iPhoto Library.photolibrary/Masters/2004/Photos Clubbing/original2.MOV00234.MPG' (Cannot commit transaction. cannot commit - no transaction is active)
Sep 22, 2019 09:16:46.320 [0x7000008e9000] ERROR - SQLITE3:0x10d29afb0, 11, database corruption at line 79051 of [bf8c1b2b7a]

Sep 22, 2019 09:16:52.398 [0x7000008e9000] ERROR - SQLITE3:0x10d29afb0, 1, statement aborts at 1: [COMMIT] cannot commit - no transaction is active
Sep 22, 2019 09:16:52.398 [0x7000008e9000] ERROR - Failed to commit transaction (../Library/MetadataItem.cpp:961) (tries=10): Cannot commit transaction. cannot commit - no transaction is active
Sep 22, 2019 09:16:52.398 [0x7000008e9000] ERROR - Exception inside transaction (inside=1) (../Library/MetadataItem.cpp:961): Cannot commit transaction. cannot commit - no transaction is active
Sep 22, 2019 09:16:52.398 [0x7000008e9000] ERROR - SQLITE3:0x10d29afb0, 1, statement aborts at 1: [ROLLBACK] cannot rollback - no transaction is active
Sep 22, 2019 09:16:52.398 [0x7000008e9000] ERROR - Failed to roll back transaction (../Library/MetadataItem.cpp:959): Cannot rollback transaction. cannot rollback - no transaction is active
Sep 22, 2019 09:16:52.399 [0x7000008e9000] ERROR - Thread: Uncaught exception running async task which was spawned by thread 0x700000348000: Cannot commit transaction. cannot commit - no transaction is active
Sep 22, 2019 09:16:52.411 [0x700000f0d000] ERROR - SQLITE3:0x10d29afb0, 11, database corruption at line 79051 of [bf8c1b2b7a]
Sep 22, 2019 09:16:52.411 [0x700000f0d000] ERROR - SQLITE3:0x10d29afb0, 11, statement aborts at 11: [SELECT idx, start_block, leaves_end_block, end_block, root FROM 'main'.'fts4_metadata_titles_segdir' WHERE level = ? ORDER BY idx ASC] database disk image is malformed
Sep 22, 2019 09:16:52.411 [0x700000f0d000] ERROR - Failed to commit transaction (../Library/MetadataItemClustering.cpp:114) (tries=1): Cannot commit transaction. database disk image is malformed

You next goal is to follow the steps listed in Repair A Corrupt Database.
It’s reasonably safe because you’ll be repairing a copy of the current DB,
then moving that into place later in the steps.

Let us know how it goes.

ok brilliant - deleting the com.plexapp.plugins.library.db file seems to have sorted it… ta very much!

1 Like

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