Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
maxLevel2
stylenone

Overview

This document provides examples of common RPM installation failures. You can use these examples to help identify and resolve issues that you may encounter when you install RPMs.

Warning
titleImportant:

This document only applies to installation failures for operating system-related RPMs. This document does not include information for RPMs that The rpm.versions System controls.

  • To install operating system packages, use WHM's Install an RPM interface (WHM >> Home >> Software >> Install an RPM).
  • To change how your server processes updates for these packages, use the Operating System Package Updates section of WHM's Update Preferences interface (WHM >> Home >> Server Configuration >> Update Preferences).


Note
titleNote:

If you continue to experience problems with the RPM installation process after you review this document, open a support ticket.

The no package available error

If the /etc/yum.conf file excludes a required package from updates, or a package does not exist on your server, the installation process fails.

Localtab Group


Localtab
titleError

In this example, the absence of the wget package causes the installation to fail:

Code Block
languagetext
linenumberstrue
[20130131.123334]   Setting up Install Process
[20130131.123334]   No package wget available.
[20130131.123335]   Nothing to do
[20130131.123339] E Sysup: Needed system RPMs were not installed: wget
[20130131.123339] ***** FATAL: Cannot proceed. Needed system RPMs were not installed.
[20130131.123339]   The Administrator will be notified to review this output when this script completes
[20130131.123339] E Detected events which require user notification during updatenow. Will send iContact the log
=> Log closed Thu Jan 31 12:33:39 2013
[20130131.123339]
 E Running `/usr/local/cpanel/scripts/updatenow --upcp 
--log=/var/cpanel/updatelogs/update.1359657200.log` failed, exited with 
code 4608
=> Log closed Thu Jan 31 12:33:39 2013



Localtab
titleTroubleshoot

To troubleshoot this issue, perform the following steps:

  1. Open the /etc/yum.conf file with a text editor and remove the required package from the exclude line. For example:

    Code Block
    exclude=bind-chroot courier* dovecot* exim* filesystem httpd* mod_ssl* mydns* mysql* nsd* perl* php* proftpd* pure-ftpd* ruby* spamassassin* squirrelmail*


  2. Save your changes and run the RPM installation process again.


The package is obsoleted error

This error generally occurs due to conflicts that exist between the RPMs and a third-party repository. An RPM installation may fail if the system classifies a package as obsolete.

Localtab Group


Localtab
titleError

In this example, the system classifies the curl-devel package as obsolete:

Code Block
linenumberstrue
[20130208.081257]   Setting up Install Process
[20130208.081257]  
 Package curl-devel is obsoleted by libcurl-devel, trying to install 
libcurl-devel-7.21.7-5.el5.remi.2.x86_64 instead
[20130208.081257]   Package libcurl-devel-7.21.7-5.el5.remi.2.x86_64 already installed and latest version
[20130208.081257]  
 Package curl-devel is obsoleted by libcurl-devel, trying to install 
libcurl-devel-7.21.7-5.el5.remi.2.x86_64 instead
[20130208.081257]   Package libcurl-devel-7.21.7-5.el5.remi.2.x86_64 already installed and latest version
[20130208.081257]   Nothing to do
[20130208.081258] E Sysup: Needed system RPMs were not installed: curl-devel
[20130208.081258] ***** FATAL: Cannot proceed. Needed system RPMs were not installed.
[20130208.081258]   The Administrator will be notified to review this output when this script completes
[20130208.081258] E Detected events which require user notification during updatenow. Will send iContact the log
=> Log closed Fri Feb  8 08:12:58 2013
[20130208.081258]
 E Running `/usr/local/cpanel/scripts/updatenow --upcp 
--log=/var/cpanel/updatelogs/update.1360329171.log` failed, exited with 
code 18 (signal = 0)



Localtab
titleTroubleshoot

To troubleshoot this error, perform the following steps:

  1. Run the rpm -qa|grep curl command to determine which third-party curl RPMs exist on your system. The output will resemble the following example:

    Code Block
    languagetext
    linenumberstrue
    compat-libcurl3-7.15.5-2.el5.remi
    curl-7.15.5-15.el5
    curl-7.21.7-5.el5.remi.2
    libcurl-devel-7.21.7-5.el5.remi.2
    libcurl-7.21.7-5.el5.remi.2


  2. Run the ls /etc/yum.repos.d command to confirm whether your server uses a third-party repository. The output will resemble the following example:

    Code Block
    languagetext
    linenumberstrue
    ./ CentOS-Debuginfo.repo epel.repo remi.repo.save
    ../ CentOS-Media.repo epel-testing.repo
    CentOS-Base.repo CentOS-Vault.repo remi.repo 


  3. Disable the third-party repository that caused the error. To do this, run the following command:

    Code Block
    languagetext
    yum-config-manager --disable repositoryname


    Note
    titleNote:

    In this example, repositoryname represents the third-party repository to disable.


  4. Run the RPM installation process again.


RPM conflicts

RPMs in the system's update log that do not match similar RPMs in the repository are commonly known as "rogue RPMs," and cause the installation process to fail.

Localtab Group


Localtab
titleError

In this example, the MySQL RPM causes the installation process to fail:

Code Block
languagetext
linenumberstrue
[20130128.230346] Testing RPM transaction
[20130128.230348] error: Failed dependencies:
[20130128.230348] MySQL conflicts with *mysql-5.0.77-4.el5_4.2.i386*
[20130128.230348] W Exit Code: 254
[20130128.230348] ***** FATAL: Test install failed: error: Failed dependencies:
[20130128.230348] MySQL conflicts with mysql-5.0.77-4.el5_4.2.i386
[20130128.230348] The Administrator will be notified to review this output when this script completes
[20130128.230348] E Error testing if the RPMs will install: Died at /usr/local/cpanel/scripts/updatenow.static line 12517.
[20130128.230348] E Detected events which require user notification during updatenow. Will send iContact the log



Localtab
titleTroubleshoot

To troubleshoot this error, perform the following steps

  1. Run the rpm qa|grep -i ^mysqlcommand to locate the version of the MySQL RPM in the update log. The output will resemble the following example:

    Code Block
    languagetext
    mysql-5.0.77-4.el5_4.2


  2. Run the previous command on another server and compare the output to the output of the first server, for example:

    Code Block
    languagetext
    linenumberstrue
    MySQL-server-5.5.28-2.cp.1148
    


    Note
    titleNote:

    The difference in RPM versions indicates that the mysql-5.0.77-4.el5_4.2 RPM is a rogue RPM, which is why it conflicts with the MySQL installation.


  3. Remove the "rogue" RPM file, for example:

    Code Block
    languagetext
    rpm -e --nodeps --justdb mysql-5.0.77-4.el5_4.2


  4. Run the RPM installation process again.


Failure to unpack a new package

An RPM installation fails if the update process cannot unpack the new package to the correct location. Binaries that you cannot modify (immutable binaries) cause this error.

Localtab Group


Localtab
titleError

In this example, both the tar and unzip packages cause the installation process to fail:

Code Block
languagetext
linenumberstrue
[20130210.141900]   Running Transaction
[20130210.141903]   
[20130210.141903]   Installing     : gzip                                                     1/3 
[20130210.141903]   
[20130210.141903]  
 Installing     : 
unzip                                                    2/3Error 
unpacking rpm package unzip-5.52-3.el5.i386
[20130210.141903]    
[20130210.141903]   error: unpacking of archive failed on file /usr/bin/unzip: cpio: rename
[20130210.141903]   
[20130210.141903]  
 Installing     : 
tar                                                      3/3Error 
unpacking rpm package 2:tar-1.15.1-32.el5_8.i386
[20130210.141903]    
[20130210.141903]   error: unpacking of archive failed on file /bin/tar: cpio: rename
[20130210.141904]   
[20130210.141904]   Installed:
[20130210.141904]     gzip.i386 0:1.3.5-13.el5.centos                                               
[20130210.141904]   
[20130210.141904]   Failed:
[20130210.141904]     tar.i386 2:1.15.1-32.el5_8               unzip.i386 0:5.52-3.el5              
[20130210.141904]   
[20130210.141904]   Complete!
[20130210.141910]
 E Sysup: Needed system RPMs were not installed: tar, unzip, wget 
[20130210.141910] ***** FATAL: Cannot proceed. Needed system RPMs were 
not installed.
[20130210.141910]   The Administrator will be notified to review this output when this script completes
[20130210.141910] E Detected events which require user notification during updatenow. Will send iContact the log



Localtab
titleTroubleshoot

To troubleshoot this error, perform the following steps:

  1. Run the lsattr /usr/bin/unzip command to determine whether immutable binaries caused this error.
    The following example indicates that the system contains immutable binaries.

    Code Block
    languagetext
    linenumberstrue
    ----i-------- /usr/bin/unzip
    ----i-------- /bin/tar


  2. Remove the immutable flags. To do this, run the following commands:

    Code Block
    languagetext
    linenumberstrue
    chattr -i /usr/bin/unzip
    chattr -i /bin/tar


  3. Run the RPM installation process again.


The Your RPM database appears unstable error

An RPM installation fails if the destination directory is immutable or full.

Localtab Group


Localtab
titleError

In this example, any attempt to install an RPM causes the installation process to fail.

Code Block
languagetext
linenumberstrue
[root@read-only ~]# /scripts/upcp --force
[2017-07-21 12:20:48 -0500]   Checking that the RPM DB is 
OK...
[2017-07-21 12:20:48 -0500]   glibc-2.17-157.el7_3.4.x86_64
[2017-07-21 12:20:48 -0500]   OK: RPM DB is responding to 
queries
[2017-07-21 12:20:48 -0500] Testing if rpm_is_working RPM is installed
[2017-07-21 12:20:48 -0500] package rpm_is_working is not installed
[2017-07-21 12:20:48 -0500] Testing if it's possible to install a simple RPM
[2017-07-21 12:20:48 -0500] error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Read-only file system)
[2017-07-21 12:20:48 -0500] The RPM did not appear to install.
[2017-07-21 12:20:48 -0500] W Your RPM database appears unstable. It is not possible at the moment to install any RPMs.
Your RPM database appears unstable. It is not possible at the moment to install any RPMs. at /scripts/upcp line 866.



Localtab
titleTroubleshoot

To troubleshoot this error, perform either of the following actions:


Additional documentation

Localtab Group


Localtab
activetrue
titleSuggested documentation

Content by Label
showLabelsfalse
max5
showSpacefalse
cqllabel = "rpms" and label = "whm" and space = currentSpace()


Localtab
titleFor cPanel users

Content by Label
showLabelsfalse
max5
showSpacefalse
cqllabel = "rpms" and label = "cpanel" and space in ("DOC",currentSpace())


Localtab
titleFor WHM users

Content by Label
showLabelsfalse
max5
showSpacefalse
cqllabel = "rpms" and label = "whm" and space in (currentSpace(),"DOC")


Localtab
titleFor developers

Content by Label
showLabelsfalse
max5
showSpacefalse
cqllabel = "rpms" and space = "DD"