Quickstart

[rocheryderm]

Hello

Brand new customer... signed up for a Quickstart install yesterday, and am hoping anyone can set my expectations.

How long until someone at Nagios confirms receipt of my request?
How long until someone can help with the Quickstart install?

Thanks

Mike

[bolson]

Hello Mike, My name is Brian and I host the QuickStarts for Nagios Enterprises. Your post states that you are a Nagios customer. Is this true?

[rocheryderm]

For the record, "Yes."

[benjaminsmith]

Hi @rocheryderm,

Generally speaking, the QuickStarts are for prospective customers to help them get their systems up and running. Are your currently using Nagios XI? Is there anything we can help you with as far as questions or technical support goes? Please let me know.

It's Friday and the sales office is closed right now, but I can follow up with them on Monday regarding your questions.

[rocheryderm]

I've been using the Nagios XI ".ova" file for VMware and that was a fantastic way to spin up a proof-of-concept.

However, now I need to deploy XI on the corporate build (RHEL 7.2) and have had problems with the channels/repos/certificates that I am unable to squash.

I noticed that on the Nagios Quickstarts site it says:

We know you’re busy, that’s exactly why our expedited remote assistance offers up to an hour for our knowledgeable and friendly technicians to help you install and configure your Nagios software. They’ll answer your questions, customize your deployment, and completely crush any issues you’re facing.

I've reached that point.

Here is where I'm at (and I've reverted to snapshot several times already... this is just one of the results)

Code: Select all

[root@nagios1p nagiosxi]# subscription-manager attach --pool=8a85f98c61d317c90161e149c4597e2a
Successfully attached a subscription for: Red Hat Enterprise Linux Server, Standard (Physical or Virtual Nodes)

[root@nagios1p nagiosxi]# yum-config-manager --enable rhel-7-server-optional-rpms
Loaded plugins: product-id, susemanagerplugin, yumnotify
===================================================================================================== repo: rhel-7-server-optional-rpms =====================================================================================================
[rhel-7-server-optional-rpms]
async = True
bandwidth = 0
base_persistdir = /var/lib/yum/repos/x86_64/7Server
baseurl = https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/optional/os
cache = 0
cachedir = /var/cache/yum/x86_64/7Server/rhel-7-server-optional-rpms
check_config_file_age = True
compare_providers_priority = 80
cost = 1000
deltarpm_metadata_percentage = 100
deltarpm_percentage =
enabled = 1
enablegroups = True
exclude =
failovermethod = priority
ftp_disable_epsv = False
gpgcadir = /var/lib/yum/repos/x86_64/7Server/rhel-7-server-optional-rpms/gpgcadir
gpgcakey =
gpgcheck = True
gpgdir = /var/lib/yum/repos/x86_64/7Server/rhel-7-server-optional-rpms/gpgdir
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
hdrdir = /var/cache/yum/x86_64/7Server/rhel-7-server-optional-rpms/headers
http_caching = all
includepkgs =
ip_resolve =
keepalive = True
keepcache = False
mddownloadpolicy = sqlite
mdpolicy = group:small
mediaid =
metadata_expire = 86400
metadata_expire_filter = read-only:present
metalink =
minrate = 0
mirrorlist =
mirrorlist_expire = 86400
name = Red Hat Enterprise Linux 7 Server - Optional (RPMs)
old_base_cache_dir =
password =
persistdir = /var/lib/yum/repos/x86_64/7Server/rhel-7-server-optional-rpms
pkgdir = /var/cache/yum/x86_64/7Server/rhel-7-server-optional-rpms/packages
proxy = False
proxy_dict =
proxy_password =
proxy_username =
repo_gpgcheck = False
retries = 10
skip_if_unavailable = False
ssl_check_cert_permissions = True
sslcacert = /etc/rhsm/ca/redhat-uep.pem
sslclientcert = /etc/pki/entitlement/6283726763261645133.pem
sslclientkey = /etc/pki/entitlement/6283726763261645133-key.pem
sslverify = True
susemanager_token =
throttle = 0
timeout = 30.0
ui_id = rhel-7-server-optional-rpms/7Server/x86_64
ui_repoid_vars = releasever,
   basearch
username =

[root@nagios1p nagiosxi]#

[root@nagios1p nagiosxi]# ./fullinstall
Your system $PATH does not include /sbin and /usr/sbin. This is usually the result of installing GNOME rather than creating a clean system.
Adding /sbin and /usr/sbin to $PATH.
========================
Nagios XI Full Installer
========================

This script will do a complete install of Nagios XI by executing all necessary sub-scripts.

IMPORTANT: This script should only be used on a 'clean' install of CentOS, RHEL, Ubuntu LTS, Debian, or Oracle. Do NOT use this on a system that has been tasked with other purposes or has an existing install of Nagios
Core. To create such a clean install you should have selected only the base package in the OS installer.
Do you want to continue? [Y/n] Y
Proceeding with installation...
Checking MySQL credentials...
MySQL not yet installed - that's okay.
Running './0-repos'...
Configuring Repos...
package centos-release is not installed
./0-repos: line 81: rhn-channel: command not found
https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/optional/os/repodata/repomd.xml: [Errno 14] curl#60 - "Peer's certificate issuer has been marked as not trusted by the user."
Trying other mirror.
It was impossible to connect to the Red Hat servers.
This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
or a transparent proxy that tampers with TLS security, or an incorrect system clock.
Please collect information about the specific failure that occurs in your environment,
using the instructions in: https://access.redhat.com/solutions/1527033 and open a ticket with Red Hat Support.

https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/optional/os/repodata/repomd.xml: [Errno 14] curl#60 - "Peer's certificate issuer has been marked as not trusted by the user."
Trying other mirror.
https://cdn.redhat.com/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml: [Errno 14] curl#60 - "Peer's certificate issuer has been marked as not trusted by the user."
Trying other mirror.
Passed Optional Repo Check
Enabling Nagios repo...
Installing Nagios Repo PKG: packages/nagios-repo-7-3.el7.noarch.rpm
warning: packages/nagios-repo-7-3.el7.noarch.rpm: Header V4 RSA/SHA1 Signature, key ID 1e924cb3: NOKEY
Preparing...                          ########################################
Updating / installing...
nagios-repo-7-3.el7                   ########################################
Loaded plugins: product-id, subscription-manager, susemanagerplugin, yumnotify
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
Enabling EPEL repo...
Installing EPEL PKG: ./packages/epel-release-7-2.noarch.rpm
warning: ./packages/epel-release-7-2.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID 352c64e5: NOKEY
Preparing...                          ########################################
Updating / installing...
epel-release-7-2                      ########################################
Loaded plugins: product-id, subscription-manager, susemanagerplugin, yumnotify


 One of the configured repositories failed (Unknown),
 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=<repoid> ...

     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 <repoid>
        or
            subscription-manager repos --disable=<repoid>

     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=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
epel-release RPM installed OK
Repo configured OK
RESULT=0
Running './1-prereqs'...
Installing prerequisites...
Loaded plugins: product-id, subscription-manager, susemanagerplugin, yumnotify


 One of the configured repositories failed (Unknown),
 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=<repoid> ...

     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 <repoid>
        or
            subscription-manager repos --disable=<repoid>

     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=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
RESULT=1

===================
INSTALLATION ERROR!
===================
Installation step failed - exiting.
Check for error messages in the install log (install.log).

If you require assistance in resolving the issue, please include install.log
in your communications with Nagios XI technical support.

The script that failed was: './1-prereqs'
[root@nagios1p nagiosxi]#

[benjaminsmith]

Hello @rocheryderm,

Ok, let's get this worked out. Looking at the install log, it looks like this server does not have internet connectivity or are you going through a proxy server? Can you provide us more information about the RHEL 7.2 corporate build? Thanks.

Code: Select all

It was impossible to connect to the Red Hat servers.
This could mean a connectivity issue in your environment, such as the requirement to configure a proxy,
or a transparent proxy that tampers with TLS security, or an incorrect system clock.

[rocheryderm]

I definitely have access to the Internet from this host.

I found out that my corporate firewall guys are doing some kind of certificate re-signing -- I may not be using the correct phrase.

Which is breaking a lot of things, not just my ability to install Nagios with the ".fullinstall" method.

I'm now waiting for their support team to tell me how I'm supposed to get any work done. I'm open to suggestions if anyone has a clue.

The Nagios install log wasn't capturing that detail.

[benjaminsmith]

Hi @rocheryderm

We've instructions and builds for offline installations, but you will still need to install required packages from the RHEL Optional Channel from a DVD or local repository.

Installing Nagios XI In An Offline Environment
https://assets.nagios.com/downloads/nag ... onment.pdf

Let me know if you have any questions.