MySQL handler wrongly reports SUCCESS
Hi,
We had to use a backup of a database today, and to our horror discovered that they where old! We check our backupninja mails daily to make sure no server backup failes.
But the mysql handler wrongly reports SUCCESS, here where our case:
Debug: check_perms /etc/backup.d Debug: perms: drwxrwx--- Debug: gperm: rwx Debug: wperm: --- Debug: check_perms /etc/backup.d/20.mysql Debug: perms: -rw------- Debug: gperm: --- Debug: wperm: --- Info: >>>> starting action /etc/backup.d/20.mysql (because of --now) Debug: yes Debug: mv /root/.my.cnf /root/my.cnf.disable Info: Initializing SQL dump method /usr/bin/mysql: Can't read dir of '/etc/mysql/conf.d/' (Errcode: 2) Fatal error in defaults handling. Program aborted ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) Debug: rm /root/.my.cnf Debug: mv /root/my.cnf.disable /root/.my.cnf Info: <<<< finished action /etc/backup.d/20.mysql: SUCCESS Debug: send report to root Info: FINISHED: 1 actions run. 0 fatal. 0 error. 0 warning.
Even though the mysql client reports login error (because of missing dir! argh) the ninja report is SUCCESS :(
(from redmine: created on 2010-08-02, closed on 2010-08-06)