added a z and see if this works
PlexLogs.tar (780.5 KB)
Do you have database backup files in the Databases directory?
What you have as current is damaged
Mar 22, 2025 20:56:18.860 [0x7f5e77b17ad0] 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)
Mar 22, 2025 20:56:18.906 [0x7f5e77b17ad0] INFO - SQLITE3:0x80000001, 283, recovered 4 frames from WAL file /share/CACHEDEV1_DATA/.qpkg/PlexMediaServer/Library/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.blobs.db-wal
Mar 22, 2025 20:56:18.909 [0x7f5e77b17ad0] INFO - Running migrations. (EPG 0)
Mar 22, 2025 20:56:18.911 [0x7f5e77b17ad0] INFO - Running down migration 202309200919.
Mar 22, 2025 20:56:18.911 [0x7f5e77b17ad0] 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)"
Mar 22, 2025 20:56:18.911 [0x7f5e77b17ad0] ERROR - Exception inside transaction (inside=1) (/data/jenkins/server/3520991443/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)
Mar 22, 2025 20:56:18.911 [0x7f5e77b17ad0] 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)
Mar 22, 2025 20:56:18.928 [0x7f5e729f4b38] ERROR - Thread: Uncaught exception running async task which was spawned by thread 0x7f5e77b17ad0: std::bad_cast
Mar 22, 2025 20:56:18.930 [0x7f5e72eb2b38] INFO - Preemptively preparing driver icr for GPU JasperLake [UHD Graphics]
Mar 22, 2025 20:56:18.930 [0x7f5e72eb2b38] INFO - [DriverDL/icr] Obtaining driver
You can put my DBRepair.sh tool in /share/Public and run it as ‘root’ user.
It’ll help you find a good DB to use from the backups you have (it checks)
Info in the README.md
Good to know and to answer your question, Do you have database backup files in the Databases directory? - Don’t know
I will run the tool and see what I can do. Ran fine on the Pi as of this afternoon. I shut it down once I migrated the PMS data off.
Thank you
You don’t show using Replace (to use a DB backup)
Don’t you have any ?
I wasn’t sure based off the guide, so I started with the auto. As it said the DB’s were good I wasn’t sure if I should go to the replace still. I have a few backups listed and one external from January (full PMS directory).
I used the most current backup and no go. I then tried the next backup and no luck and went down the line, No luck getting it to work with any of the four listed in the tool. I haven’t done anything yet with the external backup I have.
One question I have as since the old Pi host was operational (still is as far as I know), can we repair it there and export and import?
I powered the Pi Plex device back up and the old instance is up and running fine. (Family is having withdrawal reactions).
Ok, I repaired the DB on the Pi and optimized. Cleaned up the directories on the QNAP and started the export/import process from scratch. Old Pi host is offline and I reclaimed the server and it started on the QNAP.
Not sure what happened but after much trial and error all seems to be good at this point.
Things have been running super and just wanted to say thanks again for all the guidance and support. I know you must be very busy and have limited time, but really do appreciate all you did to help me learn complete this.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
