Sqlite3 error since the latest updates on podman/docker

Hey,

I am running Plex within a rootless podman container and I use the linuxserver.io docker container. I also have plexdrive and rclone as the storage backend for my media and I use a tmpfs for the transcoder directory + an NVMe RAID1 array serves the database.

It has been working all fine with the same setup for years. However everything broke since the latest updates around the beginning of summer or so. Since the new updates with the media library now if I run a media scan, plex starts scanning the folders just fine, but especially if a lot of new content is added to a folder, Plex seemingly never stops scanning the library and I keep seeing the following line in the logs:

Sqlite3: Sleeping for 200ms to retry busy DB.

Then I cannot stop the scanning anymore, the intro detection is seemingly hung forever too. New playback sessions also cannot be started since the db is busy. I can however browse my media library just fine though (I assume SELECT works even when the db is locked).

If I stop the container at this point, it leaves a zombie/defunct process that’s impossible to kill since it has a few files open. Only a reboot/unmount of the partition works to get rid of that. I have explained this situation a little more here: https://github.com/linuxserver/docker-plex/issues/281

I can provide any logs if needed, but please suggest me a fix because now I have Plex Pass for nothing. Plex in its current state is just impossible to use for me and I am thinking about looking for an alternative already even though I love Plex. :relaxed:

Thanks

Server Version#: 1.24.2.4973
Player Version#:-

Seemingly this issue always occurs while intro detection is on. Otherwise there are no database locks. Please take a look at it.

I take it back, it happens all the time. Even if I do a scan on an “other videos” container with only 11 new videos in it. The server is frozen seemingly stuck with sql queries and nothing can kill it.

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