#Sqlite3: Sleeping for 200ms to retry busy DB
1 messages ยท Page 1 of 1 (latest)
You can press the "Close Post" button above or type /close at any time to close this post.
I ran a search for previous topics but didn't find much information. It looks like my library may be a little too large and when PMM runs the PlexDB can't handle the amount of operations? Looking for advice on how to better optimize my PMM script so stuff doesn't lock up. I'm running the latest version of PMM and Plex. PMM is set to run at 8:00am.
๐ Great! Let's start to review and make recommendations, rcalorie... ๐
๐ If you want to review this again, rcalorie:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> ๐
Using Asset Directory: config/assets
Connected to server rahul-server version 1.32.7.7621-871adbd44
Running on Linux version 6.1.36-Unraid
Plex DB cache setting: 40 MB
PlexPass: True on Public update channel.
Scheduled maintenance running between 2:00 and 5:00
Connected to library Movies
Type: Movie
Agent: tv.plex.agents.movie
Scanner: Plex Movie
Ratings Source: Rotten Tomatoes
Movies Library Connection Successful
To be clear, I've been facing this issue for the last few months, and on previous versions of PMM/Plex. I turned off PMM for a while but recently havce been doing some cleanup and wanted to reenable it.
under Plex settings in config.yml, db_cache: 1024
Replace/remove legacy yml items
Drop down to 1.32.6 for Plex version
Run nightly version of PMM
Those are the 4 things I would start with
Thanks I'll work on that