Latest update broke pms mac on high sierra

Plex Media Server Desktops & Laptops
1

Server Version#: 1:32:2 OR - -
Player Version#: Apple TV latest
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

Got a notification on Apple TV player last night there was a new version of PMS, I said go ahead overnight.

I had also switched off ipv6 last night as I’ve been having the data transfer failed bug that @ChuckPa has been so helpful in trying to eradicate.

Ran fine after switching off last night so I think that’s a red herring; I think the update borked it.

App will try and start (on mac osx high Sierra), appears in taskbar, spins launching and then crashes. Log included below.

Hardware is a hackintosh that’s happily run for over a decade with various updates, and obviously hasn’t been updated in a few years as stable on HS.

Log indicates a database issue. I’ve backed up prefs file and app support folder, Ive re-downloaded the app, done a clean install and then swapped out prefs file (loads fine), and then app support (crashes).

Can anyone tell me what I need to remove to get it to load and rebuild the database; and whether that’ll scupper me for progress through shows/movies?

Thanks pals

————————
CRASH LOG
———————

[0x700000dce000] INFO - Plex Media Server v1.32.1.6999-91e1e2e2c - Apple iMac14,2 x86_64 - build: darwin-x86_64 macos - GMT 01:00
May 10, 2023 00:03:25.232 [0x700000dce000] INFO - MacOSX version: 10.14.6, language: en-GB
May 10, 2023 00:03:25.233 [0x700000dce000] INFO - Processor: 8-core Intel(R) Core™ i7 CPU 860 @ 2.80GHz
May 10, 2023 00:03:25.234 I[0x700000dce000] INFO - Compiler is - Clang 11.0.1 (https://plex.tv b587490162c22e078c314e3f7dc560c691d126aa)
May 10, 2023 00:03:25.234 [0x700000dce000] INFO - /Applications/Plex Media Server.app/Contents/MacOS/Plex Media Server
May 10, 2023 00:03:27.151 [0x700000ed4000] DEBUG - [JobRunner] Job running: “/Applications/Plex Media Server.app/Contents/MacOS/CrashUploader” “–directory=/Users/marked1/Library/Application Support/Plex Media Server/Crash Reports/1.32.1.6999-91e1e2e2c” --version=1.32.1.6999-91e1e2e2c --platform=MacOSX --platformVersion=10.14.6 --serverUuid=bcb1f9e5f328e3b889d36c53fa0a613443878250 --userId=mark.ed@me.com --sentryUrl=https://o17675.ingest.sentry.io/api/1233455/minidump/ --sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx --vendor=Apple --model=x86_64 --device=iMac14,2
May 10, 2023 00:03:27.200 [0x700000ed4000] DEBUG - [JobRunner] Jobs: Starting child process with pid 884
May 10, 2023 00:03:28.060 [0x700000fda000] DEBUG - BPQ: [Idle] → [Starting]
May 10, 2023 00:03:28.069 [0x700000fda000] DEBUG - FeatureManager: Using cached data for features list
May 10, 2023 00:03:28.381 [0x700000fda000] DEBUG - [CERT] Subject name is /CN=.bc3d670a4bc34f25b5bc365e78992fbf.plex.direct
May 10, 2023 00:03:28.382 [0x700000fda000] DEBUG - [CERT] Installed certificate with fingerprint a0:35:4b:e4:03:c7:4e:a4:1b:4b:27:d3:4b:82:48:1c:01:57:61:4e.
May 10, 2023 00:03:28.382 [0x700000fda000] DEBUG - [CERT/OCSP] Stapling requests will be made to ‘http://r3.o.lencr.org/’.
May 10, 2023 00:03:28.384 [0x700000fda000] INFO - [CERT/OCSP] Successfully retrieved response from cache.
May 10, 2023 00:03:28.385 [0x700000fda000] DEBUG - HttpServer: Listening on port 32400.
May 10, 2023 00:03:28.402 [0x700000fda000] DEBUG - HttpServer: Listening on port 32401.
May 10, 2023 00:03:28.402 [0x700000fda000] DEBUG - Running server…
May 10, 2023 00:03:28.402 [0x700001269000] DEBUG - HttpServer: Set up a thread pool with 2 threads.
May 10, 2023 00:03:28.404 [0x700000fda000] DEBUG - Opening 20 database sessions to library (com.plexapp.plugins.library), SQLite 3.39.4, threadsafe=1
May 10, 2023 00:03:28.445 [0x700000fda000] INFO - SQLITE3:(nil), 283, recovered 40 frames from WAL file /Users/marked1/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db-wal
May 10, 2023 00:03:28.687 [0x700000fda000] INFO - Running migrations. (EPG 0)
May 10, 2023 00:03:28.703 [0x700000fda000] DEBUG - Captured session 0.
May 10, 2023 00:03:28.703 [0x700000fda000] DEBUG - Captured session 1.
May 10, 2023 00:03:28.703 [0x700000fda000] DEBUG - Captured session 2.
May 10, 2023 00:03:28.703 [0x700000fda000] DEBUG - Captured session 3.
May 10, 2023 00:03:28.704 [0x700000fda000] DEBUG - Captured session 4.
May 10, 2023 00:03:28.704 [0x700000fda000] DEBUG - Captured session 5.
May 10, 2023 00:03:28.704 [0x700000fda000] DEBUG - Captured session 6.
May 10, 2023 00:03:28.704 [0x700000fda000] DEBUG - Captured session 7.
May 10, 2023 00:03:28.704 [0x700000fda000] DEBUG - Captured session 8.
May 10, 2023 00:03:28.704 [0x700000fda000] DEBUG - Captured session 9.
May 10, 2023 00:03:28.704 [0x700000fda000] DEBUG - Captured session 10.
May 10, 2023 00:03:28.704 [0x700000fda000] DEBUG - Captured session 11.
May 10, 2023 00:03:28.704 [0x700000fda000] DEBUG - Captured session 12.
May 10, 2023 00:03:28.704 [0x700000fda000] DEBUG - Captured session 13.
May 10, 2023 00:03:28.704 [0x700000fda000] DEBUG - Captured session 14.
May 10, 2023 00:03:28.704 [0x700000fda000] DEBUG - Captured session 15.
May 10, 2023 00:03:28.704 [0x700000fda000] DEBUG - Captured session 16.
May 10, 2023 00:03:28.704 [0x700000fda000] DEBUG - Captured session 17.
May 10, 2023 00:03:28.704 [0x700000fda000] DEBUG - Captured session 18.
May 10, 2023 00:03:28.704 [0x700000fda000] DEBUG - Captured session 19.
May 10, 2023 00:03:28.706 [0x700000fda000] DEBUG - Captured session 0.
May 10, 2023 00:03:28.706 [0x700000fda000] DEBUG - Captured session 1.
May 10, 2023 00:03:28.706 [0x700000fda000] DEBUG - Captured session 2.
May 10, 2023 00:03:28.706 [0x700000fda000] DEBUG - Captured session 3.
May 10, 2023 00:03:28.706 [0x700000fda000] DEBUG - Captured session 4.
May 10, 2023 00:03:28.706 [0x700000fda000] DEBUG - Captured session 5.
May 10, 2023 00:03:28.716 [0x700000fda000] DEBUG - Captured session 6.
May 10, 2023 00:03:28.716 [0x700000fda000] DEBUG - Captured session 7.
May 10, 2023 00:03:28.716 [0x700000fda000] DEBUG - Captured session 8.
May 10, 2023 00:03:28.716 [0x700000fda000] DEBUG - Captured session 9.
May 10, 2023 00:03:28.717 [0x700000fda000] DEBUG - Captured session 10.
May 10, 2023 00:03:28.717 [0x700000fda000] DEBUG - Captured session 11.
May 10, 2023 00:03:28.717 [0x700000fda000] DEBUG - Captured session 12.
May 10, 2023 00:03:28.717 [0x700000fda000] DEBUG - Captured session 13.
May 10, 2023 00:03:28.717 [0x700000fda000] DEBUG - Captured session 14.
May 10, 2023 00:03:28.717 [0x700000fda000] DEBUG - Captured session 15.
May 10, 2023 00:03:28.717 [0x700000fda000] DEBUG - Captured session 16.
May 10, 2023 00:03:28.717 [0x700000fda000] DEBUG - Captured session 17.
May 10, 2023 00:03:28.717 [0x700000fda000] DEBUG - Captured session 18.
May 10, 2023 00:03:28.717 [0x700000fda000] DEBUG - Captured session 19.
May 10, 2023 00:03:28.717 [0x700000fda000] INFO - Analyzing database.
May 10, 2023 00:03:46.038 [0x700000fda000] INFO - Vacuuming database.
May 10, 2023 00:04:08.289 [0x700000fda000] ERROR - SQLITE3:(nil), 11, database corruption at line 59420 of [a29f994989]
May 10, 2023 00:04:08.289 [0x700000fda000] ERROR - SQLITE3:(nil), 11, statement aborts at 7: [INSERT INTO vacuum_db.‘fts4_metadata_titles_docsize’ SELECTFROM"main".‘fts4_metadata_titles_docsize’] database disk image is malformed
May 10, 2023 00:04:08.340 [0x700000fda000] ERROR - SQLITE3:(nil), 11, statement aborts at 1: [VACUUM] database disk image is malformed
May 10, 2023 00:04:08.492 [0x700000fda000] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::loadOne: database disk image is malformed
May 10, 2023 00:04:09.191 [0x700000fda000] DEBUG - ChangestampAllocator: initialized to 144147734
May 10, 2023 00:04:09.280 [0x700000fda000] DEBUG - Opening 2 database sessions to library (com.plexapp.plugins.library.blobs), SQLite 3.39.4, threadsafe=1
May 10, 2023 00:04:09.288 [0x700000fda000] INFO - SQLITE3:(nil), 283, recovered 21 frames from WAL file /Users/marked1/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.blobs.db-wal
May 10, 2023 00:04:09.321 [0x700000fda000] INFO - Running migrations. (EPG 0)
May 10, 2023 00:04:09.325 [0x700000fda000] DEBUG - Captured session 0.
May 10, 2023 00:04:09.325 [0x700000fda000] DEBUG - Captured session 1.
May 10, 2023 00:04:10.527 [0x700000c45000] DEBUG - [GPU] Got device: AMD Radeon RX 560, amd@unknown, default true, best true, ID 1000003da, DevID [1002:67ef:1da2:e348], flags 0x1
May 10, 2023 00:04:10.717 [0x700000c45000] DEBUG - Grabber: Cleaning up orphaned grabs.
May 10, 2023 00:04:10.723 [0x700000fda000] DEBUG - Media Provider: Registering provider com.plexapp.plugins.library
May 10, 2023 00:04:10.724 [0x700000cc8000] DEBUG - MyPlex: mapping state set to ‘Unknown’.
May 10, 2023 00:04:10.724 [0x700000fda000] DEBUG - Auth: Refreshing tokens inside the token-based authentication filter.
May 10, 2023 00:04:10.729 [0x700000cc8000] DEBUG - Relay: read 58 cached entries from hosts file
May 10, 2023 00:04:10.741 [0x700000fda000] DEBUG - MyPlex: using cached data for request for https://plex.tv/api/v2/server/access_tokens?auth_token=xxxxxxxxxxxxxxxxxxxx
May 10, 2023 00:04:10.743 [0x700000fda000] DEBUG - MyPlex: updating with 9 access tokens
May 10, 2023 00:04:10.746 [0x700000fda000] DEBUG - MyPlex: using cached data for request for https://plex.tv/api/v2/server/users?auth_token=xxxxxxxxxxxxxxxxxxxx
May 10, 2023 00:04:10.746 [0x700000cc8000] DEBUG - [MediaProviderManager/HCl#1] HTTP requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
May 10, 2023 00:04:10.747 [0x700000fda000] DEBUG - MyPlex: using cached data for request for https://plex.tv/api/v2/server/users/subscriptions?auth_token=xxxxxxxxxxxxxxxxxxxx
May 10, 2023 00:04:10.749 [0x700000fda000] DEBUG - MyPlex: using cached data for request for https://plex.tv/api/v2/server/users/services?auth_token=xxxxxxxxxxxxxxxxxxxx
May 10, 2023 00:04:10.752 [0x7000012ec000] DEBUG - Auth: Refreshing tokens inside the token-based authentication filter.
May 10, 2023 00:04:10.752 [0x7000012ec000] DEBUG - [HCl#2] HTTP requesting GET https://plex.tv/api/v2/server/access_tokens?auth_token=xxxxxxxxxxxxxxxxxxxx
May 10, 2023 00:04:10.753 [0x700000fda000] ERROR - SQLITE3:(nil), 1, no such table: metadata_agent_providers in “update metadata_agent_providers set online = 0”
May 10, 2023 00:04:10.761 [0x700000fda000] ERROR - Error: Unable to set up server: sqlite3_statement_backend::prepare: no such table: metadata_agent_providers for SQL: update metadata_agent_providers set online = 0 (N4soci10soci_errorE)

2

Database corruption.

Run the DB repair utility.

3

Thanks for the tip, sadly repair throws up the following error - without really knowing what I’m doing I’m trying reindex now.

Exporting current databases using timestamp: 2023-05-10_10.46.58
Exporting Main DB
Exporting Blobs DB
Successfully exported the main and blobs databases. Proceeding to import into new databases.
Importing Main DB.
Runtime error near line 847314: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847317: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847318: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847319: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847320: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847339: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847340: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847341: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847343: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847344: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847345: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847346: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847348: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847349: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847350: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847351: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847352: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847353: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847354: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847355: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847356: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847357: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847358: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847359: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847360: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847361: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847376: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847377: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847381: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847382: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847383: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847384: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847385: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847386: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847387: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847388: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847389: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847390: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847391: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847392: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847393: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847394: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847395: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847396: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847397: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847398: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847399: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847400: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847401: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847402: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 847403: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848441: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848442: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848443: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848444: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848445: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848446: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848447: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848448: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848449: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848450: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848451: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848452: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848453: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848563: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848638: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848639: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848672: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848681: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848682: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848689: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848703: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848705: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848707: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848709: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848710: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848711: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848712: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848713: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848715: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848720: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848727: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848728: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848729: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848730: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848731: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848732: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848733: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848734: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848735: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848736: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848737: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848738: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848739: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848740: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848741: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848742: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848743: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848747: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848748: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848749: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848750: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848751: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848752: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Runtime error near line 848753: UNIQUE constraint failed: fts4_metadata_titles_docsize.docid (19)
Error 1 from Plex SQLite while importing from ‘./dbtmp/library.plexapp.sql-2023-05-10_10.46.58’
Cannot continue.

4

I’m not sure this is a simple database corruption issue.

I’m on different architecture (Linux & Docker) but I had this error when trying to start 1.32.1.6999. If I roll back to 1.32.0.6973 (without making any database changes or repairs) Plex starts fine.

There are a few comments on Reddit that others are experiencing this issue so it appears that it might be an issue with the update, rather than an database problem.

5

Bingo bango boss! Rolling back fixed the problem. I did try rolling back, then downloading the latest on offer: 1.32.2.7002-86cfcc10c - and using that but it crashes just the same. So I guess i’ve got to be wary of a few updates for a while.

6

Something similar happened to me upgrading on Debian. Rolling back the package didn’t work, presumably because the DB was already corrupt or migrated in some form.

I restored a DB backup and rolled back the package and that worked, but trying to upgrade again corrupted the DB. Restoring and rolling back fixed it once again.

This is the first time I’ve had an issue with a PMS upgrade over the 5+ years I’ve been using it.

7

Can confirm I have the same issue and rolling back to this version works for me. Upgrading to anything higher right now breaks it again.

8

Have you tried reindexing?

9

I tried a repair, it did not go well.

I ended up having to backup and rebuild multiple times following the official Plex guide, a couple of Reddit posts and eventually, on the third run of ChuckPA’s PlexDBRepair script, managed to rebuild the database.

One thing I did learn during this is that the scheduled backup task hasn’t run since August 2022 so that’s something I’ll be keeping an eye on going forward.

It’s a little strange that everything worked fine rolling back to .6973 and didn’t on .6999 but I’ve solved my problem it seems.

10

Happened to me as well. 1.32 broke Plex in High Sierra.

Dowgrading to 1.31 made the trick.

I hope nobody in the family clicks on Update Plex Media Server. Maybe it’s time to upgrade my old MacMini.

11

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