Nagios Version Upgrade

[kenneth59]

Hi All,

I am currently testing an upgrade of Nagios in an offline environment before applying it to the actual system and have encountered an issue.

Current Specifications:

• Nagios Version: 5.8.9

• Operating System: Red Hat 8.9

• Network: Offline (not connected to the internet)

Based on the documentation linked below, it appears that to upgrade to nagiosxi-2024R1, I first need to upgrade to Nagios 5.10. I followed this process and successfully upgraded to nagiosxi-2024R1 from Nagios 5.10. However, I noticed the following:

There is no change in the user interface, and the Nagios version number at the bottom of the screen still shows Nagios 5.10.
Running cat /usr/local/nagiosxi/var/xiversion also indicates that the version is still 5.10.
However, when I run rpm -q nagiosxi in the terminal, it shows that nagiosxi-2024R1.3.1-1.el8.x86_64 is installed.
Could you help clarify why this discrepancy exists? How can I confirm that the system is indeed running nagiosxi-2024R1.3.1-1.el8.x86_64?

Reference Document:
https://assets.nagios.com/downloads/nag ... onment.pdf

[jsimon]

Hi @kenneth59,

Do you know how your Nagios server was originally set up? This could be the result of an incompatibility with RPM and source installs, depending on how your server was originally set up. Can you provide the output of the following command? This will help with diagnosis.

Code: Select all

yum list --installed | grep nagios

[kenneth59]

Hi @kenneth59,

Do you know how your Nagios server was originally set up? This could be the result of an incompatibility with RPM and source installs, depending on how your server was originally set up. Can you provide the output of the following command? This will help with diagnosis.

Code: Select all

yum list --installed | grep nagios

Hi jsimon,

The results from running the mentioned command show nagiosxi-wkhtmltox.x86_64 at version 5.11.3-1.el8. This is because, in my earlier attempts to upgrade from 5.10, the upgrade did not work as expected. I then tried the upgrade again after moving to version 5.11.3, but both versions presented the same issue.

Below is the result after running the command you mention

Code: Select all

nagios-repo.noarch                            8-2.el8                                   @System
nagiosxi.x86_64                               2024R1.3.1-1.el8                          @@commandline
nagiosxi-mrtg.x86_64                          2024R1.3.1-1.el8                          @@commandline
nagiosxi-nagioscore.x86_64                    2024R1.3.1-1.el8                          @@commandline
nagiosxi-nagiosplugins.x86_64                 2024R1.3.1-1.el8                          @@commandline
nagiosxi-nagvis.x86_64                        2024R1.3.1-1.el8                          @@commandline
nagiosxi-ndoutils.x86_64                      2024R1.3.1-1.el8                          @@commandline
nagiosxi-nrds.x86_64                          2024R1.3.1-1.el8                          @@commandline
nagiosxi-nrpe.x86_64                          2024R1.3.1-1.el8                          @@commandline
nagiosxi-nsca.x86_64                          2024R1.3.1-1.el8                          @@commandline
nagiosxi-nxti.x86_64                          2024R1.3.1-1.el8                          @@commandline
nagiosxi-phantomjs.x86_64                     2024R1.3.1-1.el8                          @@commandline
nagiosxi-pnp.x86_64                           2024R1.3.1-1.el8                          @@commandline
nagiosxi-shellinabox.x86_64                   2024R1.3.1-1.el8                          @@commandline
nagiosxi-wkhtmltox.x86_64                     5.11.3-1.el8                              @@commandline
nagiosxi-wmic.x86_64                          2024R1.3.1-1.el8                          @@commandline

[jsimon]

That is interesting. Given it looks like this was a standard RPM/Offline installation that was upgraded properly, it seems to me like the ideal next steps for diagnosis would be opening a case with our Support department, as this will likely require a more detailed investigation into your system profile to figure out.

It might be worth noting that wkhtmltox was deprecated as of XI version 2024R1.1, and we are now using Chromium Browser for report generation, so this is a package that need not be maintained going forward.

[kenneth59]

That is interesting. Given it looks like this was a standard RPM/Offline installation that was upgraded properly, it seems to me like the ideal next steps for diagnosis would be opening a case with our Support department, as this will likely require a more detailed investigation into your system profile to figure out.

It might be worth noting that wkhtmltox was deprecated as of XI version 2024R1.1, and we are now using Chromium Browser for report generation, so this is a package that need not be maintained going forward.

Noted. Thank you for your help. I will consider raising a ticket if I still can't get it to work

[kenneth59]

Hi @jsimon,

I discovered the cause of the incomplete installation. During the installation process, the httpd service needs to be running. However, Nagios 2024R1.3.1-1.el8 requires the yajl RPM package to be installed for the httpd service to function. If the package is not installed before the upgrade, the httpd service stops operating, preventing the user interface components from being updated.

After installing the yajl RPM package, the httpd service can restart, but since the service was down during the initial installation, starting it afterward results in the user interface appearing unchanged. Additionally, because Nagios has already been upgraded, attempting to rerun the upgrade process fails as the system detects that the latest version is already installed.

Is there a way to update the user interface package under these circumstances?

[gwesterman]

Hi @kenneth59,

There may be a fix for your specific circumstance, but I highly recommend just restarting the process with the required packages installed (although I am surprised they aren't). If you don't have a snapshot that allows you to do so let us know, but I cannot guarantee anything and would likely point you to opening a support ticket under that circumstance.

Thank you!

[kenneth59]

Hi @gwesterman,

Got it, thank you! I ran the RPM file manually, and everything is now working fine.