Unraid Plex crashing with “Sqlite3: Sleeping for 200ms to retry busy DB.”

Plex Media Server NAS & Devices
1

Hi all, I am running unraid with Plex running in docker using the linuxserver district.

It works fine for a while and then crashes with the log showing:

**Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Sqlite3: Sleeping for 200ms to retry busy DB.
Got SIGTERM, quitting.
Leaving mDNS multicast group on interface virbr0.IPv4 with address 192.168.122.1.
Leaving mDNS multicast group on interface docker0.IPv4 with address 172.17.0.1.
Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.1.109.
avahi-daemon 0.6.32-rc exiting.
Sqlite3: Sleepin[cont-finish.d] executing container finish scripts…
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
Critical: libusb_init failed

[s6-finish] sending all processes the KILL signal and exiting.

[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] 10-adduser: executing…
usermod: no changes
**

Can anyone help?

2

I had this same issue
TLDR: ran an optimize Database and that fixed the issue.

I had tried a reboot of the whole system, restarting plex, moving the DB to another location. Nothing seemed to fix it until I ran an optimize database. It took it overnight to finish (or it finished sometime during the night, but it worked.

3

Generally the database is optimized overnight every few days by scheduled tasks; if it’s not for some reason, it can indeed help to optimize manually.