I have been running ImageMaid for quite some time without issue, however the last 2 days I have noticed the script never finishes. When I check my Plex dashboard I see "Backing up database" and it just spins and spins. I have not made any recent changes to my environment so I am not sure why it has suddenly stopped working.
#ImageMaid Database backup task
dusk relic
livid beaconBOT
Welcome @dusk relic!
Someone from <@&938443185347244033> will assist when they're available.
Including meta.log from the beginning is a huge help. Type !logs for more information.
After attaching your log, do not forget to hit the green check boxes when prompted by our bot.
You can press the "Close Post" button above or type /close at any time to close this post.
livid beaconBOT
You can press the "Close Post" button above or type `/close` at any time to clos...
dusk relic
It seems the backup task that ImageMaid triggers is eating away at my disk space and when I kill the container the space doesn’t come back. Where is this DB backup getting stored?
glossy jetty
If you are requesting a copy of the database from Plex, then all that interim stuff is internal to Plex. Image maid stores the copy it receives in its config directory and only hangs on to one at a time.
If Plex is unable to complete the database backup, then there's something going wrong inside Plex outside of Imagemaid's control.
dusk relic
I wonder what has changed that it’s failing to download the copy correctly
glossy jetty
If it's inside Plex, then perhaps database problems?
Imagemaid just says to Plex "hey can you send me a copy of your database?" and from that point until Kometa receives the download, it's all inside Plex.
dusk relic
I just ran the chuckpa database repair just in case, but I’m still having the same problem
Maybe something has changed with the Plex image
glossy jetty
If possible you might want to try the direct copy method instead of downloading it from Plex.
dusk relic
Is there a preferred method? I could look at the docs to see how to set that up.
glossy jetty
There's the two methods, and it's up to you as far as which you prefer. Neither has any advantage as far as Imagemaid is concerned; it jsut needs a copy of the database, and you can either ask Plex for a copy via the network OR make a direct copy from the plex metadata folder.
For the direct copy, Imagemaid will need access to the Plex metadata folder.
dusk relic
I am going to post some logs from when it stopped working when I get home.
Too hard to troubleshoot remotely 😂
glossy jetty
The first two logs are timeouts where Plex just doesn't respond in time. Nothing IM can do about that.
[2025-05-19 06:40:03,262] [imagemaid.py:443] [CRITICAL] | HTTPConnectionPool(host='10.0.1.100', port=32400): Read timed out. (read timeout=600)
[2025-05-20 06:40:10,830] [imagemaid.py:443] [CRITICAL] | HTTPConnectionPool(host='10.0.1.100', port=32400): Read timed out. (read timeout=600)
The last log shows an internal error from inside Plex:
[ERROR] | Metadata Error: Database Download Failed Try Using Local Copy: (500) internal_server_error; (redacted)/diagnostics/databases <html><head><title>Internal Server Error</title></head><body><h1>500 Internal Server Error</h1></body></html> |
Imagemaid has said "Hey Plex give me a copy of your database" and in the process of creating that copy something exploded inside Plex. This also isn't anything that IM can address or affect.
A 500 error means "Something terrible has happened inside the server that no developer foresaw and no tester ever encountered, so no sensible error handling is in place. Instead, all I can do is tell you that something terrible has happened and abort whatever I am doing"
It seems like perhaps your Plex database is very large so the direct-copy method might be best.
Also, are you really uploading enough art that IM has anything significant to do on a daily basis?
dusk relic
No. I was only using it to empty the phototranscoder folder daily
glossy jetty
I'd do that with a cron job instead. I have this running:
*/10 * * * * bash /opt/scripts/pt-cleanup.sh >> /opt/scripts/pt-cleanup.log 2>&1
Where /opt/scripts/pt-cleanup.sh:
#!/bin/bash
# clear out phototranscoder dirs
rm -fr /opt/plex/Library/Application\ Support/Plex\ Media\ Server/Cache/PhotoTranscoder/*
No need to spin up IM just for that.
especially no need for a copy of the database for that.
dusk relic
sweet! I will look into setting that up instead
dusk relic
Okay tracked down what happened. There was a recent change in plex that caused massive growth in the DB
(Statistics) The fix for Bandwidth reporting was reverted as it was causing massive database growth
made my DB go from 750MB to like 13GB
restored a backup and everything is working properly
gritty coralBOT
antwanchild used !aenh
@dusk relic, anything else needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.