EasyApache "Could not ensure pkglist" Error

Each time EasyApache runs, it will compile a list of packages that are required for the options you have selected. The list of packages may include many different names for the same software to account for different naming conventions in the wide variety of operating systems cPanel supports.

When EasyApache stops with an error stating it "Could not ensure pkglist," this indicates that the software update system on your machine is not functioning correctly. It does not matter if your operating system does not provide the packages mentioned, since cPanel attempts to install them one at a time and will ignore those deemed not valid for your OS. The key point of this failure message is to inform you that your software update system appears to be broken to EasyApache.

Although it is impossible to list all possible errors that may arise with the various update systems, the following is a list of common errors and possible solutions:

Error: Cannot open/read repomd.xml file for repository ... No more mirrors to try.

Suggestion: This error typically indicates that the mirrors listed in your /etc/yum.repos.d/ are out of date or temporarily unavailable. If the mirrors are in the process of syncing, this issue may correct itself after a short time. If not, you may need to update the list of mirrors Yum is using. Check with your operating system vendor for a more recent repo list.

Error: There was a problem importing one of the Python modules required to run yum. ... Cannot allocate memory

Suggestion: Python frequently runs into the memory limits set inside WHM and cPanel. You may be able to resolve this issue by increasing the per process memory limit in the WHM Tweak Settings feature, or by running EasyApache from the command line to minimize its memory footprint.

Error: up2date error while loading shared libraries ... No such file or directory

Suggestion: This type of error sometimes indicates that the system software has been updated in small pieces rather than as frequent full updates. You may need to manually install the RPMs necessary to get up2date functioning again by locating them on RPMFind.net, your distribution's mirrors, or your installation CDs. Often you can find help in locating the necessary RPMs by searching on your operating system vendor's message boards for the exact text of the error message. Once the library issue is fixed, do a full system update.

Error: Traceback ... ImportError ... cannot open shared object file

Suggestion: This is similar to the up2date error just mentioned. Yum is unable to locate libraries it requires to function correctly. You may need to manually install the RPMs necessary to get Yum functioning again by locating them on RPMFind.net, your distribution's mirrors, or your installation CDs. Often you can find help in locating the necessary RPMs by searching on your operating system vendor's message boards for the exact text of the error message. Once the library issue is fixed, do a full system update.

Error: Traceback ... DatabaseError ... unable to open database file

Suggestion: This occasionally happens when Yum uses cached metadata that has been corrupted. yum clean dbcache may correct this issue.

Error: glibc-common ... is needed by package glibc-dummy-centos-4

Suggestion: This type of error message usually indicates that the glibc-dummy-[distro] -[release] package supplied with your Virtuozzo installation is not up to date with the latest changes provided by your Linux distribution. The glibc-dummy package is installed to save disk space by moving some data into the Virtuozzo template area. It should be safe to uninstall the glibc-dummy package, allowing Yum to upgrade glibc, but it would be better to have your VPS provider upgrade the glibc-dummy package for you. See the following for additional details: http://kb.swsoft.com/en/1010

Error: Missing Dependency ... is needed by package ...

Suggestion: This indicates that the mirrors known to your update system cannot fully fill the dependencies for the selected packages. This may be caused by an operating system library transition that is not yet complete or a delay in synchronization of the update mirrors. It may also indicate that a third-party mirror that was added to your mirror list has not kept up with package changes from your operating system vendor. If you have added third-party mirrors to your update system configuration, removing them may fix this problem. If that is not the case, wait for your operating system vendor to update their mirrors.

Error: Could not find the GPG Key necessary to validate pkg

Suggestion: Many distributions update the GNU Privacy Guard keys they use to sign packages and the package lists on an annual basis. Typically, the new GPG keys are sent out as an update before the old keys expire. If you perform updates infrequently, you may not receive the new keys by the time they are in use signing packages. Check with your operating system vendor to get a new copy of their GPG signing keys.

Error: file /etc/fonts/fonts.conf from install of fontconfig-2.2.3-13.el4 conflicts with file from package fontconfig-2.2.3-7 file /usr/share/man/man5/fonts-conf.5.gz from install of fontconfig-2.2.3-13.el4 conflicts with file from package fontconfig-2.2.3-7

Suggestion: Your OS is suffering from a known bug as outlined at http://bugs.centos.org/view.php?id=1024.

The solution is to fix the errant package, which is different for various systems. This is how it can be done with yum, rpm, or up2date (ALERT! Note: package names, versions, and archtypes may differ — query your package manager as needed to determine what packages to actually manage!):

yum erase fontconfig-2.2.3-7.i386
yum erase fontconfig-2.2.3-7.x86_64
yum update

rpm -e fontconfig-2.2.3-7.i386
rpm -e fontconfig-2.2.3-7.x86_64

up2date fontconfig

Error: No method to auto repair package system

Suggestion : This means that Cpanel::SysPkgs's config check returned a failed status and does not have a way to try to fix what it detected. You will need to manually troubleshoot your OS's update system at this point.

Error: Checking GPG signatures... Unknown signature /var/cache/apt/archives/some_package_here.rpm: (SHA1) DSA sha1 md5 (GPG) NOT OK (MISSING KEYS: GPG#3ab2ce5e)

Suggestion: The system administrator needs to import the key used to sign the packages. See "Could not find the GPG Key necessary to validate pkg" for more information about that.

Error: Package system can not be repaired automatically

Suggestion: This means that Cpanel::SysPkgs's config check returned a failed status and it's attempt to auto fix the problem did not work. You will need to manually fix your OS's update system at this point.


Note

If you are uncertain about which system command is having issues, you can run EasyApache again with some options, in order to see more verbose output. Running EasyApache again will try to rebuild Apache. To do so, you can run either:

From the commmand line: /scripts/easyapache --build --output-syspkg-details

From WHM: https://[Your_IP_Address]:2087/cgi/easyapache.pl?build=1&output-syspkg-details=1

When running with the above options, you will see details about the system call in bold blue letters if an error occurs. Please be sure to capture the entire system command that is failing so that it can be used for troubleshooting purposes.

Topic revision: r4 - 29 Oct 2010 - 12:29:41 - Main.MelanieSeibert