@ChuckPa can you open a PM with me so I can share full logs?
The pattern I see is when it’s looking at DatabaseFixups PlayQueue and converting to the file path.
Either a pointer to a no-longer-present file (need scan-fresh)
or there is minor database damage.
I’d go with Scan/Fresh of all library sections first
then consider running a DBRepair in case there are some flaky records.
HI @ChuckPa
I try to scan all my librairies and executre DBRepair. But today i have the same issues.
I cannot play anything on the server and my friends having issue to play something to.
Plex log say a lot of : [Req#4d4e] Waited over 10 seconds for a busy database; giving up.
Here is the output of DBRepair and the PMS logs.
PlexDBRepair_log.txt (3.6 KB)
Plex Media Server Logs_2023-06-01_06-43-36.zip (3.0 MB)
Have always the same issues. Plex crash everytime and i don’t know why…
Here is the logs after many attempts to restart PMS manually …
I see a lot of error : Waited over 10 seconds for a busy database; giving up. in the console
I have run DBrepair another time berfore the restart of PMS but DBrepair say the DB is fine
Plex Media Server Logs_2023-06-07_08-53-17.zip (558.3 KB)
Just started a fresh new server, and i have the same issues 
new server is Ubuntu 22.04 Latest LTS, plex is on docker version is : 1.32.5.7349
so well it’s more or less related to plex being very slow since some version ==> Adding metadata via API takes way too long with recent Plex server versions
during the scan i can’t do anything, not even allow the intro/outro detection, i need to have them set as scheduled task only…
running PMM or plextraktsync makes then timeout after a few, and crash… plex database has always been an issue, but it’s becoming worse and worse.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
