Trying to install Nagios Log Server recieve the following error for new Redhat install.
The step that failed was: 'prereqs'
Nagios Log Server Installation
==============================
DATE: Tue Nov 13 15:43:14 CET 2018
DISTRO INFO:
RedHatEnterpriseServer
7.4
x86_64
Running 'setup_local_syslog'...
setup_local_syslog step completed OK
Running 'prereqs'...
Enabling epel repo...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (60) Peer's certificate issuer has been marked as not trusted by the user.
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
===================
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 Enterprises technical support.
The step that failed was: 'prereqs'
Nagios Log Server Installer
Copyright 2014-2018, Nagios Enterprises LLC.
License:
Nagios Software License <http://assets.nagios.com/licenses/nagio ... icense.txt>
Usage: ./fullinstall [options...]
Options:
-h | --help
Display this help text
-a | --add_node
-m | --master
-i | --id
-n | --non-interactive
Assume defaults for all questions (for scripted installs)
ERROR: invalid command line syntax.
Nagios Log Server Installation
==============================
DATE: Tue Nov 13 15:47:32 CET 2018
DISTRO INFO:
RedHatEnterpriseServer
7.4
x86_64
Running 'setup_local_syslog'...
setup_local_syslog step already completed - skipping
Running 'prereqs'...
Enabling epel repo...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (60) Peer's certificate issuer has been marked as not trusted by the user.
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
===================
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 Enterprises technical support.
The step that failed was: 'prereqs'
The step that failed was: 'prereqs'
-
- Support Tech
- Posts: 3457
- Joined: Mon May 15, 2017 5:00 pm
Re: The step that failed was: 'prereqs'
@delwins, You have a problem with the CURL command:
https://access.redhat.com/solutions/3034501
Please go over the following article and let me know if it fixes your issue:curl: (60) Peer's certificate issuer has been marked as not trusted by the user.
https://access.redhat.com/solutions/3034501
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.