Error unpacking rpm package

Centos7 :: Error unpacking rpm package httpd-2.4.6-40.el7.centos.1.x86_64 #725

I have to build an Image Docker for the solution of my company.
This Image have to contains some dependencies and have to based on centos7. Among these dependencies, there is httpd.

So, I built an image of CentOS 7 with systemd with this Dockerfile according to these explainations : https://hub.docker.com/_/centos/

ENV container docker

RUN (cd /lib/systemd/system/sysinit.target.wants/; for i in *;
do [ $i == systemd-tmpfiles-setup.service ] || rm -f $i; done);
rm -f /lib/systemd/system/multi-user.target.wants/*;
rm -f /etc/systemd/system/*.wants/*;
rm -f /lib/systemd/system/local-fs.target.wants/*;
rm -f /lib/systemd/system/sockets.target.wants/*udev*;
rm -f /lib/systemd/system/sockets.target.wants/*initctl*;
rm -f /lib/systemd/system/basic.target.wants/*;
rm -f /lib/systemd/system/anaconda.target.wants/*;

RUN yum -y install deltarpm && yum clean all
RUN yum -y update && yum clean all
RUN yum -y install vim wget tar && yum clean all

And I push this image on my repository «agilium/centos7» And I wrote an other Dockerfile for httpd according to the same explainations : My httpd/Dockerfile

RUN yum -y update && yum clean all
RUN yum -y install httpd; yum clean all; systemctl enable httpd.service

And I have this error when I built my image :

I also tried to localinstall the rpm package, but with the same error, like this :

COPY ./install/* ./install/
RUN yum -y localinstall ./install/httpd-2.4.6-40.el7.centos.1.x86_64.rpm

I search for solutions and I find this issue #461 but it seems there was no solution found and the problem has solved itself. =/

Thanks for help.

The text was updated successfully, but these errors were encountered:

Источник

RPM Error Unpacking of Archive Failed on File – Let’s fix it!!

by Sharon Thomas | Jan 20, 2020

Are you stuck with the RPM Error Unpacking of Archive Failed on File? We can help you.

Usually, the error message occurs when the system fails to install the RPM command.

At Bobcares, we often get requests regarding RPM errors, as a part of our Server Management Services.

Today, let’s see how our Support Engineers fix the RPM error for our customers.

Explore more about RPM

RPM is the Red Hat Package Manager. To install packages under Linux systems we use RPM. The RPM package contains an arbitrary set of files like binary RPMs and source RPMs.

The source RPMs build the binary package and the binary RPMs is the compiled version of some software.

To install, upgrade or remove the programs on the Linux system, we use rpm command.

How to fix RPM Error Unpacking of Archive Failed on File?

Recently, one of our customers approached us with the same error. Now, let’s discuss how our Support Engineers fix the error for our customers.

Read Failed Error

The cpio is an archive utility and the cpio: read failed error means that the installing package is corrupt.

To fix the error our Support Engineers follow the below steps.

1. Initially, we download the package from a reliable source.

2. Then we compare the size and md5sum of the RPM copy on the system.

If there is a difference in the checksum then we do a fresh download of the RPM package from the reliable source.

Here we use the wget command to download the package file directly to the server.

Open Failed Error

Another customer approached us saying that he is getting an open fail error while installing the package using rpm command.

This error occurs if an attribute is set on the directory.

So, we use the lsattr command to check if an attribute is set on the directory.

The i indicates that the attribute is set for the file. So that we cannot alter, rename or delete the file. To fix the error, we remove the immutable bit by using the ‘chattr’ command.

After removing the attribute bit we successfully installed the RPM package. But in some cases removing the attribute bit not fixes the error.

The reason is that the RPM file is corrupt. In such cases, we download the package again to fix the unpacking of archive error.

[Need assistance to fix RPM error? – We’ll help you.]

Conclusion

In short, today we discussed in detail on RPM Error Unpacking of Archive Failed on File and saw how our Support Engineers find the fix for this error.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

Источник

LinuxHostingSupport

error: unpacking of archive failed on file /usr/bin/xxxx: cpio: open Failed

The error message “unpacking of archive failed on file /usr/bin/xxxx: cpio: open Failed” indicates that the system failed to install the rpm since it cannot unpack the package under the /usr/bin directory.

For example, you may see the error message as stated below while installing a ‘nano’ package using yum

This indicates that the file /usr/bin/nano cannot be created under the /usr/bin directory which mostly happens if an attribute is set on the directory.

Use the ‘lsattr’ command to check if an attribute is set on the directory:

If the file/directory have an immutable bit (lowercase ‘i’) set as shown in the above output, it indicates that the permissions to write in the file/directory has been denied.

To remove the immutable bit, use the ‘chattr’ command:

Once done, you can successfully install the rpm.

Important:

In some cases though, the rpm file itself is corrupt and cannot be installed, so it is also recommended to try install the rpm on another server to see if it works. If it fails on another server too, you should download the package from a different website / mirror.

3 Responses to “error: unpacking of archive failed on file /usr/bin/xxxx: cpio: open Failed”

I got the same error, but I ran ‘lsattr -d /usr/bin’ and the ‘i’ flag was not set. Any idea what else could be wrong?

I am able to rename a file in /usr/bin using mv, but writing to any file using ‘echo bla >/usr/bin/bla’ gives me a “Invalid argument” error.

I found my problem: SELinux was failing because I had mounted /var/log from a ramdisk after I installed an SSD, and so the /var/log/setroubleshoot directory was missing.

I removed the mount for /var/log from /etc/fstab, since I figured I might want to look at the logs after reboot anyway, and now everything is working fine.

Thank you for your feedback. It will definitely help others.

Источник

Error unpacking rpm package

Did you find this document helpful?

Would you like to provide more feedback on this document?

Table of Contents

RPM Installation Failures

Last modified: August 25, 2022

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.

This document only applies to installation failures for operating system-related RPMs on Red Hat-based servers. This document does not include information for RPMs that The rpm.versions System controls or for packages on servers running the UbuntuВ® operating system.

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).

To scan your installed cPanel-managed packages for problems, use the /usr/local/cpanel/scripts/check_cpanel_pkgs script. You can also use this script to reinstall cPanel & WHM packages that are out-of-date or altered.

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.

The no package available error Error

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

Troubleshoot The no package available error

To troubleshoot this issue, perform the following steps:

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

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.

The package is obsoleted error Error

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

Troubleshoot The package is obsoleted error

To troubleshoot this error, perform the following steps:

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:

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:

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

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

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.

RPM conflicts Error

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

Troubleshoot RPM conflicts

To troubleshoot this error, perform the following steps

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

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

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.

Remove the “rogue” RPM file. For example:

Run the RPM installation process again.

RPM package file conflicts

An RPM installation can fail if there are package file conflicts. This can occur when a previous RPM file isn’t removed from the system. You must remove any conflicting files before you can successfully install an RPM.

RPM package file conflicts Error

In this example, the clamav-0.100.3-1.el6.x86_64 file conflicts with the RPM package file:

Troubleshoot RPM package file conflicts

To troubleshoot this error, perform the following steps:

Run the rpm -qa | grep -i clamav command to locate the version of the ClamAV RPM in the update log. The output will resemble the following example:

Run the rpm -qa | grep -i clamav command on another server. Compare the output to the output of the first server. For example:

Remove the conflicting RPM file. For example:

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.

Failure to unpack a new package Error

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

Troubleshoot Failure to unpack a new package

To troubleshoot this error, perform the following steps:

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:

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

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.

The Your RPM database appears unstable error Error

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

Troubleshoot The Your RPM database appears unstable error

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

Rebuild the RPM database in WHM’s Rebuild RPM Database interface (WHM » Home » Software » Rebuild RPM Database).

Источник

why does yum/rpm update fails with unpacking of archive failed on file /abc/xyz cpio: rename failed — Device or resource busy ?

Environment

Issue

• Installation using yum/rpm fails for updaing packages.

Resolution

1. check if any process is holding the os-release file.

2. Stop the process which is holding the os-release file. If any application is holding the file then check if the application can be stopped. Ask the application team to stop it. Check if the process can be killed with the application team if needed.

Note:- check with the relevant application to kill the process.

3. Update the redhat-release-server package.

Root Cause

• The Docker application was holding the os-release file.

Diagnostic Steps

• The yum/rpm command unable to install/update the redhat-release-server package giving the below error.

• Product(s)
• Red Hat Enterprise Linux

• Component
• redhat-release

• Category
• Install

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Источник

Are you stuck with the RPM Error Unpacking of Archive Failed on File? We can help you.

Usually, the error message occurs when the system fails to install the RPM command.

At Bobcares, we often get requests regarding RPM errors, as a part of our Server Management Services.

Today, let’s see how our Support Engineers fix the RPM error for our customers.

Explore more about RPM

RPM is the Red Hat Package Manager. To install packages under Linux systems we use RPM. The RPM package contains an arbitrary set of files like binary RPMs and source RPMs.

The source RPMs build the binary package and the binary RPMs is the compiled version of some software.

To install, upgrade or remove the programs on the Linux system, we use rpm command.

How to fix RPM Error Unpacking of Archive Failed on File?

Recently, one of our customers approached us with the same error. Now, let’s discuss how our Support Engineers fix the error for our customers.

Read Failed Error

The cpio is an archive utility and the cpio: read failed error means that the installing package is corrupt.

To fix the error our Support Engineers follow the below steps.

1. Initially, we download the package from a reliable source.

2. Then we compare the size and md5sum of the RPM copy on the system.

ls -l [rpm]

md5sum [rpm]

If there is a difference in the checksum then we do a fresh download of the RPM package from the reliable source.

Here we use the wget command to download the package file directly to the server.

Open Failed Error

Another customer approached us saying that he is getting an open fail error while installing the package using rpm command.

error: unpacking of archive failed on file /xxx/xxx/xxx: cpio: open Failed:

This error occurs if an attribute is set on the directory.

So, we use the lsattr command to check if an attribute is set on the directory.

[root@server ~]# lsattr file
----i----------- file

The i indicates that the attribute is set for the file. So that we cannot alter, rename or delete the file. To fix the error, we remove the immutable bit by using the ‘chattr’ command.

After removing the attribute bit we successfully installed the RPM package. But in some cases removing the attribute bit not fixes the error.

The reason is that the RPM file is corrupt. In such cases, we download the package again to fix the unpacking of archive error.

[Need assistance to fix RPM error? – We’ll help you.]

Conclusion

In short, today we discussed in detail on RPM Error Unpacking of Archive Failed on File and saw how our Support Engineers find the fix for this error.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

441 votes

22 answers

Get the solution ↓↓↓

[[email protected] ~]# dnf module reset php -y
Last metadata expiration check: 0:10:14 ago on Thu 08 Apr 2021 03:32:40 AM +03.
Dependencies resolved.
====================================================================================================================================================================================================================
 Package                                            Architecture                                      Version                                              Repository                                          Size
====================================================================================================================================================================================================================
Resetting modules:
 php

Transaction Summary
====================================================================================================================================================================================================================

Complete!
[[email protected] ~]# dnf module enable php:remi-7.3 -y
Last metadata expiration check: 0:10:27 ago on Thu 08 Apr 2021 03:32:40 AM +03.
Dependencies resolved.
====================================================================================================================================================================================================================
 Package                                            Architecture                                      Version                                              Repository                                          Size
====================================================================================================================================================================================================================
Enabling module streams:
 php                                                                                                  remi-7.3

Transaction Summary
====================================================================================================================================================================================================================

Complete!
[[email protected] ~]# dnf module list php
Last metadata expiration check: 0:10:37 ago on Thu 08 Apr 2021 03:32:40 AM +03.
CentOS-8 - AppStream
Name                                      Stream                                           Profiles                                                       Summary
php                                       7.2 [d]                                          common [d], devel, minimal                                     PHP scripting language
php                                       7.3                                              common [d], devel, minimal                                     PHP scripting language
php                                       7.4                                              common [d], devel, minimal                                     PHP scripting language

CentOS Linux 8 - AppStream
Name                                      Stream                                           Profiles                                                       Summary
php                                       7.2 [d]                                          common [d], devel, minimal                                     PHP scripting language
php                                       7.3                                              common [d], devel, minimal                                     PHP scripting language
php                                       7.4                                              common [d], devel, minimal                                     PHP scripting language

Remi's Modular repository for Enterprise Linux 8 - x86_64
Name                                      Stream                                           Profiles                                                       Summary
php                                       remi-7.2                                         common [d], devel, minimal                                     PHP scripting language
php                                       remi-7.3 [e]                                     common [d], devel, minimal                                     PHP scripting language
php                                       remi-7.4                                         common [d], devel, minimal                                     PHP scripting language
php                                       remi-8.0                                         common [d], devel, minimal                                     PHP scripting language

Hint: [d]efault, [e]nabled, [x]disabled, [i]nstalled
[[email protected] ~]# dnf install -y php php-cli php-common
Last metadata expiration check: 0:10:48 ago on Thu 08 Apr 2021 03:32:40 AM +03.
Package php-7.4.16-1.el8.remi.x86_64 is already installed.
Package php-cli-7.4.16-1.el8.remi.x86_64 is already installed.
Dependencies resolved.
====================================================================================================================================================================================================================
 Package                                           Architecture                                  Version                                                  Repository                                           Size
====================================================================================================================================================================================================================
Installing:
 php-common                                        x86_64                                        7.3.27-1.el8.remi                                        remi-modular                                        1.1 M
Installing dependencies:
 php-json                                          x86_64                                        7.3.27-1.el8.remi                                        remi-modular                                         75 k

Transaction Summary
====================================================================================================================================================================================================================
Install  2 Packages

Total download size: 1.2 M
Installed size: 12 M
Downloading Packages:
(1/2): php-json-7.3.27-1.el8.remi.x86_64.rpm                                                                                                                                        184 kB/s |  75 kB     00:00
(2/2): php-common-7.3.27-1.el8.remi.x86_64.rpm                                                                                                                                      1.4 MB/s | 1.1 MB     00:00

{-code-4}

Write your answer

122

votes

Answer

—
Total 1.1 MB/s | 1.2 MB 00:01
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : php-json-7.3.27-1.el8.remi.x86_64 1/2
Error unpacking rpm package php-json-7.3.27-1.el8.remi.x86_64
Running scriptlet: php-common-7.3.27-1.el8.remi.x86_64 2/2
error: unpacking of archive failed on file /etc/php.d/20-json.ini: cpio: rename failed — Operation not permitted
error: php-json-7.3.27-1.el8.remi.x86_64: install failed
Installing : php-common-7.3.27-1.el8.remi.x86_64 2/2
Error unpacking rpm package php-common-7.3.27-1.el8.remi.x86_64
Verifying : php-common-7.3.27-1.el8.remi.x86_64 1/2
Verifying : php-json-7.3.27-1.el8.remi.x86_64 2/2
Failed:
php-common-7.3.27-1.el8.remi.x86_64 php-json-7.3.27-1.el8.remi.x86_64
Error: Transaction failed
[[email protected] ~]#|||systemctl stop php-fpm httpd|||php|||OS Version: Centos 8
Web Server: Apache 2.4.46

937

votes

Answer

Solution:

The problem solved just by deleting the/etc/php.d/ directory. Then reinstall PHP.

Share solution ↓

Additional Information:

Link To Source

Link To Answer
People are also looking for solutions of the problem: use the option —with-all-dependencies (-w) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Similar questions

Find the answer in similar questions on our website.