Can't upgrade xi past 2024R1.1.2

This support forum board is for support questions relating to Nagios xi, our flagship commercial network monitoring solution.
cbeattie-unitrends
Posts: 84
Joined: Mon Oct 10, 2016 2:51 pm

Can't upgrade xi past 2024R1.1.2

Post by cbeattie-unitrends »

Hello,

I have a Nagios xi 2024R1.1.2 instance (on CentOS Stream 9 x64) that's giving me trouble when trying to upgrade it. I've always used the Quick or Manual instructions from this PDF and I don't recall having problems like this before.

If I follow the quick instructions, the upgrade starts but then fails looking for php-imap:

Code: Select all

...
Checking global event handlers...
Checking obsessive compulsive processor commands...
Checking misc settings...

Total Warnings: 0
Total Errors:   0

Things look okay - No serious problems were detected during the pre-flight check
Last metadata expiration check: 1:03:30 ago on Tue 27 Aug 2024 03:18:58 PM UTC.
Dependencies resolved.
Nothing to do.
Complete!
Last metadata expiration check: 1:03:32 ago on Tue 27 Aug 2024 03:18:58 PM UTC.
No match for argument: php-imap
Error: Unable to find a match: php-imap
I found some other posts for php-imap but they seemed to be for either offline installs or RHEL8-based distros. I did try to single-step to the next version of Nagios xi instead, and got a completely different error:

Code: Select all

# tar xzf nagiosxi-2024R1.1.3-1.el9.x86_64.tar.gz
# cd nagiosxi
# ./upgrade
Last metadata expiration check: 1:17:10 ago on Tue 27 Aug 2024 03:18:58 PM UTC.
Error:
 Problem: problem with installed package snmptt-1.4.2-1.el9.noarch
  - package nagiosxi-nxti-2024R1.1.3-1.el9.x86_64 from @commandline conflicts with snmptt provided by snmptt-1.4.2-1.el9.noarch from @System
  - package nagiosxi-nxti-2024R1.1.3-1.el9.x86_64 from @commandline conflicts with snmptt provided by snmptt-1.4.2-1.el9.noarch from nagiosxi-deps
  - conflicting requests
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
This is the same box as this post. I can't tell if the two problems are linked or one box just happens to have two separate problems.
Top
jsimon
Posts: 318
Joined: Wed Aug 23, 2023 11:27 am

Re: Can't upgrade xi past 2024R1.1.2

Post by jsimon »

Hi @cbeattie-unitrends,

We believe we have identified and corrected this issue in our next release, which should be available in the next few days. My suggestion for you at this point would be to wait for the 2024R1.2.1 release and see if that fixes your upgrade issues. If you made a snapshot of your system pre-upgrade, I would suggest rolling back to your snapshot in the meantime and upgrading from there. We apologize for the inconvenience!
Top
cbeattie-unitrends
Posts: 84
Joined: Mon Oct 10, 2016 2:51 pm

Re: Can't upgrade xi past 2024R1.1.2

Post by cbeattie-unitrends »

Even though I waited for more releases, I wasn't able to upgrade to any of them. However, I was eventually able to figure it out. It was the same core problem that the offline and RHEL8 users had: a missing nagiosxi-deps package.

I can't remember whether I actually found it in an upgrade or offline install tarball (I tried a lot of things), but once I found the RPM I ran yum -y --nogpgcheck localinstall nagiosxi-deps-el9-2024r1.3.3-1.noarch.rpm and the upgrade script didn't die looking for php-ipam any more.

Then it died trying to stop a non-existent mariadb instance. This was baffling because as far as I could tell, it was supposed to be using mysqld. upgrade was calling manage_services.sh. It wasn't until I looked in manage_services.sh more carefully that I saw that it was reading values out of a file called xi-sys.cfg. There were multiple instances of that file, but once I found the correct one, changing the line mysqld="mariadb" to mysqld="mysqld" finally allowed upgrading that box to 2024R1.3.3.
Top

Return to “Nagios xi”