Backupxi failed -"Scheduled Local Backup Failed"

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Post Reply
igae1
Posts: 40
Joined: Thu May 25, 2017 6:35 am

Backupxi failed -"Scheduled Local Backup Failed"

Post by igae1 »

Hi,
We have recived the following notification:
"Scheduled Local Backup Failed, Last output from the system: Error backing up MySQL database 'nagios' - check the password in this script!"
We have checked that the password in this script is correct, because is the password of the configuration file /usr/local/nagiosxi/etc/xi-sys.cfg
We have sucesfully connected to the mysql database nagios with the user and passw0rd stored in configuration file /usr/local/nagiosxi/etc/xi-sys.cfg
This is the backup daily of mysql nagios:

MySQL dump 10.14 Distrib 5.5.68-MariaDB, for Linux (x86_64)
--
-- Host: localhost Database: nagios
-- ------------------------------------------------------
-- Server version 5.5.68-MariaDB

/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;
/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;
/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;
/*!40101 SET NAMES utf8 */;
/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;
/*!40103 SET TIME_ZONE='+00:00' */;
/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;
/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;
/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;
/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;

--
-- Current Database: `nagios`
--

CREATE DATABASE /*!32312 IF NOT EXISTS*/ `nagios` /*!40100 DEFAULT CHARACTER SET utf8 */;

USE `nagios`;



Tnaks
igae1
Posts: 40
Joined: Thu May 25, 2017 6:35 am

Re: Backupxi failed -"Scheduled Local Backup Failed"

Post by igae1 »

Hi,
backup keeps failing
Thanks
igae1
Posts: 40
Joined: Thu May 25, 2017 6:35 am

Re: Backupxi failed -"Scheduled Local Backup Failed"

Post by igae1 »

This issue is already solved.

We have run a restore database job yesterday and it worked today.
Post Reply