Issue obsidian update error installed on centos 8

[torefloo]

hello
I'm using plesk obsidian on centos 8, but for the last few days, when I try to update with the yum update -y command, I get the following error;



Package Architecture Version Repository Size
================================================================================
Upgrading:
coreutils x86_64 8.30-12.el8 baseos 1.2 M
perl-interpreter x86_64 4:5.26.3-420.el8 baseos 6.3 M

Transaction Summary
================================================================================
Upgrade 2 Packages

Total download size: 7.5 M
Downloading Packages:
(1/2): coreutils-8.30-12.el8.x86_64.rpm 724 kB/s | 1.2 MB 00:01
(2/2): perl-interpreter-5.26.3-420.el8.x86_64.r 1.2 MB/s | 6.3 MB 00:05
--------------------------------------------------------------------------------
Total 1.4 MB/s | 7.5 MB 00:05
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Upgrading : perl-interpreter-4:5.26.3-420.el8.x86_64 1/4
Error unpacking rpm package perl-interpreter-4:5.26.3-420.el8.x86_64
Upgrading : coreutils-8.30-12.el8.x86_64 2/4
error: unpacking of archive failed on file /usr/bin/perl: cpio: rename failed - Operation not permitted
error: perl-interpreter-4:5.26.3-420.el8.x86_64: install failed

Error unpacking rpm package coreutils-8.30-12.el8.x86_64
Verifying : coreutils-8.30-12.el8.x86_64 1/4
Verifying : coreutils-8.30-8.el8.x86_64 2/4
Verifying : perl-interpreter-4:5.26.3-420.el8.x86_64 3/4
Verifying : perl-interpreter-4:5.26.3-416.el8.x86_64 4/4

Failed:
coreutils-8.30-8.el8.x86_64
coreutils-8.30-12.el8.x86_64
perl-interpreter-4:5.26.3-416.el8.x86_64
perl-interpreter-4:5.26.3-420.el8.x86_64

Error: Transaction failed

 

[Bitpalast]

This issue has been discussed in other current threads several times. CentOS 8 was end of life at the end of 2021. The repositories are no longer accessible in their original path. In order to keep using Plesk you need to migrate your CentOS 8 to AlmaLinux. You can find a script and instructions how to do that here: GitHub - AlmaLinux/almalinux-deploy: EL to AlmaLinux migration tool.

 

[torefloo]

well, centos can't be used in plesk panels anymore, do we need to use almalinux, definitely?

 

[Bitpalast]

CentOS 7.9 can still be used. Plesk does not support products that are "end of life", and eventually support for CentOS 7.9 will also cease when it becomes end of life.

You can use AlmaLinux or RockyLinux instead. Most prefer AlmaLinux.

 

[torefloo]

Also, with this transition, can't I use it without losing the data on my existing plesk server?

 

[torefloo]

The most important question is will I lose data after this transition?

 

[Bitpalast]

An in-place update should not touch your content. However, there is always a risk involved, e.g. that with an update of the kernel the system won't boot or that some services might not be operable after a reboot. In such cases you need to investigate the cause, fix the problem, restart the services. But that is just standard administrator work. If you are not using any awkward super-special-extra configurations on your system, a migration to AlmaLinux should be easy as described in their instructions. It is always recommended to have a full backup before doing a migration.

If you feel uncomfortable, another way to migrate is to setup a new server from scratch with AlmaLinx, then install a fresh Plesk on it, then restore a Plesk full backup to that new server.

 

[torefloo]

hello, I switched to almalinux yesterday, but I am still getting update errors, my screenshot is as follows;

 

[Bitpalast]

This could be a file permission issue with the target file. Is the target writeable?

 

[torefloo]

what do you mean by target result I run yum update -y command it just can't install these packages to get the latest updates but

 

[Bitpalast]

The error in your screenshot is:
"unpacking of archive failed on file /usr/bin/perl: cpio: rename failed - Operation not permitted"
This means that yum tries to unpack the archive, but the file where it should be unpacked to is already present and read-only or the directory is read-only.

 

[torefloo]

So how can I detect this writing problem and find a solution?

 

[Bitpalast]

Just a few suggestions: Have you checked the file permissions of the target? Have you checked the directory permissions of the target directory? Have you compared the results to a standard installation of your operating system how it should normally look, e.g. on a small test server? Have you tried to search on Google or Linux forums for the error that you are getting? Is the repository from where the installations are done the right repository that is normally used for your operating system? Do you have selinux enabled and might it be blocking access to some files?