dear plex am having this issue where i get error “Sqlite3: Sleeping for 200ms to retry” when attempting to scan my library, am using a combination of linux (ubuntu)/docker, docker compose, rclone, mergerfs, and gdrive. according to the internet there is a fix or workout to this but am getting stuck trying to apply it, please i need help.
more info about this:
https://www.reddit.com/r/PleX/comments/ic3cjr/anyone_try_giving_sqlite3_more_cache_to_help/
part where am getting stuck:
You appear to be trying to launch Plex’s SQLite interpreter by using the bash variable ${sqplex}. Your terminal doesn’t know what that variable means, so it thinks you’re trying to run an empty command. I searched the threads you linked for sqplex and found nothing, so I have no way of knowing how it was meant to work. This is why it isn’t working for you. You should instead try running the command via the actual SQLite interpreter. I am not sure where that is located on a Docker install, perhaps someone else can help with that.
thank you for your reply, those links i posted are in relevance to a fix/workaround to my issue or at least that is what am hoping and yes hopefully somebody can help me.
In the following Plex article, we can see how to locate the Plex Sqlite tool
The command you typed into your terminal that failed was supposed to be adjusted based on the above location.
"${sqplex}"
is supposed to be replaced with
"/usr/lib/plexmediaserver/Plex SQLite"
It looks like what @nibbles said, you aren’t using the correct executable.
Since this looks to be in a docker image, be sure you are running this command from within that image. For example “docker exec -it ”
Then make sure you are running “sqlite3 com.plexapp.plugins.library.db” on the files you are trying to change this page file. Your command here looks like you are trying to also vacuum the DB and other SQL maintenance tasks. Plex’s version of SQLite is custom and it’s recommended you use their executable to make changes.
Lastly, this fix only helps if you are running the Plex DB from a HDD or slower SSD.
If you are running on anything recent or NVMe (or even a RAM drive) you won’t see much of a benefit, but I keep it since my server has lots of RAM that I don’t mind be being used for this purpose.
Follow the commands exactly, but from within the docker image and this should work just fine. A successful output is just a new line, then you Ctrl + D to exit SQLite
ok thank u, i was able to it with the help of somebody, i believe sqlite3 need to be install to be able to run those commands
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
