Database locking up PMS

Server Version#: 1.32.7.7328

Hello everyone,

after scanning a few new movies my PMS starts to stall and becomes unresponsive. In the activity tracker (?) it showing that it scans the new movie, but the bar never completely fills up. In the attached logs it probably starts at:

Jul 24, 2023 04:03:24.588 [4252] DEBUG - Added new metadata item (Amityville II: The Possession) with ID 37314

The cause for the problem seems to be the database

ERROR - Waited over 10 seconds for a busy database; giving up.

Sadly I can’t figure out why that is happening. I already tried repairing the DB with Plex and the repair DB script. The only way to get the server to run again is to kill all plex processes in the taskmanager and start the PMS up again.

Any help will be appreciated, thanks in advance!

Plex Media Server.1 - Copy.zip (603.7 KB)

I had a similar problems for months and finally I found out one disk (with media) was giving reading errors. So it was all a hardware problem.

How did you find the error? I’m going to start some disk scans, but those will take a few hours/days. Any shortcuts?

I use TrueNAS and I was reading the operating system log files and found the read errors. I do not know if this is your case, but what you described looks suspiciously too similar to my situation. Plex became unresponsive, the log files said issues about DB being blocked and sometimes something about a thread blocking the DB with a thread counter, if I refreshed the client the thread counter would increase by one. And restarting Plex would bring everything back to normal until the whole thing happened again. which can be in one hour or several days. I was literally months suffering with that problem. And to make things worse, the read errors were not really due to the harddisk itself, but a bad cable. I replaced the harddisk and it continued happening. Then I replace all cables and it stopped.

I actually found a few unreadable blocks on a hard drive and exchanged that one, so thanks for that. But sadly the problem still exists. :frowning:

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