[ZBX-21865] Zabbix 6.0 LTS install from repo fails with dependency resolution failure Created: 2022 Nov 03  Updated: 2022 Dec 05  Resolved: 2022 Nov 04

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Packages (C)
Affects Version/s: 6.0.10
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Alan McKinnon Assignee: Aleksey Volodin
Resolution: Duplicate Votes: 0
Labels: installation, packages
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

New Rocky9 minimal install after running yum update.

Issue Links:
Duplicate
duplicates ZBX-21363 rpm packages for rhel 9 from zabbix-r... Closed
Story Points: 0

 Description   

Steps to reproduce:

  1. Create new Rocky9 VM, run yum update
  2. Install mariadb-server
  3. Follow official installation instructions at https://www.zabbix.com/download for Zabbix 6.0LTS / Rocky 9 / Server, Frontend, Agent / Mysql / Apache
  4.  

Result:

This command:

{{{{dnf install zabbix-server-mysql zabbix-web-mysql zabbix-apache-conf zabbix-sql-scripts zabbix-selinux-policy zabbix-agent }}}}

fails to fulfil dependencies and gives this error:

Error: 
 Problem: package zabbix-web-deps-6.0.10-release1.el9.noarch requires zabbix-web = 6.0.10-release1.el9, but none of the providers can be installed
  - cannot install both zabbix-web-6.0.10-release1.el9.noarch and zabbix-web-1:6.0.8-1.el9.noarch
  - package zabbix-apache-conf-6.0.10-release1.el9.noarch requires zabbix-web-deps = 6.0.10-release1.el9, but none of the providers can be installed
  - package zabbix-web-mysql-1:6.0.8-1.el9.noarch requires zabbix-web = 1:6.0.8-1.el9, but none of the providers can be installed
  - cannot install the best candidate for the job
(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)

Running the command again with option --nobest allows package installation to complete with these out-of-sync versions:

[root@zabbix ~]# rpm -qa zabbix-web
zabbix-web-6.0.10-release1.el9.noarch
[root@zabbix ~]# rpm -qa zabbix-web-mysql
zabbix-web-mysql-6.0.10-release1.el9.noarch

I cannot determine yet if these different versions of packages work correctly together

 

Expected:

All Zabbix components should successfully resolve with their dependencies, either version 6.0.8 or 6.0.10, which ever is newest

 Comments   
Comment by Alan McKinnon [ 2022 Nov 03 ]

After some more investigation I see the problem is the presence of EPEL repo so we must add a 4th step to "Steps To Reproduce":

4. Install EPEL Repo:

dnf install http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm{{{}{}}}

 

Now running dnf --showduplicates shows the actual problem:{{{}{}}}

[root@zabbix repodata]# dnf --showduplicates list zabbix-server-mysql
Last metadata expiration check: 0:02:20 ago on Thu 03 Nov 2022 22:48:35.
Installed Packages
zabbix-server-mysql.x86_64                                         1:6.0.8-1.el9                                               @epel 
Available Packages
zabbix-server-mysql.x86_64                                         6.0.6-2.el9                                                 zabbix
zabbix-server-mysql.x86_64                                         6.0.7-1.el9                                                 zabbix
zabbix-server-mysql.x86_64                                         6.0.8-release1.el9                                          zabbix
zabbix-server-mysql.x86_64                                         6.0.9-release1.el9                                          zabbix
zabbix-server-mysql.x86_64                                         6.0.10-release1.el9                                         zabbix
{{zabbix-server-mysql.x86_64                                         1:6.0.8-1.el9                                               epel }}

 

I am not an expert in yum/dnf and did not want to chase endless search engine results on how to prefer packages(s) from a defined repo, so I simply disabled the EPEL repo, ran dnf makecache and the installation step 2b now runs correctly. As long as EPEL is disabled, all is fine but the original problem recurs if EPEL is again disabled. This is a problem as I installed MariaDB from EPEL.

 

Perhaps extend Step 2a in the installation instructions to run the correct command that will prefer zabbix repo for zabbix components, as EPEL seems to be taking precedence.

Comment by Alan McKinnon [ 2022 Nov 04 ]

I figured out what the 1: prefix is in zabbix packages from EPEL.

It's an Epoch, used to correct issues with version numbers, like if a project had beta versions up to 10.x and they restarted from 1.x for the actual release. So 1:1.0.0 is always greater than 10.x which has an implicit Epoch of 0:  I recall now having to deal with this mess 6 years ago for ansible scripts and it's a complete PITA because an Epoch can never be removed

 

Bottom line - Zabbix-6 from your repos is incompatible with EPEL and the two cannot be used together.

 

You can close this ticket, I have my answer and sorry for the noise.

Comment by Jurijs Klopovskis [ 2022 Nov 04 ]

This is documented here https://www.zabbix.com/documentation/6.0/en/manual/installation/install_from_packages/rhel

Updated download instructions

Generated at Sat Apr 26 05:54:24 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.