Zabbix Agent Rocky Linux 9 Update Issues
I have been running into an issue with Zabbix and Rocky Linux 9. It appears there is a conflict between the zabbix repo packages and the EPEL packages that is what is causing this issue:
Whenever I tried to yum update with both the zabbix repos and the EPEL repos enabled I would get the following output.
Error:
Problem 1: package zabbix-web-deps-6.4.12-release1.el9.noarch from zabbix requires zabbix-web = 6.4.12-release1.el9, but none of the providers can be installed
- cannot install both zabbix-web-6.4.12-release1.el9.noarch from zabbix and zabbix-web-1:6.0.25-1.el9.noarch from epel
- cannot install the best update candidate for package zabbix-web-deps-6.4.7-release1.el9.noarch
- cannot install the best update candidate for package zabbix-web-6.4.7-release1.el9.noarch
Problem 2: cannot install both zabbix-web-6.4.12-release1.el9.noarch from zabbix and zabbix-web-1:6.0.25-1.el9.noarch from epel
- package zabbix-web-deps-6.4.12-release1.el9.noarch from zabbix requires zabbix-web = 6.4.12-release1.el9, but none of the providers can be installed
- package zabbix-web-pgsql-1:6.0.25-1.el9.noarch from epel requires zabbix-web = 1:6.0.25-1.el9, but none of the providers can be installed
- package zabbix-nginx-conf-6.4.12-release1.el9.noarch from zabbix requires zabbix-web-deps = 6.4.12-release1.el9, but none of the providers can be installed
- cannot install the best update candidate for package zabbix-web-pgsql-6.4.7-release1.el9.noarch
- cannot install the best update candidate for package zabbix-nginx-conf-6.4.7-release1.el9.noarch
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Editing /etc/yum.repos.d/epel.repo
and adding the following line to the file should resolve this issue.
Line to add:
excludepkgs=zabbix*
My /etc/yum.repos.d/epel.repo
now looks like
[epel]
name=Extra Packages for Enterprise Linux $releasever - $basearch
# It is much more secure to use the metalink, but if you wish to use a local mirror
# place its address here.
#baseurl=https://download.example/pub/epel/$releasever/Everything/$basearch/
metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-$releasever&arch=$basearch&infra=$infra&content=$contentdir
enabled=1
gpgcheck=1
countme=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-$releasever
exclude=zabbix*
[epel-debuginfo]
name=Extra Packages for Enterprise Linux $releasever - $basearch - Debug
# It is much more secure to use the metalink, but if you wish to use a local mirror
# place its address here.
#baseurl=https://download.example/pub/epel/$releasever/Everything/$basearch/debug/
metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-debug-$releasever&arch=$basearch&infra=$infra&content=$contentdir
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-$releasever
gpgcheck=1
[epel-source]
name=Extra Packages for Enterprise Linux $releasever - $basearch - Source
# It is much more secure to use the metalink, but if you wish to use a local mirror
# place its address here.
#baseurl=https://download.example/pub/epel/$releasever/Everything/source/tree/
metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-source-$releasever&arch=$basearch&infra=$infra&content=$contentdir
enabled=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-$releasever
gpgcheck=1
After reinstalling the zabbix agent. I am now able to run yum update
and not get the error that I was getting before.