Resolved Error updating Plesk 17.0.17 from update 3 running on CentOS 7.3

[Vincent Bourgonje]

When auto updating the following error appeared in the log file:

Running Transaction Check
Error unpacking rpm package plesk-service-node-utilities-17.0.17-cos7.build1700161028.14.x86_64
plesk-service-node-utilities-17.0.17-cos7.build1700161005.19.x86_64 was supposed to be removed but is not!
Exception: Scriptlet or other non-fatal errors occurred during transaction.
Updating: plesk-service-node-utilities-17.0.17-cos7.build1700161028.14.x86_64 [1/4]
error: unpacking of archive failed on file /usr/local/psa/admin/sbin/deployer: cpio: rename failed - Permission denied
error: plesk-service-node-utilities-17.0.17-cos7.build1700161028.14.x86_64: install failed
chsh: Shell not changed.
Changing shell for popuser.
chsh: Shell not changed.
Changing shell for mhandlers-user.
Updating: psa-mail-driver-common-17.0.17-cos7.build1700170131.16.x86_64 [2/4]
Cleanup: psa-mail-driver-common [3/4]

I wasn't able to fix this error. Not with Plesk repair installation or with other recommendations found in this forum and the Plesk knowledge base.

I have the same problem on 2 VPS servers both on CentOS 7.3 - another one running on CentOS 7.2 did upgrade without any problems.

I tried to remove "plesk-service-node-utilities-17.0.17-cos7.build1700161005.19.x86_64 was supposed to be removed but is not!" but was not successful. Any help would be appreciated.

CentOS Linux 7.3.1611 (Core)‬
Product Plesk Onyx
Version 17.0.17 Update #3, last updated on Oct 21, 2016 01:34 PM

 

[mizar]

It seems the selinux forbid rpm to unpack the packages. Please either disable it (at least for upgrade time) by executing setenforce 0 or make sure that Plesk policy is loaded - semodule -l | grep plesk

 

[Vincent Bourgonje]

Great both servers have been updated succesfully now! Thanks for your help.

I used the following steps to solve the problem:

- logged in at the cli as root user
- deleted /var/lock/parallels-panel-upgrade-failure.flag
- setenforce 0
- run the update through the admin GUI (Tools & Settings > Plesk > Updates & Upgrades)
- setenforce 1
- exit!

 

[DaVince]

Hi,

I was wondering if this is just a stopgap fix and SELinux needs to be disabled and re-enabled every time I wish to update the server, or that the server update process is pretty much 'fixed' after doing it once. I ask because in my case, plesk did seem to be in the policies but it failed anyway, and I had to do what other Vincent posted.

 

[Vincent Bourgonje]

Since I have updated with disabling SELinux (setenforce 0) and reenabling it after the update I never had any problems anymore with updating. So you can switch it on after fixing the failing update and leave it on.