Failed Backup should stop

Community Support Backups
1

Hi,
I changed the root password for MySQL and also updated it in /usr/local/hestia/conf/mysql.conf
and /root/.my.cnf. It has the correct rights, but now, backups fail and they loop endlessly.
A safeguard should be put in place to avoid the loops as they fill the hard drives trying over and over again, with the same problems.

Messages like:
2025-12-07 22:11:23 dbname (mysql)
Error: mysql config parsing failed

And it starts over, creating infinite /backup/tmp.NNNN files filling up the disk.

Hopefully it will be implemented in a future version.

2

Hi,

I’m trying to reproduce the issue and I can’t. :frowning: Did you remove any database manually or do anything else that could help me figure out how to reproduce the problem?

3

HI,
I actually had a mixed mess from the DB created via HestiaCP and then tinkered with by PHPMyAdmin. Ended up dropping it from PHPMyAdmin but I finally found the reference in /usr/local/hestia/data/users/[username]/db.conf and deleted the line.
Had to restart hestiacp and then the backup was fine.
So if you want to test, just add any random non-existing DB into that file and start a backup. You will see that it stops on that ghost DB and starts over.

4

Ok, thanks, I’ll take a look.