Page 1 of 1
Backup component
Posted: Wed Sep 30, 2015 5:35 am
by morabanc
I'm testing the backup component, when I try to create a backup nothing happens, this error is appearing in error_log from apache:
PHP Warning: filesize(): stat failed for Error backing up MySQL database 'nagios' - check the password in this script! in /usr/local/nagiosxi/html/includes/components/scheduledbackups/scheduledbackups.inc.php on line 516
I can't check if the password is correct or not, because php file is protected with source guardian.
If I launch the backup script backup_xi.sh it works fine.
Thanks.
Re: Backup component
Posted: Wed Sep 30, 2015 9:16 am
by jdalrymple
The auth info ultimately comes from /usr/local/nagiosxi/html/config.inc.php, but it comes there for backup_xi.sh also I'm pretty sure.
Did you change your auth parameters for either of the databases?
Re: Backup component
Posted: Thu Oct 01, 2015 8:55 am
by morabanc
No, we are using default password
Re: Backup component
Posted: Thu Oct 01, 2015 9:37 am
by lmiltchev
Can you run the following command and show the output?
Code: Select all
grep pwd /usr/local/nagiosxi/html/config.inc.php
Re: Backup component
Posted: Mon Oct 05, 2015 10:58 am
by morabanc
Hello,
Here the output:
grep pwd /usr/local/nagiosxi/html/config.inc.php
"pwd" => 'n@gweb',
"pwd" => 'n@gweb',
"pwd" => 'n@gweb',
Re: Backup component
Posted: Mon Oct 05, 2015 11:09 am
by jolson
If I launch the backup script backup_xi.sh it works fine.
This is the interesting part to me. What version of XI are you running?
Check users and groups:
Code: Select all
grep nag /etc/passwd
grep nag /etc/group
Check sudoers:
Re: Backup component
Posted: Tue Oct 06, 2015 3:29 am
by morabanc
Hi,
I solved it! It was a permissions problem, realated with the own of /store/backups/nagiosxi/ directory, the owner should be nagios, and it was configured with root, after to change this it has worked.
Thanks for your suppport.
Re: Backup component
Posted: Tue Oct 06, 2015 9:23 am
by hsmith
Is there anything else we can do to help you out with this particular issue, or are we all right to mark this one resolved and close it up?