Nagios Support Forum

Dumb question. But i am attempting to upgrade and older install of NagiosXI. We had it running in a fully offline environment. But we're finally able to connect it to a proxy out. If I attempt to update through the webUI it just sits there for hours on end with no movement.

I then attempted to run the update from yum. yum update nagiosxi. Returns no packages marked for upgrade.

Then I attempted to run the latest offline update 5.6.13. it comes back saying the nagiosxi-dep-5.3.2-1 are not compatible.

So I need some help with this.

Environment is NagiosXI Appliance 2.2 (CentOS 6) Nagios version 5.3.2

If you started from one of our appliances, you would want to follow this document for upgrading

https://assets.nagios.com/downloads/nag ... ctions.pdf

Okay. So I have tried to run these commands before. I apologize I did not give the output.

I have tried to run it both online and offline manually. Here is the output from the online attempt I just ran.

Cleaning repos: base extras nagios-base nagiosxi-deps updates
Cleaning up Everything
Cleaning up list of fastest mirrors
Loaded plugins: fastestmirror
Setting up Local Package Process
Examining /tmp/nagiosxi/nagiosxi-deps-5.6.14-1.noarch.rpm: nagiosxi-deps-5.6.14-1.noarch
Marking /tmp/nagiosxi/nagiosxi-deps-5.6.14-1.noarch.rpm as an update to nagiosxi-deps-5.3.2-1.noarch
Determining fastest mirrors
Resolving Dependencies
--> Running transaction check
---> Package nagiosxi-deps.noarch 0:5.3.2-1 will be updated
---> Package nagiosxi-deps.noarch 0:5.6.14-1 will be an update
--> Processing Dependency: snmptt for package: nagiosxi-deps-5.6.14-1.noarch
--> Processing Dependency: net-snmp-perl for package: nagiosxi-deps-5.6.14-1.noarch
--> Processing Dependency: php-devel for package: nagiosxi-deps-5.6.14-1.noarch
--> Processing Dependency: php-imap for package: nagiosxi-deps-5.6.14-1.noarch
--> Processing Dependency: python-pip for package: nagiosxi-deps-5.6.14-1.noarch
--> Processing Dependency: rsync for package: nagiosxi-deps-5.6.14-1.noarch
--> Processing Dependency: ansible for package: nagiosxi-deps-5.6.14-1.noarch
--> Processing Dependency: shellinabox for package: nagiosxi-deps-5.6.14-1.noarch
--> Running transaction check
---> Package nagiosxi-deps.noarch 0:5.6.14-1 will be an update
--> Processing Dependency: snmptt for package: nagiosxi-deps-5.6.14-1.noarch
--> Processing Dependency: python-pip for package: nagiosxi-deps-5.6.14-1.noarch
--> Processing Dependency: ansible for package: nagiosxi-deps-5.6.14-1.noarch
--> Processing Dependency: shellinabox for package: nagiosxi-deps-5.6.14-1.noarch
---> Package net-snmp-perl.x86_64 1:5.5-60.el6_10.1 will be installed
---> Package php-devel.x86_64 0:5.3.3-50.el6_10 will be installed
---> Package php-imap.x86_64 0:5.3.3-50.el6_10 will be installed
--> Processing Dependency: libc-client.so.2007()(64bit) for package: php-imap-5.3.3-50.el6_10.x86_64
---> Package rsync.x86_64 0:3.0.6-12.el6 will be installed
--> Running transaction check
---> Package libc-client.x86_64 0:2007e-11.el6 will be installed
---> Package nagiosxi-deps.noarch 0:5.6.14-1 will be an update
--> Processing Dependency: snmptt for package: nagiosxi-deps-5.6.14-1.noarch
--> Processing Dependency: python-pip for package: nagiosxi-deps-5.6.14-1.noarch
--> Processing Dependency: ansible for package: nagiosxi-deps-5.6.14-1.noarch
--> Processing Dependency: shellinabox for package: nagiosxi-deps-5.6.14-1.noarch
--> Finished Dependency Resolution
Error: Package: nagiosxi-deps-5.6.14-1.noarch (/nagiosxi-deps-5.6.14-1.noarch)
Requires: ansible
Error: Package: nagiosxi-deps-5.6.14-1.noarch (/nagiosxi-deps-5.6.14-1.noarch)
Requires: python-pip
Error: Package: nagiosxi-deps-5.6.14-1.noarch (/nagiosxi-deps-5.6.14-1.noarch)
Requires: snmptt
Error: Package: nagiosxi-deps-5.6.14-1.noarch (/nagiosxi-deps-5.6.14-1.noarch)
Requires: shellinabox
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

The only change from online to offline is in offline it complains that the 5.3.2-deps are not compatible.

Let me know where to go or try next.

This looks like someone removed or disabled the epel repository

Run the following to add it to your installation

Yeah I was just about to reply. The epel.repo file was busted. I am running the upgrade now and it seems to be working. I will upload results when it is finished.

Thanks

derik.petty wrote:Yeah I was just about to reply. The epel.repo file was busted. I am running the upgrade now and it seems to be working. I will upload results when it is finished.

Thanks

Sounds good!