Page 2 of 2
Re: Upgrade from nagiso XI 2014R2.6 to Nagios XI 5
Posted: Thu Dec 03, 2015 2:29 pm
by jomann
It looks like you don't have perl-Config-Tiny, you can try running
yum install perl-Config-Tiny
However it should have been added with other perl modules via dependencies.
Re: Upgrade from nagiso XI 2014R2.6 to Nagios XI 5
Posted: Thu Dec 03, 2015 3:03 pm
by emartine
yum install perl-Config-Tiny
Loaded plugins: package_upload, product-id, security, subscription-manager
Setting up Install Process
Package perl-Config-Tiny-2.12-1.el6.rfx.noarch already installed and latest version
Nothing to do
At this time it looks like the web interface is now unavailable. I get a login prompt but after authenticating I get an error 500 when attempting to login.
Re: Upgrade from nagiso XI 2014R2.6 to Nagios XI 5
Posted: Thu Dec 03, 2015 10:33 pm
by Box293
With the webpage inacessible we''ll need to proceed with a command line upgrade, which is straight forward.
First, please run
Code: Select all
yum install --disablerepo=rpmforge -y 'perl(Test::Simple)' 'perl(Class::Accessor)' perl-Params-Validate perl-Config-Tiny perl-Math-Calc-Units
Let us know what the output of this is.
If it all appears OK, please follow this procedure:
https://assets.nagios.com/downloads/nag ... nstall.pdf
If this fails, please post the output.
Re: Upgrade from nagiso XI 2014R2.6 to Nagios XI 5
Posted: Wed Dec 09, 2015 11:48 am
by emartine
On Friday I rebooted and tried it again manually and it succeeded 5.2.2. Seems to be working. Today I attempted update to the latest version since a version update was recently released.
I did this upgrade over the web interface and although the command box say
==================
UPGRADE COMPLETED!
==================
The web says
The update did not complete successfully. Please try updating manually.
After a refresh the bottom page now says 5.2.3
Attempting to check for updates says we are up-to-date.
Time to start using it and testing.
Re: Upgrade from nagiso XI 2014R2.6 to Nagios XI 5
Posted: Wed Dec 09, 2015 12:07 pm
by hsmith
That's just a display bug. It should be squashed in the next version.