How to fix Error unpacking rpm package cpio: open?

A

Alexander2021-10-20 16:39:54

Access rights

Alexander, 2021-10-20 16:39:54

When trying to install / update packages, an error occurs that the package cannot be unpacked because open and symlink.
It is these reasons that do not google.

For example:

Running transaction
  Установка   : python2-certbot-1.11.0-2.el7.noarch                                                                                                                                                            1/2 
Error unpacking rpm package python2-certbot-1.11.0-2.el7.noarch
error: unpacking of archive failed on file /usr/bin/certbot-2;61701b24: cpio: open
  Установка   : certbot-1.11.0-2.el7.noarch                                                                                                                                                                    2/2 
Error unpacking rpm package certbot-1.11.0-2.el7.noarch
error: python2-certbot-1.11.0-2.el7.noarch: install failed
error: unpacking of archive failed on file /usr/bin/certbot;61701b24: cpio: symlink
  Проверка    : certbot-1.11.0-2.el7.noarch                                                                                                                                                                    1/2 
  Проверка    : python2-certbot-1.11.0-2.el7.noarch                                                                                                                                                            2/2 

Неудача:
  certbot.noarch 0:1.11.0-2.el7                                                                        python2-certbot.noarch 0:1.11.0-2.el7

Perhaps the reason is that /usr/bin is not allowed to write:

ls -la /usr/
итого 136
drwxrwxrwx.  13 root root  4096 сен  1 23:31 ./
dr-xr-xr-x.  19 root root  4096 окт 20 16:25 ../
dr-xr-xr-x.   2 root root 36864 сен  1 22:40 bin/

But trying to change permissions results in chmod: changing permissions for "/usr/bin": Operation not allowed

Reply

Answer the question

In order to leave comments, you need to log in

1 answer(s)

V

Vitaly Karasik, 2021-10-20
@vitaly_il1

1) Do you have space on the disk? ("df -h")
2) run chmod as root or via sudo