Upgrade from 2024R1.0.1 to 2024R1.1.1 fails

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Post Reply
olabisid
Posts: 14
Joined: Fri Apr 19, 2019 10:50 am

Upgrade from 2024R1.0.1 to 2024R1.1.1 fails

Post by olabisid »

I tried both manual (from command prompt) and GUI and both fail.

command prompt failed because I was prompted for a password and it says password is incorrect.

GUI failed with log below:
---- Starting Nagios XI Backup ----
\nStarting new backup....\n
Backing up Nagios Core...
tar: Removing leading `/' from member names
tar: /usr/local/nagios/var/rw/nagios.qh: socket ignored
Backing up Nagios XI...
tar: Removing leading `/' from member names
Backing up MRTG...
tar: Removing leading `/' from member names
Backing up the SNMP directories
tar: Removing leading `/' from member names
tar: Removing leading `/' from member names
Backing up NRDP...
tar: Removing leading `/' from member names
Backing up Nagvis...
tar: Removing leading `/' from member names
Backing up nagios user home dir...
tar: Removing leading `/' from member names
Backing up MySQL databases...
mysqldump: [Warning] Using a password on the command line interface can be insecure.
mysqldump: Error: 'Access denied; you need (at least one of) the PROCESS privilege(s) for this operation' when trying to dump tablespaces
mysqldump: Error 1194: Table 'nagios_systemcommands' is marked as crashed and should be repaired when dumping table `nagios_systemcommands` at row: 990436
Error backing up MySQL database 'nagios' - check the password in this script!
occ
Posts: 26
Joined: Fri Jan 11, 2019 5:05 am

Re: Upgrade from 2024R1.0.1 to 2024R1.1.1 fails

Post by occ »

olabisid wrote: Mon Apr 08, 2024 10:22 am I tried both manual (from command prompt) and GUI and both fail.

command prompt failed because I was prompted for a password and it says password is incorrect.

GUI failed with log below:
---- Starting Nagios XI Backup ----
\nStarting new backup....\n
Backing up Nagios Core...
tar: Removing leading `/' from member names
tar: /usr/local/nagios/var/rw/nagios.qh: socket ignored
Backing up Nagios XI...
tar: Removing leading `/' from member names
Backing up MRTG...
tar: Removing leading `/' from member names
Backing up the SNMP directories
tar: Removing leading `/' from member names
tar: Removing leading `/' from member names
Backing up NRDP...
tar: Removing leading `/' from member names
Backing up Nagvis...
tar: Removing leading `/' from member names
Backing up nagios user home dir...
tar: Removing leading `/' from member names
Backing up MySQL databases...
mysqldump: [Warning] Using a password on the command line interface can be insecure.
mysqldump: Error: 'Access denied; you need (at least one of) the PROCESS privilege(s) for this operation' when trying to dump tablespaces
mysqldump: Error 1194: Table 'nagios_systemcommands' is marked as crashed and should be repaired when dumping table `nagios_systemcommands` at row: 990436
Error backing up MySQL database 'nagios' - check the password in this script!

Hi,
you can find your password in /usr/local/nagiosxi/script/
get_mysql_password.sh
olabisid
Posts: 14
Joined: Fri Apr 19, 2019 10:50 am

Re: Upgrade from 2024R1.0.1 to 2024R1.1.1 fails

Post by olabisid »

I tried that password and it said incorrect password...
User avatar
swolf
Developer
Posts: 308
Joined: Tue Jun 06, 2017 9:48 am

Re: Upgrade from 2024R1.0.1 to 2024R1.1.1 fails

Post by swolf »

Hi @olabisid,

Thanks for reaching out - it sounds like you might be seeing two separate issues.

First, there's the issue of getting your database credentials. When Nagios XI first sets up MySQL, it stores the root database password in /usr/local/nagiosxi/etc/xi-sys.cfg. If the password in that file doesn't get you root access to your server's database, it generally means that someone manually reconfigured the password. You'll need to check your own records for access.

Once you do recover your password, there's at least one crashed database table which may be preventing your upgrade. We have an automated solution for this via /usr/local/nagiosxi/scripts/repair_databases.sh. If this script doesn't successfully repair your database, I recommend opening a case on Answer Hub.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy
olabisid
Posts: 14
Joined: Fri Apr 19, 2019 10:50 am

Re: Upgrade from 2024R1.0.1 to 2024R1.1.1 fails

Post by olabisid »

I ran the repair command and now Nagios is taking us to the install page on the browser.

Also, when we tried to run the manual upgrade, it is still failing at the password prompt. messages below:

*** Main program, CGIs and HTML files installed ***

You can continue with installing Nagios as follows (type 'make'
without any arguments for a list of all possible options):

make install-init
- This installs the init script in /lib/systemd/system

make install-commandmode
- This installs and configures permissions on the
directory for holding the external command file

make install-config
- This installs sample config files in /usr/local/nagios/etc

make[1]: Leaving directory `/tmp/nagiosxi/subcomponents/nagioscore/nagios-4.4.13'
/usr/bin/install -c -m 755 -d -o root -g root /lib/systemd/system
/usr/bin/install -c -m 755 -o root -g root startup/default-service /lib/systemd/system/nagios.service
UPGRADE: Nagios Core upgraded OK.
Enter password:
Password failed.
Enter password:
Password failed.
Enter password:
Password failed.
Warning: Stored or entered MySQL root password does not work.
Make sure the "mysqlpass" value in "/usr/local/nagiosxi/etc/xi-sys.cfg" and
"/usr/local/nagiosxi/var/xi-sys.cfg" is up to date and accurate
or enter in the up to date password when upgrading without the "-n" option.
Skipping updates to MySQL user permissions...
Psihawk
Posts: 27
Joined: Wed May 13, 2020 9:29 pm

Re: Upgrade from 2024R1.0.1 to 2024R1.1.1 fails

Post by Psihawk »

I get the same error on mine.. Password in those files is the correct one.
I am running a two server setup with the database on a separate server. Could this be the cause? I know we had an issue that was corrected just getting to 2024 version.. Could this issue have cropped up again?
Post Reply