Red Hat Package Manager, more commonly referred to as RPM for short, allows users to deploy files faster and with much more ease. This system creates standards and regulations involving software installation, including how one can install software on a system. cPanel and WHM servers already come with several pre-installed RPMs, but you still have the option to get more. Also, RPMs make it easier to update your systems.
Although it makes the lives of webmasters and web owners a lot easier, RPM installation can still fail at times. Knowing more about these problems you may face will allow you to approach it with more confidence and resolve it quickly.
Error No. 1: “The no package available”
A common RPM-related error, “The no package available” error occurs when a file called “/etc/yum.conf” does not include a required update package, or when your server does not have the necessary package for installation. A common situation wherein this error occurs is the absence of wget package.
Here are the steps to troubleshoot this problem:
Error No. 2: “The package is obsoleted”
This error usually takes place because of conflicts between RPMS and another entity, usually a third-party repository. When this issue occurs, the RPM installation may fail when the system considers the package obsolete. An example is when the system categorizes the curl-devel package as “obsolete.”
For troubleshooting this error, follow these steps:
Error No. 3: Conflicts with the RPM itself
Rouge RPMs can also develop in the repository. Basically, these refers to RPMs in the update log of the system’s not matching similar RPMs contained in the repository. These rouge RPMs can lead to installation failures. For example, problems with the MySQL RPM can cause an unsuccessful installation process.
For the troubleshooting of this particular problem, try these steps:
RPM plays important roles in your day-to-day cPanel and WHM tasks, so make sure it works optimally and troubleshoot issues right away.