D
Dokploy12mo ago
prtik

backup cron issue/bug

I've setup backblaze as s3 storage for backup. So, I've two database replica one for dev/beta test and second for production and i was testing backup and i set cron to run on dev db every 3 minutes and even if i later delete backup tasks its still weirdly running! How do i disable it?!
11 Replies
prtik
prtikOP12mo ago
anyone??
Siumauricio
Siumauricio12mo ago
do you mean even if you delete the backup, the backup is still running?
prtik
prtikOP12mo ago
Yess! i had to stop the ccontainer, but i don't want to leave zombie cron job to lingered around.. how can i delete that specific cron job if this happens again or even want to remove the current one which still causing issue..
Siumauricio
Siumauricio12mo ago
I tried to replicate but nothing seems wrong, can you provide step by step to reproduce this issue?
prtik
prtikOP12mo ago
1. Create 2 mariadb databases 2. Setup backblaze bucket storage 3. Setup backup job on both db and define prefix path for 1st db - db/ and 2nd db - dev/ and add cron - */3 * * * [every 3 min] 4. check if db are backing up. 5. now delete any of the db's backup job Hopefully you'll see that backup still runs every 3 min, unless you stop that database container!
Siumauricio
Siumauricio12mo ago
Ok i didn't try if the database is not running 😁 maybe that's the issue I will try, thanks
prtik
prtikOP12mo ago
Sure. 😃
Siumauricio
Siumauricio12mo ago
I tried but nothing seems wrong, i deleted the dev backup and it was removed it sucessfully you can see in the image
No description
prtik
prtikOP12mo ago
Did you check bucket after deleting backup? if its generating backups?
Podgorski
Podgorski11mo ago
@prtik I am facing the same situation with my Postgres database. I even removed the backup, but it continues to run every 10 minutes. Did you manage to solve it?
prtik
prtikOP10mo ago
Hello @Podgorski sorry for delayed response, unfortunately i didn't find cause that time and due to limited access to dokploy support i couldn't able to open a proper ticket to inform it also, as @Siumauricio couldn't able to replicate this im suspecting it's a very very specific bug and happening in specific conditions only and for few instances.. So what i did back then, since i had backup i completely removed the service and created new one, that way the docker container from which un-controllable mysql dump was executing was stoped and i setup new backup. I hope this helps you any way...

Did you find this page helpful?