Nagios XI Installation failure on RHEL 8.6

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Post Reply
deby23456
Posts: 21
Joined: Tue Apr 11, 2023 1:44 pm

Nagios XI Installation failure on RHEL 8.6

Post by deby23456 »

Hello team,

We are installing latest Nagios XI version on RHEL 8.6 server, it is a fresh installation. We do not have full internet access, but we are good enough to get the specific URLs whitelisted.

While installing the Nagios XI, we are getting below error:

Errors during downloading metadata for repository 'epel':
- Curl error (60): Peer certificate cannot be authenticated with given CA certificates for https://mirrors.fedoraproject.org/metal ... contentdir [SSL certificate problem: self signed certificate in certificate chain]
Error: Failed to download metadata for repo 'epel': Cannot prepare internal mirrorlist: Curl error (60): Peer certificate cannot be authenticated with given CA certificates for https://mirrors.fedoraproject.org/metal ... contentdir [SSL certificate problem: self signed certificate in certificate chain]
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.

Please suggest.


reply:
Accessing the epel repo is an issue with Redhat, not nagios. Have a look in /etc/yum.repos.d (or similar) and see if the path is accessible.

reply:
Not sure if it'll help or if this is the issue but did you enable CodeReady Builder? Was looking at one of their document and found this information.
https://answerhub.nagios.com/support/s/ ... I-5d1c3f10
sgardil
Posts: 124
Joined: Wed Aug 09, 2023 9:58 am

Re: Nagios XI Installation failure on RHEL 8.6

Post by sgardil »

Hey @deby23456

were you able to resolve this issue? Like mentioned in your post for the reply the mirrorlist issue is and issue with Redhat and not us. Normally when this happens it is fixed relatively quickly. If it's not fixed let us know and we can look into it more.
Post Reply