Displayed version not correct

[smblair]

We just upgraded, using RPMs in an isolated environment, from 5.6.9 to 5.6.13 and all appears well except for the web UI displayed version. We tried running the suggested Mysql command, to no effect. This is not a great concern but we would prefer to have the current version displayed correctly.

Any suggestions?

[benjaminsmith]

Hello @smblair

I found another case with a similar issue it was due to noexec set on /tmp directory, when you run the following command are the latest packages installed?

Code: Select all

rpm -qa | grep nagios

Is the /usr/local/nagiosxi/tmp/upgrade.log still available? Also please send over the system profile for us to review and check the versions. Thanks.

To send us your system profile.
Login to the Nagios XI GUI using a web browser
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and share this in a private message and then reply to this post to bring it up in the queue.

[smblair]

Your suggested grep would have found nothing. The correct regex is '^nagios'. Package names are generally not capitalized. And yes, the packages are up to date, I updated it today.
The last upgrade.log is from 2019-05-20 and only relates to backup. Probably not helpful.
Our environment is very restrictive and the systems are CIS compliant , with a few exceptions. I remounted both /tmp and /var/tmp with noexec removed, restarted Nagios, and no change.
Executing "View System Info" worked fine and that is what is attached. Executing "Download Profile" resulted in:
PROFILE BUILD FAILED
Array
(
)
CODE: 1
System profile sent in pm, per request.

[ssax]

If the version didn't update, the upgrade did not succeed (even when the RPMs show success).

You must do this:

Download the same version again and put it in your /tmp directory of your XI server:

Code: Select all

https://repo.nagios.com/?repo=offline

Then as root, run these commands on your XI server:
- Run every command exactly as shown, the mv/cd is there for a reason

Code: Select all

cd /tmp
rm -rf nagiosxi
tar zxf nagiosxi-5.6.13-1.el7.x86_64.tar.gz​
mv nagiosxi nag
cd nag
rpm2cpio nagiosxi-5.6.13-1.el7.x86_64.tar.gz​ | cpio -idmv
cd tmp/nagiosxi
./rpmupgrade

Then send us the full output of all the commands.

Thank you

[smblair]

This system is subscribed to a Foreman server and has access to all the RPMs from your repo. Our policies and practical concerns do not allow individually downloading to a specific system which has no internet access.
What is it that you think would be different from performing "rpmupgrade" vs. "yum install" from Foreman when they are the same packages?

[ssax]

Running it that way gives you the errors, that's the only way that I know how to get you access to that info.

I have no experience with Foreman so I'm unable to help you there.

[smblair]

Foreman is the upstream project from Red Hat's Satellite 6 server. It is, at minimum, a package manager that effectively mirrors remote repositories like yours. We keep the five most recent versions of a given package. For instance, we have nagiosxi versions 5.6.10 through 5.6.13.
When we had a compatibility problem with an earlier Xi version, we had no problem reverting to a known good version using "yum downgrade". Foreman behaves exactly as if the system were directly subscribed to your yum repository.

I attached an excerpt from yum.log and a listing of currently installed RPMs. There are no other Nagios RPMs installed.

[ssax]

This is the one that failed:

Code: Select all

nagiosxi-5.6.13-1.el7.x86_64

Even though it's an RPM, it still tries to do DB updates and other things, check out the rpmupgrade file if you have questions. One of the subprocesses failed so it didn't actually upgrade nagiosxi fully even though yum said it did. For whatever reason one of the subprocessese failed which didn't notify the package manager to say it failed. I do know that running it the way that I found (which has fixed many others with this same issue) allows you to see what those errors are. If you can think of a better way to get access to that information I'm all ears. That's the only way I've found.

You can use the RPM from the Foreman server if you'd like, I just don't know of any other way to get you access to those errors messages so that you can see them and fix the issues so that it can be installed completely.

Do you see error(s) in this file?

Code: Select all

/tmp/xi-upgrade.log