Server Version#: v.1.41.8.9834-071366d65
Player Version#: N/A
I’m getting the dreaded “Sqlite3: Sleeping for 200ms to retry busy DB.” message over and over and over again to the point where PMS isn’t even usable.
I’m running PMS as a docker container within Unraid. Docker and all the non-media files are run off a NVME SSD, so it’s definitely not a hard drive speed issue. I tried repairing it with the tool by ChuckPA and it didn’t accomplish anything.
I know it’s not a server issue or that the db is excessively large. I spun up an Emby instance last night, it was able to index the entire library overnight and everything works perfectly when I tried it this morning.
I tried restarting PMS many times yesterday to no avail. I’m just seeing the Sqlite3 error message over and over and over again.
I’ve attached my server logs that are set to debug
It looks like it’s 182 MB. I don’t even get what it’s trying to read / write though. I didn’t see anything running in the background when I saw the Sqlite busy messages.
I have it running on Unraid using the official Plex docker image.
I’ve attached some pictures of the CPU usage. There are times where a single core would spike, but only really for a second. The second picture is a representation of what the “typical” state would be.
I don’t know how relevant it is, but Unraid is running as a VM on ESXi. The video card is passed through directly to Unraid. 48 of the 64 threads were assigned to the Unraid VM with 64 GB of ECC RAM.
Is the EPG data update super database intensive? I see that it’s downloading ~20,700 airings. I usually have that done only at 3 AM so it doesn’t interrupt anything, but for some reason, it’s been updating for quite a long time now.