Have you checked your database integrity? Otherwise a copy of your server logs are needed right after the restart along with a file that isnt populating metadata. Similar issues have been flapping network connections.
Thanks for continuing to look into this. So I just added the ‘Rebirth’ version of the famous dinosaur series and Plex could find no metadata and upon clicking ‘match’ it finds no options. The first timestamped Logs are taken immediately after this.
Then I stopped and restarted Plex and it was able to match the file and attach all relevant metadata. The second timestamped Logs are taken immediately after this.
I thought comparing the two may prove more helpful? They are only 2 minutes apart.
Thanks again.
Plex Media Server Logs_2025-08-05_10-40-20.zip (2.0 MB)
Plex Media Server Logs_2025-08-05_10-42-24.zip (1.8 MB)
I’m seeing where PMS is giving up doing its tasks because it’s waited too long for the DB.
Aug 05, 2025 08:03:13.737 [139925779061560] ERROR - [MediaProviderManager/MetadataAgentManager] Waited over 10 seconds for a busy database; giving up.
Aug 05, 2025 08:03:13.737 [139925779061560] ERROR - Thread: Uncaught exception running async task which was spawned by thread 139925893483320: std::exception
Given this is happening immediately after startup, while only a dual-core CPU, the DS220+ should be able to power through that startup.
The most common cause here is fragmented database
The first step is to optimize the database in a way PMS can’t. (‘auto’ option)
The request was to HPIiyama, but I also did this on my side and all seems ok
Checking the PMS databases
Check complete. PMS main database is OK.
Check complete. PMS blobs database is OK.
Did you complete the entire optimization (which removes dead records from the DB) or did you just check it?
I had only checked but just did the automatic command.
and all seems good,
Automatic Check,Repair,Index started.
Checking the PMS databases
Check complete. PMS main database is OK.
Check complete. PMS blobs database is OK.Exporting current databases using timestamp: 2025-08-07_20.04.54
Exporting Main DB
Exporting Blobs DB
Successfully exported the main and blobs databases.
Start importing into new databases.
Importing Main DB.
Importing Blobs DB.
Successfully imported databases.
Verifying databases integrity after importing.
Verification complete. PMS main database is OK.
Verification complete. PMS blobs database is OK.
Saving current databases with ‘-BACKUP-2025-08-07_20.04.54’
Making repaired databases active
Repair complete. Please check your library settings and contents for completeness.
Recommend: Scan Files and Refresh all metadata for each library section.Backing up of databases
Backup current databases with ‘-BACKUP-2025-08-07_20.06.15’ timestamp.
Reindexing main database
Reindexing main database successful.
Reindexing blobs database
Reindexing blobs database successful.
Reindex complete.
Automatic Check, Repair/optimize, & Index successful.
The good news is the latest server update has fixed the issue. Must have been a bug in the last two releases. Hopefully downloading the latest server update will fix for everyone.
Thanks for all the input.
Hi - issue now fixed thanks to today’s Plex server update release. Thank you for your efforts though.
Please could you do me a favour and remove my old user name from your post? Appreciate it.
