We have a RedHat 8 server running 2024R2.2 (and php 8.1) in a secure environment which needs offline upgrades.
I have just tried upgrading to 2024R2.2.1, it seemed successful but does not show in the frontend or in /usr/local/nagiosxi/var/xiversion
I tried following the instructions on viewtopic.php?p=362002&hilit=upgrade+no ... fa#p362002 , it went through and seemed to try installing, no visible errors in the output, but still change in the version.
It's not an issue with the 'upgrade' script and the PHP 7 rpm's, as I've excluded the rpm and removed them from the offline-nagiosxi directory, this has worked several times before.
Offline upgrade from 2024R2.2 to 2024R2.2.1 issue
Re: Offline upgrade from 2024R2.2 to 2024R2.2.1 issue
Hi @scookpfs,
I'm sorry to hear you're running into issues with offline upgrades. I believe opening a support case is the best way to fix the problems you're seeing. You can do that here.
I'm sorry to hear you're running into issues with offline upgrades. I believe opening a support case is the best way to fix the problems you're seeing. You can do that here.
-
SprunkiRetake
- Posts: 2
- Joined: Mon May 19, 2025 9:06 pm
Re: Offline upgrade from 2024R2.2 to 2024R2.2.1 issue
I ran into a similar issue during an offline upgrade — the script looked successful, but the version didn't update in the frontend or xiversion file.
Sprunki Retake Good tunes will help people relax!
Re: Offline upgrade from 2024R2.2 to 2024R2.2.1 issue
What worked for me was manually checking the contents of /usr/local/nagiosxi/tmp after the upgrade attempt. Sometimes the unpacked files don’t fully overwrite, especially if permissions are weird or SELinux is being picky. I had to chown a few things and rerun parts of the install manually.
-
zross
Re: Offline upgrade from 2024R2.2 to 2024R2.2.1 issue
Nice. Thank you.fondicky wrote: ↑Thu Oct 02, 2025 11:41 pm What worked for me was manually checking the contents of /usr/local/nagiosxi/tmp after the upgrade attempt. Sometimes the unpacked files don’t fully overwrite, especially if permissions are weird or SELinux is being picky. I had to chown a few things and rerun parts of the install manually.