Upgrading from 2.2.3 to 2.3.0

SteveBeauchemin · Post by **SteveBeauchemin** » Thu Sep 14, 2017 10:52 am

I plan to do the upgrade soon, but before I do, are there an issues I need to know about ahead of time.

Are there any possible stumbling blocks to be aware of.

Please advise.

Thanks

Steve B

Post by **tgriep** » Thu Sep 14, 2017 12:10 pm

I did a search and I found a few people having issues with custom Python installs which caused the rrdtool from building.
It is needed to display / generate the Bandwidth graph.
But other than that, I didn't find much else but make sure you do a backup first.

SteveBeauchemin · Post by **SteveBeauchemin** » Thu Sep 14, 2017 2:33 pm

I like ESX and vmware.

The upgrade ran clean but nothing worked after.

The sources were gone, the web pages were not found... not much fun.

I reverted the ESX to a snapshot I made a couple hours ago in case this happened.

So I am at 2.2.3 still.

I could have just reinstalled it from scratch I suppose, from the fullinstall script. I just couldn't have the down time today.

I could not find any install or upgrade log file after either.

Steve B

Post by **tgriep** » Thu Sep 14, 2017 4:00 pm

The NNA installs / upgrades do not create a log files so you would have to scroll back in the buffer and look at the errors if any were produced.

It almost sounds like the Web server wasn't running after the upgrade.
One thing, did you try and reboot the server after the upgrade to see if things start up?

Can you run the following on the NNA server and post it here so we can get some specifics of the OS the NNA software is running on?

Code: Select all

uname -a
cat /etc/*release*
php -v
python -V

Thanks.

SteveBeauchemin · Post by **SteveBeauchemin** » Thu Sep 14, 2017 5:01 pm

I am providing the data requested. I did not reboot the server after upgrade.

I did the manual upgrade from /tmp/nagiosna with NNA running. After the upgrade completed I stopped all related items: httpd mariadb nagiosna
I used ps -ef and made sure nothing was running, killed off any nna owned processes.
Then started up: httpd mariadb nagiosna

I will go through the upgrade again next week and do a reboot after. I just could not afford the down time today.

Results as requested:

Code: Select all

uname -a
Linux [hostname] 3.10.0-514.26.2.el7.x86_64 #1 SMP Fri Jun 30 05:26:04 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

cat /etc/*release*
cat: /etc/lsb-release.d/: Is a directory
NAME="Red Hat Enterprise Linux Server"
VERSION="7.3 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="7.3"
PRETTY_NAME="Red Hat Enterprise Linux Server 7.3 (Maipo)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:redhat:enterprise_linux:7.3:GA:server"
HOME_URL="https://www.redhat.com/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 7"
REDHAT_BUGZILLA_PRODUCT_VERSION=7.3
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="7.3"
Red Hat Enterprise Linux Server release 7.3 (Maipo)
Red Hat Enterprise Linux Server release 7.3 (Maipo)
cpe:/o:redhat:enterprise_linux:7.3:ga:server

php -v
PHP 5.4.16 (cli) (built: Aug  5 2016 07:50:38)
Copyright (c) 1997-2013 The PHP Group
Zend Engine v2.4.0, Copyright (c) 1998-2013 Zend Technologies

python -V
Python 2.7.5

Thanks

Steve B

Post by **tgriep** » Fri Sep 15, 2017 12:11 pm

Thanks for the data. All of the versions look stock.

Next time you run the upgrade, screen capture the error and post it.
Run the following as root and post the output.

Code: Select all

ps -ef --cols=300

And if you cannot access the Web interface, look at the Apache log files in the following folder for any errors and post them.

Code: Select all

/var/log/httpd

Thanks

Nagios Support Forum

Upgrading from 2.2.3 to 2.3.0

Upgrading from 2.2.3 to 2.3.0

Re: Upgrading from 2.2.3 to 2.3.0

Re: Upgrading from 2.2.3 to 2.3.0

Re: Upgrading from 2.2.3 to 2.3.0

Re: Upgrading from 2.2.3 to 2.3.0

Re: Upgrading from 2.2.3 to 2.3.0