Plex Media Server on Synology won't run

Synology NAS DS1019, DSM Version: 7.2.1-69057
Plex Media Server Version#: 1.29.2.6364-7000
Plex Player Version#: 1.99.0.210-2d92b948

After using Plex Media Server on a Synology NAS DS1019 for 4+ years without any major issues, I’ve been fighting various issues with this for about a week now. My Plex is basically DOWN, as my Plex media server is unreachable. I was initially getting 500 errors, despite the Plex Media Server showing as “running” in Synology. After implementing a port forwarding rule on my Verizon Fios router, and re-installing Plex Media Server AGAIN (this time using the “Claim Code” approach to try to “re-claim” my server, what I now see is that Plex “tries” to run, but then stops.

I pulled the latest Plex Media Server log, and there appear to be references in there to failed database migrations…??

Any guidance would be appreciated, because Plex is effectively dead for me right now, as my server is offline…
Thanks!

Plex Media Server.log (8.7 KB)

Aug 26, 2024 15:42:49.081 [0x7f0e6e1100d0] ERROR - SQLITE3:0x80000001, 1, table sqlite_master may not be modified in "UPDATE sqlite_schema SET sql = replace(sql, 'dt_integer(8)', 'datetime') WHERE name = 'plugins' AND type = 'table'"
Aug 26, 2024 15:42:49.082 [0x7f0e6e1100d0] ERROR - Exception inside transaction (inside=1) (/data/jenkins/server/3537899744/Library/DatabaseMigrations.cpp:289): sqlite3_statement_backend::prepare: table sqlite_master may not be modified for SQL: UPDATE sqlite_schema SET sql = replace(sql, 'dt_integer(8)', 'datetime') WHERE name = 'plugins' AND type = 'table'
Aug 26, 2024 15:42:49.086 [0x7f0e6e1100d0] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::prepare: table sqlite_master may not be modified for SQL: UPDATE sqlite_schema SET sql = replace(sql, 'dt_integer(8)', 'datetime') WHERE name = 'plugins' AND type = 'table'
Aug 26, 2024 15:42:49.300 [0x7f0e6e1100d0] DEBUG - ChangestampAllocator: initialized to 10989410
Aug 26, 2024 15:42:49.311 [0x7f0e6e1100d0] DEBUG - Opening 2 database sessions to library (com.plexapp.plugins.library.blobs), SQLite 3.35.5, threadsafe=1
Aug 26, 2024 15:42:49.318 [0x7f0e6e1100d0] INFO - Running migrations. (EPG 0)
Aug 26, 2024 15:42:49.321 [0x7f0e6e1100d0] DEBUG - Captured session 0.
Aug 26, 2024 15:42:49.321 [0x7f0e6e1100d0] DEBUG - Captured session 1.
Aug 26, 2024 15:42:49.322 [0x7f0e6e1100d0] INFO - Running down migration 202309200919.
Aug 26, 2024 15:42:49.322 [0x7f0e6e1100d0] DEBUG - Captured session 0.
Aug 26, 2024 15:42:49.322 [0x7f0e6e1100d0] DEBUG - Captured session 1.
Aug 26, 2024 15:42:49.322 [0x7f0e6e1100d0] ERROR - SQLITE3:0x80000001, 1, near ">>": syntax error in "UPDATE tags SET extra_data = extra_data ->> 'url' WHERE extra_data IS NOT NULL and json_valid(extra_data)"
Aug 26, 2024 15:42:49.322 [0x7f0e6e1100d0] ERROR - Exception inside transaction (inside=1) (/data/jenkins/server/3537899744/Library/DatabaseMigrations.cpp:289): sqlite3_statement_backend::prepare: near ">>": syntax error for SQL: UPDATE tags SET extra_data = extra_data ->> 'url' WHERE extra_data IS NOT NULL and json_valid(extra_data)
Aug 26, 2024 15:42:49.323 [0x7f0e6e1100d0] ERROR - Exception thrown during migrations, aborting: sqlite3_statement_backend::prepare: near ">>": syntax error for SQL: UPDATE tags SET extra_data = extra_data ->> 'url' WHERE extra_data IS NOT NULL and json_valid(extra_data)
Aug 26, 2024 15:42:49.326 [0x7f0e686aab38] WARN - [GPU] Failed to load PCIID map: Failed to locate a readable PCIID database
Aug 26, 2024 15:42:49.326 [0x7f0e686aab38] DEBUG - [GPU] Got device: , intel@builtin, default true, best true, ID /dev/dri/renderD128, DevID [8086:5a85:8086:7270], flags 0xce
Aug 26, 2024 15:42:49.326 [0x7f0e686aab38] INFO - Preemptively preparing driver icr for GPU 
Aug 26, 2024 15:42:49.353 [0x7f0e686aab38] DEBUG - Grabber: Cleaning up orphaned grabs.
Aug 26, 2024 15:42:49.354 [0x7f0e686aab38] ERROR - Thread: Uncaught exception running async task which was spawned by thread 0x7f0e6e1100d0: std::bad_cast
Aug 26, 2024 15:42:49.354 [0x7f0e686aab38] DEBUG - MyPlex: mapping state set to 'Unknown'.
Aug 26, 2024 15:42:49.354 [0x7f0e6e1100d0] DEBUG - Media Provider: Registering provider com.plexapp.plugins.library
Aug 26, 2024 15:42:49.354 [0x7f0e6e1100d0] DEBUG - Auth: Refreshing tokens inside the token-based authentication filter.
Aug 26, 2024 15:42:49.356 [0x7f0e686aab38] DEBUG - Relay: read 94 cached entries from hosts file
Aug 26, 2024 15:42:49.357 [0x7f0e686aab38] DEBUG - [MediaProviderManager/HCl#1] HTTP requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Aug 26, 2024 15:42:49.357 [0x7f0e6e1100d0] DEBUG - MyPlex: using cached data for request for https://plex.tv/api/v2/server/access_tokens?auth_token=xxxxxxxxxxxxxxxxxxxx
Aug 26, 2024 15:42:49.359 [0x7f0e6e1100d0] DEBUG - MyPlex: updating with 28 access tokens
Aug 26, 2024 15:42:49.360 [0x7f0e6e1100d0] ERROR - Error: Unable to set up server: std::bad_cast (St8bad_cast)

Were you previously running a 1.40 release?

If so, you cannot directly fall back to 1.29.2 due to database changes.

You will need to install the current public or beta release.

If you see any “503 maintenance” messages in Plex Web, wait for the database maintenance to finish. Refresh the web page every 5 - 10 minutes. It will not update automatically.

@FordGuy61 - Thank you so much, that was indeed the issue.

I did upgrade last week, after seeing a new server update was available via the player app…but I didn’t really pay attention to what version it was.

After all the trouble started, in the course of troubleshooting, I have since uninstalled/reinstalled the Plex Media Server (via the Synology NAS interface) multiple times — and I had just assumed that would be grabbing the latest version
But…apparently not? Now that I’m back on 1.40, it’s back up.

Thanks again!

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