Error package ea-apache24-mod_lsapi-1:1.1-92.el8.cloudlinux.x86_64

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • paul
    Junior Member
    Forum Explorer
    • Mar 2021
    • 21

    #1

    Error package ea-apache24-mod_lsapi-1:1.1-92.el8.cloudlinux.x86_64

    Getting a problem with the latest update /scripts/upcp


    [2026-06-02 10:25:30 +1000] Processing: Running update-packages
    [2026-06-02 10:25:30 +1000] - Processing command `/usr/local/cpanel/scripts/update-packages`
    [2026-06-02 10:25:31 +1000] [/usr/local/cpanel/scripts/update-packages] checkyum version 22.3
    [2026-06-02 10:25:33 +1000] [/usr/local/cpanel/scripts/update-packages] excludes: bind-chroot dovecot* exim* filesystem kernel kernel-xen kernel-smp kernel-pae kernel-PAE kernel-SMP kernel-hugemem kernel-debug* kernel-core kernel-modules* kernel-devel* kmod-[a-z]* p0f php* proftpd* pure-ftpd*
    [2026-06-02 10:25:33 +1000] [/usr/local/cpanel/scripts/update-packages] Last metadata expiration check: 0:07:05 ago on Tue Jun 2 10:18:26 2026.
    [2026-06-02 10:25:33 +1000] [/usr/local/cpanel/scripts/update-packages] Error:
    [2026-06-02 10:25:33 +1000] [/usr/local/cpanel/scripts/update-packages] Problem: cannot install the best update candidate for package ea-apache24-mod_lsapi-1:1.1-92.el8.cloudlinux.x86_64

    Now getting contant notifications - (XID ktadbq) The "Apache PHP-FPM alt-74" service is down. The subprocess "/usr/local/cpanel/scripts/restartsrv_apache_php_fpm" reported error number 29 when it ended.

    CloudLinux v8.10.0 cPanel 134.0.34

    Any help appreciated
  • bogdan.sh
    Administrator
    • Nov 2016
    • 1305

    #2
    Hi,

    This is a temporary side-effect of the Gradual Rollout system, not a broken package. The newer ea-apache24-mod_lsapi-1.1-94 has already landed in your EA4 rollout slot, but the two dependencies it needs - criu-lve >= 4.2-1 and liblsapi >= 1.1-94 - haven't been promoted to the matching stable repo on your server yet (they're currently in the testing/rollout channel). yum sees the new module but can't pull its deps from the same place, so it stops.

    You've got two safe options:

    1. Just wait. Once those deps finish rolling out to stable, a normal yum update will pick the whole set up with no flags. If you don't want to touch anything during business hours, this is fine — nothing is broken in the meantime.

    2. Update the set now by letting the matching versions come from the CloudLinux repos in one go:


    Code:
    yum update ea-apache24-mod_lsapi criu* liblsapi* --enablerepo=cl*
    The "Apache PHP-FPM alt-74 service is down" notices should settle once mod_lsapi and its deps are aligned again - if they persist after the update, run /scripts/restartsrv_apache_php_fpm and let me know.

    Cheers​

    Comment

    Working...