Nagios Support Forum

When upgrading to 5.8.2 the upgrade fails out with this:

Updating Subscription Management repositories.
This system is registered to Red Hat Subscription Management, but is not receiving updates. You can use subscription-manager to assign subscriptions.
10 files removed
Updating Subscription Management repositories.
This system is registered to Red Hat Subscription Management, but is not receiving updates. You can use subscription-manager to assign subscriptions.
RHEL_7_Server_EPEL_RPMs_x86_64_7Server 51 MB/s | 17 MB 00:00
Last metadata expiration check: 0:00:04 ago on Thu 25 Feb 2021 04:34:00 PM EST.
Error:
Problem: conflicting requests
- nothing provides cyrus-sasl-plain needed by nagiosxi-deps-el8-5.8.2-1.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)


It sounds like I maybe just need to install this?

https://centos.pkgs.org/8/centos-baseos ... 4.rpm.html

But wanted to confirm since this is the first upgrade I've had require some kind of prerequisite.

I'm on RHEL 8.2 and NagX1 5.8.1 if that helps. Tried to DNF it but could find it:

dnf install cyrus-sasl-plain
Updating Subscription Management repositories.
This system is registered to Red Hat Subscription Management, but is not receiving updates. You can use subscription-manager to assign subscriptions.
RHEL_7_Server_EPEL_RPMs_x86_64_7Server 64 kB/s | 2.5 kB 00:00
No match for argument: cyrus-sasl-plain
Error: Unable to find a match: cyrus-sasl-plain

From a high level, you'll want to remove the Nagios RHEL7 repo and replace it with the Nagios RHEL8 repo.

You can find repo information on this page, including instructions: https://repo.nagios.com/?repo=rpm-centos

Not entirely following. To my knowledge Nagios was installed with the RHEL 8 repo

rpm -qa | grep -i 'nagios'
nagios-repo-8-1.el8.noarch
nagios-test-repo-8-1.el8.noarch
nagiosxi-deps-el8-5.8.1-1.noarch

These should be the right ones right? If you're talking about that "RHEL_7_Server_EPEL_RPMs_x86_64_7Server" that's just an internal repo we have:

Repo-id : Default_Organization_RHEL_7_Server_EPEL_RPMs_x86_64_7Server_RHEL_7_Server_EPEL_RPMs_x86_64_7Server
Repo-name : RHEL_7_Server_EPEL_RPMs_x86_64_7Server
Repo-revision : 1609299067
Repo-updated : Tue 29 Dec 2020 10:31:07 PM EST
Repo-pkgs : 13,501
Repo-available-pkgs: 13,476
Repo-size : 16 G
Repo-baseurl : https://vml1030.servers.windstream.com/ ... 64_7Server
Repo-expire : 1 second(s) (last: Fri 26 Feb 2021 03:28:52 PM EST)
Repo-filename : /etc/yum.repos.d/redhat.repo

Repo-id : nagios-base
Repo-name : Nagios
Repo-revision : 1613083194
Repo-updated : Thu 11 Feb 2021 05:39:57 PM EST
Repo-pkgs : 80
Repo-available-pkgs: 80
Repo-size : 606 M
Repo-baseurl : https://repo.nagios.com/nagios/8/
Repo-expire : 172,800 second(s) (last: Fri 26 Feb 2021 03:28:52 PM EST)
Repo-filename : /etc/yum.repos.d/nagios-8.repo

Repo-id : nagiosxi-deps
Repo-name : Nagios XI Dependencies
Repo-revision : 1614180218
Repo-updated : Wed 24 Feb 2021 10:23:38 AM EST
Repo-pkgs : 26
Repo-available-pkgs: 26
Repo-size : 4.3 M
Repo-baseurl : https://repo.nagios.com/nagiosxi-deps/8/
Repo-expire : 172,800 second(s) (last: Fri 26 Feb 2021 03:28:52 PM EST)
Repo-filename : /etc/yum.repos.d/nagios-8.repo

It's not possible to pull updates from RedHat unless you have an active subscription.

If I had to guess, I'd say your internal package repo is serving a set of packages for RHEL 7, and because you don't have a sub with RH, your machine isn't set up to pull updates from RH's servers either, so there's no RHEL8 packages available to your system.

You need at least one package repo serving RHEL 8 packages.

Ahh you mean the 8 EPEL? https://dl.fedoraproject.org/pub/epel/e ... noarch.rpm. I read "Nagios RHEL7 repo and replace it with the Nagios RHEL8 repo" as the Nagios Repo. I'll have to open a ticket to our security team to open a connection to dl.fedoraproject.org before I can add the EPEL 8 repo. I'll do that and try the update again after I add the repo.

Okay, let us know if that works.

Worked with our networking team to get an exception to the IPs needed for the RHEL 8 Public repo instead of our private one. After we got that it looks like it worked, so ty. I think this is safe to close. Although I'll mention the yum update using the public repo leaves me with only python3 and I have to keep making a symlink for python for checks to work.

ln -sf /usr/bin/python3 /usr/bin/python

Something to check and handle that would be useful.

J.A.K wrote:Worked with our networking team to get an exception to the IPs needed for the RHEL 8 Public repo instead of our private one. After we got that it looks like it worked, so ty. I think this is safe to close. Although I'll mention the yum update using the public repo leaves me with only python3 and I have to keep making a symlink for python for checks to work.

ln -sf /usr/bin/python3 /usr/bin/python

Something to check and handle that would be useful.

Locking thread