Nagios XI CentOS Support 8.2`

[RIDS_I2MP]

Hi Team,
We are planning to upgrade OS version of nagios servers from centos 7.8 to 8.2
Could you please update us if any challenges with CentOS 8.2 for Nagios XI 5.6.14 version application.

Thanks
Nitin Parate

[ssax]

You would need to upgrade to XI 5.7+ first (go to XI 5.7.4 if you do) to support RHEL/CENT/ORACLE 8 as support wasn't implemented for EL8 until then:

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

Personally, I would probably stay on EL7 latest for compatibility reasons, I do know that the VMWare perl SDK and the Dell EMC plugins have issues with EL8 (the respective vendors need to update them to support it). There are likely other 3rd party plugins that haven't been updated to support it yet as well.

I would spin up a test server and see if you run into issues, your XI license allows you a test/backup server:

https://support.nagios.com/kb/article.php?id=145

Let us know if you have any questions.

Thank you!

[RIDS_I2MP]

Hi Team,
We are getting below error while upgrading Nagios XI to latest version.
Please check and suggest next steps to fix it.


[root@EU2NAPU004 nagiosxi]# cd /tmp
[root@EU2NAPU004 tmp]# rm -rf nagiosxi xi*.tar.gz
[root@EU2NAPU004 tmp]# wget http://assets.nagios.com/downloads/nagi ... est.tar.gz
--2020-11-04 09:50:28-- http://assets.nagios.com/downloads/nagi ... est.tar.gz
Resolving assets.nagios.com (assets.nagios.com)... 72.14.181.71, 2600:f03c:91ff:fedf:b821
Connecting to assets.nagios.com (assets.nagios.com)|72.14.181.71|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://assets.nagios.com/downloads/nag ... est.tar.gz [following]
--2020-11-04 09:50:28-- https://assets.nagios.com/downloads/nag ... est.tar.gz
Connecting to assets.nagios.com (assets.nagios.com)|72.14.181.71|:443... connected.
ERROR: cannot verify assets.nagios.com's certificate, issued by ‘/C=UK/O=Ricoh/OU=Ricoh/CN=EUHUB02-PX002.ad.eu.rf-group.org’:
Unable to locally verify the issuer's authority.
To connect to assets.nagios.com insecurely, use `--no-check-certificate'.
[root@EU2NAPU004 tmp]# wget --no-check-certificate http://assets.nagios.com/downloads/nagi ... est.tar.gz
--2020-11-04 09:50:47-- http://assets.nagios.com/downloads/nagi ... est.tar.gz
Resolving assets.nagios.com (assets.nagios.com)... 72.14.181.71, 2600:f03c:91ff:fedf:b821
Connecting to assets.nagios.com (assets.nagios.com)|72.14.181.71|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://assets.nagios.com/downloads/nag ... est.tar.gz [following]
--2020-11-04 09:50:47-- https://assets.nagios.com/downloads/nag ... est.tar.gz
Connecting to assets.nagios.com (assets.nagios.com)|72.14.181.71|:443... connected.
WARNING: cannot verify assets.nagios.com's certificate, issued by ‘/C=UK/O=Ricoh/OU=Ricoh/CN=EUHUB02-PX002.ad.eu.rf-group.org’:
Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 200 OK
Length: 68154983 (65M) [application/x-gzip]
Saving to: ‘xi-latest.tar.gz’

100%[==============================================================================================================================>] 68,154,983 222KB/s in 3m 40s

2020-11-04 09:54:29 (303 KB/s) - ‘xi-latest.tar.gz’ saved [68154983/68154983]

[root@EU2NAPU004 tmp]# tar xzf xi-latest.tar.gz
[root@EU2NAPU004 tmp]# cd nagiosxi
[root@EU2NAPU004 nagiosxi]# ./upgrade

IMPORTANT: Before upgrading, verify you have both a valid system backup as well as a configuration backup of Nagios XI before continuing! More information
about backing up and restoring Nagios XI can be found here: https://assets.nagios.com/downloads/nag ... ios-XI.pdf

NOTICE: Your Nagios XI license includes a test environment instance that allows you to verify successful upgrade and configuration changes before applying
them to your production environment. As a best practice for ensuring the reliability of your monitoring systems, we advise you to upgrade your test environment
before upgrading any production instances. More information on licensing can be found here: https://assets.nagios.com/handouts/nagi ... Policy.pdf

Are you sure you want to continue? [y/N] y
Proceeding with upgrade...
Nagios XI Upgrade Log
==========================
DATE: Wed Nov 4 09:55:20 GMT 2020

DISTRO INFO:
CentOS
7.8.2003
x86_64


Archive: sourceguardian/ixed4.lin.x86-64.zip
inflating: /usr/lib64/php/modules/ixed.5.4.lin
Sourceguardian extension found for PHP version 5.4
Sourceguardian extension already in php.ini
Checking required prereqs...
Please wait...

OLD VERSION: 5605
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: mirror.vorboss.net
* epel: mirrors.ukfast.co.uk
* extras: mirrors.ukfast.co.uk
* updates: mirror.netweaver.uk
http://repo.nagios.com/nagios/7/repodata/repomd.xml: [Errno 14] HTTPS Error 301 - Moved Permanently
Trying other mirror.


One of the configured repositories failed (Nagios),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=nagios-base ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable nagios-base
or
subscription-manager repos --disable=nagios-base

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=nagios-base.skip_if_unavailable=true

failure: repodata/repomd.xml from nagios-base: [Errno 256] No more mirrors to try.
http://repo.nagios.com/nagios/7/repodata/repomd.xml: [Errno 14] HTTPS Error 301 - Moved Permanently
[root@EU2NAPU004 nagiosxi]# cd /tmp
[root@EU2NAPU004 tmp]# wget -O upgrade.sh https://assets.nagios.com/downloads/nagiosxi/upgrade.sh
--2020-11-04 10:01:07-- https://assets.nagios.com/downloads/nagiosxi/upgrade.sh
Resolving assets.nagios.com (assets.nagios.com)... 72.14.181.71, 2600:f03c:91ff:fedf:b821
Connecting to assets.nagios.com (assets.nagios.com)|72.14.181.71|:443... connected.
ERROR: cannot verify assets.nagios.com's certificate, issued by ‘/C=UK/O=Ricoh/OU=Ricoh/CN=EUHUB02-PX002.ad.eu.rf-group.org’:
Unable to locally verify the issuer's authority.
To connect to assets.nagios.com insecurely, use `--no-check-certificate'.


Thanks
Nitin Parate

[ssax]

Edit your /etc/yum.repos.d file for the nagios repo, change all the URLs from http to https and try again.

You'll also need to add --no-check-certificate onto your wget commands if it's failing to validate the certificate.

What do these output?

Code: Select all

nmap -Pn -p80,443 assets.nagios.com
nmap -Pn -p80,443 repo.nagios.com
curl -k -L -v 'https://assets.nagios.com'

I can only assume you have a web gateway or proxy that's interfering with it as as the cert from the output doesn't match what is actually on the site so it's likely something on your end is redirecting to it:

Code: Select all

/C=UK/O=Ricoh/OU=Ricoh/CN=EUHUB02-PX002.ad.eu.rf-group.org

[RIDS_I2MP]

Hi Team,

PFB details:

[root@EU2NAPU004 yum.repos.d]# cat nagios-7.repo
[nagios-base]
name=Nagios
baseurl=https://repo.nagios.com/nagios/7/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-NAGIOS-V2

[nagiosxi-deps]
name=Nagios XI Dependencies
baseurl=https://repo.nagios.com/nagiosxi-deps/7/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-NAGIOS-V2
[root@EU2NAPU004 yum.repos.d]# nmap -Pn -p80,443 assets.nagios.com

Starting Nmap 6.47 ( http://nmap.org ) at 2020-11-05 08:27 GMT
Nmap scan report for assets.nagios.com (72.14.181.71)
Host is up (0.00098s latency).
PORT STATE SERVICE
80/tcp open http
443/tcp open https

Nmap done: 1 IP address (1 host up) scanned in 0.28 seconds
[root@EU2NAPU004 yum.repos.d]# nmap -Pn -p80,443 repo.nagios.com

Starting Nmap 6.47 ( http://nmap.org ) at 2020-11-05 08:27 GMT
Nmap scan report for repo.nagios.com (72.14.181.71)
Host is up (0.00092s latency).
rDNS record for 72.14.181.71: assets.nagios.com
PORT STATE SERVICE
80/tcp open http
443/tcp open https

[RIDS_I2MP]

Hi Team,

[root@EU2NAPU004 yum.repos.d]# ls
CentOS-Base.repo CentOS-Debuginfo.repo CentOS-Media.repo CentOS-Vault.repo epel.repo nagios-7.repo
CentOS-CR.repo CentOS-fasttrack.repo CentOS-Sources.repo CentOS-x86_64-kernel.repo epel-testing.repo
[root@EU2NAPU004 yum.repos.d]#

I can see above files, which files needs to be updated to https from http.

Please check and update.

[ssax]

They look proper, run this command and try again:

Code: Select all

yum clean all