Nagios Support Forum

Updating 412 to 529 fails
The Nagios XI is running in a VMware 5.5.0 environment imported from an ova.
CentOS release 6.5 (Final)
Kernel 2.6.32-358.2.1.e16.x86_64 on an x86_64, (64 bit)
I followed the instructions in the XI_Upgrade_Instructions.pdf and after issuing the update script the process fails because it cannot connect to a mirror.
This script is searching for a Centos/6.6/ directory which has been depreciated to /6/

Can the xi-5.2.9.tar.gz be used in place of the xi-latest.tar.gz, with the XI_Upgrade_Instructions.pdf successfully?
OR
Has the Beta offline procedure in http://repo.nagios.com/#offline with nagiosxi-5-2.9.el6.x86_64.tar.gz been used successfully?
OR
Will the backup of this appliance restore properly on the new nagiosxi-5.2.9-64.ova ?

[email protected] wrote:Updating 412 to 529 fails
The Nagios XI is running in a VMware 5.5.0 environment imported from an ova.
CentOS release 6.5 (Final)
Kernel 2.6.32-358.2.1.e16.x86_64 on an x86_64, (64 bit)
I followed the instructions in the XI_Upgrade_Instructions.pdf and after issuing the update script the process fails because it cannot connect to a mirror.
This script is searching for a Centos/6.6/ directory which has been depreciated to /6/

Could you post the install.log for us to look at? Are you using a proxy, or do you have a firewall blocking traffic?

Can the xi-5.2.9.tar.gz be used in place of the xi-latest.tar.gz, with the XI_Upgrade_Instructions.pdf successfully?

Yes.

Has the Beta offline procedure in http://repo.nagios.com/#offline with nagiosxi-5-2.9.el6.x86_64.tar.gz been used successfully?

Yes, but this will only work for existing upgrades, that were started as offline installs.

Will the backup of this appliance restore properly on the new nagiosxi-5.2.9-64.ova ?

If you were using postgres previously, I don't believe so. You would need to dump the files.

I am not using a proxy, I can get to the mirror sites listed, and the 6.6 directory has a message in it that the 6.6 has been depreciated use 6
I looked at the upgrade log. It looks like the access may be being blocked from the device. Please confirm

I'm not seeing any errors in that upgrade.log, what is the exact error you are receiving?

We got the ports opened on the firewall/proxy. It is now working

Awesome! Is it alright if we lock this thread and mark this issue as resolved?

Yes