Skip to main content

EasyApache 4 on EL9: AttributeError: 'NoneType' object has no attribute 'version'

Violet Browning
  • Updated

Symptoms

On EL9 servers, accessing the EasyApache 4 tool in WHM reports the following error:

CONFIG_TEXT: Error: API failure: “/usr/bin/python3” reported error code “1” when it ended: Traceback (most recent call last): File "/usr/local/cpanel/bin/packman_get_multiinfo_json", line 74, in packman.get_info_for_packages_and_prefixes( File "/usr/local/cpanel/bin/packman_lib/dnf_impl.py", line 203, in get_info_for_packages_and_prefixes _load_package_info_into_cache_for_packages_and_prefixes(pkglist, prefixes) File "/usr/local/cpanel/bin/packman_lib/dnf_impl.py", line 73, in _load_package_info_into_cache_for_packages_and_prefixes _create_pkg_map_and_package_name_to_possible_objs( File "/usr/local/cpanel/bin/packman_lib/dnf_impl.py", line 118, in _create_pkg_map_and_package_name_to_possible_objs cache_NewestByName[package_name].version AttributeError: 'NoneType' object has no attribute 'version' w/ /usr/local/cpanel/bin/packman_get_multiinfo_json --populate-provides --disable-excludes --prefix ea- Often errors like this can be resolved by running `dnf makecache`

 

Cause

This is caused by invalid package references found in the EasyApache 4 metadata.

 

Resolution

EL9

  1. Clear the dnf/yum cache by running the following command:

    # dnf clean all

  2. Move aside this file:

    # mv -v /etc/cpanel/ea4/is_ea4{,.bak}

  3. Execute:

    # /scripts/ea4_fresh_install

  4. Install the ea-profiles-cpanel package:

    # dnf install ea-profiles-cpanel -y

CloudLinux

  1. Clear the dnf/yum cache by running the following command:

    # dnf clean all

  2. Then move aside this file:

    # mv -v /etc/cpanel/ea4/is_ea4{,.bak}

  3. Then execute:

    # /scripts/ea4_fresh_install

  4. Install the ea-profiles-cpanel package:

    # dnf install ea-profiles-cpanel -y

  5. Install the ea-profiles-cloudlinux package:

    # dnf install ea-profiles-cloudlinux -y

New installs will not be impacted.

Note: If the previous workaround, disabling the EA4 repo was used, please be sure to enable the repo again:
# dnf config-manager --set-enabled EA4

Related articles

Comments

0 comments

Article is closed for comments.

%