Skip to main content

CloudLinux OS 10 package repositories do not yet provide ea-podman, preventing installation of cpanel-meridian-plugin + cpanel-webapp-plugin and thus also logging an error/failure during scripts/upcp

🕵️🍌🅳🫆🔍

Summary

CloudLinux OS 10 package repositories, presumably for EasyApache (EA), appear to not yet provide ea-podman, preventing installation of cPanel-supplied packages cpanel-meridian-plugin & cpanel-webapp-plugin.  The package dependency issue is causing /usr/local/cpanel/scripts/check_plugin_pkgs to be unable to install the aforementioned cPanel-supplied plugin packages during automatic execution by /usr/local/cpanel/scripts/upcp and thus also can trigger a notification to configured server administrator contact(s).

Environment

# grep -EH . /etc/{alma,cloud}linux-release /usr/local/cpanel/version
/etc/almalinux-release:AlmaLinux release 10.2 (Lavender Lion)
/etc/cloudlinux-release:CloudLinux release 10
/usr/local/cpanel/version:11.138.0.6
# cat /etc/cpupdate.conf
CPANEL=edge
RPMUP=daily
SARULESUP=daily
SECURITY_UPDATES=hourly
STAGING_DIR=/usr/local/cpanel
UPDATES=daily

 

Testing steps

/usr/local/cpanel/scripts/upcp --cron

and/or

/usr/local/cpanel/scripts/check_plugin_pkgs --pkg cpanel-analytics --pkg cpanel-banners-plugin --pkg cpanel-bannerx-plugin --pkg cpanel-comet-backup-plugin --pkg cpanel-koality-plugin --pkg cpanel-meridian-plugin --pkg cpanel-monitoring-plugin --pkg cpanel-sitejet-plugin --pkg cpanel-socialbee-plugin --pkg cpanel-xovi-plugin; echo $?

 

Expected result

No errors/warnings and exit return code is zero (0) from the execution of /usr/local/cpanel/scripts/check_plugin_pkgs by /usr/local/cpanel/scripts/upcp

 

Actual result

An error due to a missing package dependency and a non-zero exit return code from the execution of /usr/local/cpanel/scripts/check_plugin_pkgs by /usr/local/cpanel/scripts/upcp

* Checking package ‘cpanel-meridian-plugin’
Package 'cpanel-meridian-plugin' is not installed, attempting to install it …

cPanel Plugins project                           25 kB/s | 2.9 kB     00:00
Error:
 Problem: package cpanel-meridian-plugin-1.3.3-1.2.1.cpanel.noarch from cpanel-plugins requires cpanel-webapp-plugin >= 1.3.1, but none of the providers can be installed
  - cannot install the best candidate for the job
  - nothing provides ea-podman >= 1.0-27 needed by cpanel-webapp-plugin-1.3.1-1.1.1.cpanel.noarch from cpanel-plugins
  - nothing provides ea-podman >= 1.0-27 needed by cpanel-webapp-plugin-1.3.1-1.2.1.cpanel.noarch from cpanel-plugins
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
Issue detected with package ‘cpanel-meridian-plugin’Cpanel::Exception::ProcessFailed::Error/(XID 4c9tqa) “/usr/bin/yum” reported error code “1” when it ended:
 at /usr/local/cpanel/Cpanel/ChildErrorStringifier.pm line 161.
 Cpanel::ChildErrorStringifier::to_exception(Cpanel::SafeRun::Object=HASH(0x39ea4540)) called at /usr/local/cpanel/Cpanel/SafeRun/Object.pm line 696
 Cpanel::SafeRun::Object::to_exception(Cpanel::SafeRun::Object=HASH(0x39ea4540)) called at /usr/local/cpanel/Cpanel/ChildErrorStringifier.pm line 140
 Cpanel::ChildErrorStringifier::die_if_error(Cpanel::SafeRun::Object=HASH(0x39ea4540)) called at /usr/local/cpanel/Cpanel/SysPkgs/YUM.pm line 912
 Cpanel::SysPkgs::YUM::_die_child_error(Cpanel::SafeRun::Object=HASH(0x39ea4540), "Error: \x{a} Problem: package cpanel-meridian-plugin-1.3.3-1.2.1."..., "packages", ARRAY(0x39e8c280), "exclude", ARRAY(0x39e8c310), "_args", ARRAY(0x39861860)) called at /usr/local/cpanel/Cpanel/SysPkgs/YUM.pm line 897
 Cpanel::SysPkgs::YUM::_exec_yum(Cpanel::SysPkgs::DNF=HASH(0x3a17da60), "packages", ARRAY(0x39e8c280), "exclude", ARRAY(0x39e8c310), "_args", ARRAY(0x39861860)) called at /usr/local/cpanel/Cpanel/SysPkgs/YUM.pm line 815
 Cpanel::SysPkgs::YUM::_call_yum(Cpanel::SysPkgs::DNF=HASH(0x3a17da60), "packages", ARRAY(0x39e8c280), "exclude", ARRAY(0x39e8c310)) called at /usr/local/cpanel/Cpanel/SysPkgs/YUM.pm line 154
 Cpanel::SysPkgs::YUM::install_packages(Cpanel::SysPkgs::DNF=HASH(0x3a17da60), "packages", ARRAY(0x39e8c280)) called at /usr/local/cpanel/Cpanel/Plugins.pm line 102
 Cpanel::Plugins::install_plugins("cpanel-meridian-plugin") called at /usr/local/cpanel/scripts/check_plugin_pkgs line 88
 scripts::check_plugin_pkgs::check_pkg(scripts::check_plugin_pkgs=HASH(0x38c7fff8), "cpanel-meridian-plugin") called at /usr/local/cpanel/scripts/check_plugin_pkgs line 58
 eval {...} called at /usr/local/cpanel/scripts/check_plugin_pkgs line 58
 scripts::check_plugin_pkgs::script(scripts::check_plugin_pkgs=HASH(0x38c7fff8)) called at /usr/local/cpanel/scripts/check_plugin_pkgs line 41

&

E    [/usr/local/cpanel/scripts/check_plugin_pkgs] The “/usr/local/cpanel/scripts/check_plugin_pkgs --pkg cpanel-analytics --pkg cpanel-banners-plugin --pkg cpanel-bannerx-plugin --pkg cpanel-comet-backup-plugin --pkg cpanel-koality-plugin --pkg cpanel-meridian-plugin --pkg cpanel-monitoring-plugin --pkg cpanel-sitejet-plugin --pkg cpanel-socialbee-plugin --pkg cpanel-xovi-plugin” command (process 849635) reported error number 1 when it ended.
  The Administrator will be notified to review this output when this script completes
   - Finished command `/usr/local/cpanel/scripts/check_plugin_pkgs --pkg cpanel-analytics --pkg cpanel-banners-plugin --pkg cpanel-bannerx-plugin --pkg cpanel-comet-backup-plugin --pkg cpanel-koality-plugin --pkg cpanel-meridian-plugin --pkg cpanel-monitoring-plugin --pkg cpanel-sitejet-plugin --pkg cpanel-socialbee-plugin --pkg cpanel-xovi-plugin` in 51.464 seconds

E Pre Maintenance ended, however it did not exit cleanly (256). The following events were logged: "scripts/check_plugin_pkgs". Please check the logs for an indication of what happened

Comments

3 comments

Date Votes
  • cPRex Jurassic Moderator

    Hey there!  Could you let me know the mirror that your downloads are coming from for the update?  We aren't expecting this behavior to happen and I'm wondering if there is a specific mirror that may be out of sync, leading to this issue.

    0
  • 🕵️🍌🅳🫆🔍
    • Edited

    Thank you for the reply.  As a status update, as best I can gather thus far, the reported symptoms I experienced appear to stem from a possible technical mistake on my end made during initial installation back in January 2026.  Specifically, I learned the cPanel EA4 DNF/YUM repository was not properly installed and enabled for whatever reason.  According to the cPanel install log, this system was provisioned on 2026-01-30, which I think may have been before subsequent cpanel-installer and/or cldeploy improvements & bug-fixes that I believe have since ironed out any kinks and refined the experience of setting up a new cPanel server on AlmaLinux OS v10 & immediately converting to CloudLinux OS v10.  I wish I could recall what order of steps the overall setup process was manually performed in, like if I ran cldeploy before the cpanel installer, or if I ran cldeploy after the cpanel installer.  I just recall I ran into various technical difficulties at the time that I believe were specific to the OS, ~EL v10, and somehow managed to make it mostly work at that time.  If I had to guess, I would suspect a manual workaround attempted probably disabled the cPanel EA4 repository while under the mistaken impression that the server should have only the CloudLinux EA4 repository installed for all EA4 packages.

    The learning experience for me as of today is that I did not realize the CloudLinux EA4 package repository is now able to coexist simultaneously with the cPanel EA4 package repository.  Making certain the cPanel EA4 repository is installed and fully enabled appears to have entirely corrected all the issue symptoms experienced.

    0
  • cPRex Jurassic Moderator

    I'm glad to hear that's all it took!

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post