yum update produces modular dependencies problems with perl modules
WHM 134, yum updates produces the following errors, how to fix?
Modular dependency problems:
Problem 1: module perl-DBI:1.641:8100020260921064825:0ccef39c.x86_64 from appstream requires module(perl:5.30), but none of the providers can be installed
- module perl:5.26:8020020201210074505:9edba152.x86_64 from appstream conflicts with module(perl:5.30) provided by perl:5.30:8040020210422110935:466ea64f.x86_64 from appstream
- module perl:5.30:8040020210422110935:466ea64f.x86_64 from appstream conflicts with module(perl:5.26) provided by perl:5.26:8020020201210074505:9edba152.x86_64 from appstream
- conflicting requests
Problem 2: module perl:5.24:8010020191121213830:3af8e029.x86_64 from appstream conflicts with module(perl:5.26) provided by perl:5.26:8020020201210074505:9edba152.x86_64 from appstream
- module perl:5.26:8020020201210074505:9edba152.x86_64 from appstream conflicts with module(perl:5.24) provided by perl:5.24:8010020191121213830:3af8e029.x86_64 from appstream
- module perl-DBI:1.641:8100020260921064832:082fdf2f.x86_64 from appstream requires module(perl:5.24), but none of the providers can be installed
- module freeradius:3.0:8080020230403133937:fbe42456.x86_64 from appstream requires module(perl:5.26), but none of the providers can be installed
- conflicting requests
Problem 3: module perl-DBI:1.641:8100020260921064910:dbc5bc9a.x86_64 from appstream requires module(perl:5.32), but none of the providers can be installed
- module perl:5.26:8020020201210074505:9edba152.x86_64 from appstream conflicts with module(perl:5.32) provided by perl:5.32:8100020240409203632:9edba152.x86_64 from appstream
- module perl:5.32:8100020240409203632:9edba152.x86_64 from appstream conflicts with module(perl:5.26) provided by perl:5.26:8020020201210074505:9edba152.x86_64 from appstream
- module perl:5.26:8020020201210074505:9edba152.x86_64 from appstream conflicts with module(perl:5.32) provided by perl:5.32:8100020260415070457:9edba152.x86_64 from appstream
- module perl:5.32:8100020260415070457:9edba152.x86_64 from appstream conflicts with module(perl:5.26) provided by perl:5.26:8020020201210074505:9edba152.x86_64 from appstream
- module perl:5.26:8020020201210074505:9edba152.x86_64 from appstream conflicts with module(perl:5.32) provided by perl:5.32:8100020260629123440:9edba152.x86_64 from appstream
- module perl:5.32:8100020260629123440:9edba152.x86_64 from appstream conflicts with module(perl:5.26) provided by perl:5.26:8020020201210074505:9edba152.x86_64 from appstream
- module perl:5.26:8020020201210074505:9edba152.x86_64 from appstream conflicts with module(perl:5.32) provided by perl:5.32:8100020260731152400:103a1005.x86_64 from appstream
- module perl:5.32:8100020260731152400:103a1005.x86_64 from appstream conflicts with module(perl:5.26) provided by perl:5.26:8020020201210074505:9edba152.x86_64 from appstream
- module perl:5.26:8020020201210074505:9edba152.x86_64 from appstream conflicts with module(perl:5.32) provided by perl:5.32:8100020260915091055:103a1005.x86_64 from appstream
- module perl:5.32:8100020260915091055:103a1005.x86_64 from appstream conflicts with module(perl:5.26) provided by perl:5.26:8020020201210074505:9edba152.x86_64 from appstream
- module freeradius:3.0:8100020240731125246:fbe42456.x86_64 from appstream requires module(perl:5.26), but none of the providers can be installed
- conflicting requests
-
Got the same, in CloudLinux 8 servers, cPanel/WHM 136.0.40
I created a ticket.0 -
quietFinn Thanks for replying, glad it isn't just me, and its happening on multiple cpanel servers. Maybe cPRex can check on this...
0 -
I'm also getting an error during a clean cPanel installation. The installation completes, but cPanel doesn't work. (Almalinux 8 os)
[/usr/local/cpanel/scripts/update-packages] Modular dependency problems:
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages]
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] Problem 1: module perl-DBI:1.641:8100 020260921064825:0ccef39c.x86_64 from appstream requires module(perl:5.30), but none of the providers can be install ed
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - module perl:5.26:80200202012100745 05:9edba152.x86_64 from appstream conflicts with module(perl:5.30) provided by perl:5.30:8040020210422110935:466ea6 4f.x86_64 from appstream
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - module perl:5.30:80400202104221109 35:466ea64f.x86_64 from appstream conflicts with module(perl:5.26) provided by perl:5.26:8020020201210074505:9edba1 52.x86_64 from appstream
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - conflicting requests
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] Problem 2: module perl:5.24:801002019 1121213830:3af8e029.x86_64 from appstream conflicts with module(perl:5.26) provided by perl:5.26:802002020121007450 5:9edba152.x86_64 from appstream
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - module perl:5.26:80200202012100745 05:9edba152.x86_64 from appstream conflicts with module(perl:5.24) provided by perl:5.24:8010020191121213830:3af8e0 29.x86_64 from appstream
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - module perl-DBI:1.641:810002026092 1064832:082fdf2f.x86_64 from appstream requires module(perl:5.24), but none of the providers can be installed
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - module freeradius:3.0:808002023040 3133937:fbe42456.x86_64 from appstream requires module(perl:5.26), but none of the providers can be installed
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - conflicting requests
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] Problem 3: module perl-DBI:1.641:8100 020260921064910:dbc5bc9a.x86_64 from appstream requires module(perl:5.32), but none of the providers can be install ed
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - module perl:5.26:80200202012100745 05:9edba152.x86_64 from appstream conflicts with module(perl:5.32) provided by perl:5.32:8100020240409203632:9edba1 52.x86_64 from appstream
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - module perl:5.32:81000202404092036 32:9edba152.x86_64 from appstream conflicts with module(perl:5.26) provided by perl:5.26:8020020201210074505:9edba1 52.x86_64 from appstream
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - module perl:5.26:80200202012100745 05:9edba152.x86_64 from appstream conflicts with module(perl:5.32) provided by perl:5.32:8100020260415070457:9edba1 52.x86_64 from appstream
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - module perl:5.32:81000202604150704 57:9edba152.x86_64 from appstream conflicts with module(perl:5.26) provided by perl:5.26:8020020201210074505:9edba1 52.x86_64 from appstream
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - module perl:5.26:80200202012100745 05:9edba152.x86_64 from appstream conflicts with module(perl:5.32) provided by perl:5.32:8100020260629123440:9edba1 52.x86_64 from appstream
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - module perl:5.32:81000202606291234 40:9edba152.x86_64 from appstream conflicts with module(perl:5.26) provided by perl:5.26:8020020201210074505:9edba1 52.x86_64 from appstream
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - module perl:5.26:80200202012100745 05:9edba152.x86_64 from appstream conflicts with module(perl:5.32) provided by perl:5.32:8100020260731152400:103a10 05.x86_64 from appstream
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - module perl:5.32:81000202607311524 00:103a1005.x86_64 from appstream conflicts with module(perl:5.26) provided by perl:5.26:8020020201210074505:9edba1 52.x86_64 from appstream
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - module perl:5.26:80200202012100745 05:9edba152.x86_64 from appstream conflicts with module(perl:5.32) provided by perl:5.32:8100020260915091055:103a10 05.x86_64 from appstream
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - module perl:5.32:81000202609150910 55:103a1005.x86_64 from appstream conflicts with module(perl:5.26) provided by perl:5.26:8020020201210074505:9edba1 52.x86_64 from appstream
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - module freeradius:3.0:810002024073 1125246:fbe42456.x86_64 from appstream requires module(perl:5.26), but none of the providers can be installed
[2026-09-21 22:44:36 +0300] [/usr/local/cpanel/scripts/update-packages] - conflicting requests0 -
It looks like the following is the fix:
dnf module reset perl-DBI perl
dnf module enable perl:5.26
dnf update --assumeno
dnf updateLet me know if that doesn't do the trick!
0 -
That didnt help for me.
EDIT:
Apparently that fix works, "dnf update" works, but those "Modular dependency problems:" lines are still there.0 -
quietFinn - let's see what else they say in your ticket.
0 -
cPRex your 4 DNF commands did allow me to update perl-DBI; however all the other errors with "stream conflicts" in my original post still exist.
0 -
cPRex - ticket #96082604
0 -
cPRex This is resolved now without any other intervention from me, yum updates are working again now, what was the fix?
0 -
techguide - we haven't released an update related to this area so it wasn't anything on our side.
0 -
Any update on ticket #96082604?
0 -
The same thing happened in that ticket - the nightly update corrected the issue.
cPanel didn't do a release last night for any version, so it's not something we changed on our side to resolve it.
0 -
Interesting that the nightly update cleared it without any new cPanel release. That makes the timing of the repository metadata or module streams seem pretty important here.
Since the same issue affected multiple servers and then resolved on its own, it would be useful to know whether the nightly update refreshed the AppStream metadata or changed something on the repository side. That could help explain why the DNF reset commands only partially addressed the errors at first.
0
Please sign in to leave a comment.
Comments
13 comments