• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question error during update plesk to 18.0.44

MicheleP

Basic Pleskian
Server operating system version
Centos
Plesk version and microupdate number
18.0.44
Hi
I've update a server from 18.0.43 to 18.0.44
during the installation I see an error with selinux and a jump from the update of package [60/116] to the cleanup process

......
Updating: plesk-resctrl-18.0-2.centos.7+p18.0.44.0+t220422.0554.x86_64 [55/116]
Installing: plesk-phpenv-0.9.0-2.centos.7+p18.0.44.0+t220513.0042.noarch [56/116]
Updating: plesk-dns-bind-driver-18.0-2.centos.7+p18.0.44.0+t220520.1914.x86_64 [57/116]
Updating: psa-selinux-18.0.20-2.centos.7+p18.0.44.0+t220422.0554.noarch [58/116]
Failed to resolve roletype statement at /etc/selinux/final/tmp/modules/400/plesk/cil:2
semodule: Failed!
Failed to resolve roletype statement at /etc/selinux/tmp/tmp/modules/400/plesk/cil:2
semodule: Failed!
Updating: 1:plesk-modsecurity-crs-3.3.2-2.centos.7+p18.0.44.0+t220422.0554.x86_64 [59/116]
Cleanup: psa-spamassassin [60/116]
Cleanup: plesk-dovecot-imap-driver [61/116]
Cleanup: plesk-dovecot-pigeonhole [62/116]
Cleanup: plesk-roundcube [63/116]
.....

But the list of the verify packages from 1 to 116 is ok

....
Verify: 55/116: plesk-dovecot-pigeonhole.x86_64 0:0.5.18-2.centos.7+p18.0.44.0+t220520.1914 - u
Verify: 56/116: plesk-service-node-utilities.x86_64 0:18.0-2.centos.7+p18.0.44.0+t220520.1914 - u
Verify: 57/116: plesk-dovecot-core.x86_64 0:2.3.18-2.centos.7+p18.0.44.0+t220520.1914 - u
Verify: 58/116: postfix.x86_64 2:3.5.14-2.centos.7+p18.0.44.0+t220518.2121 - u
Verify: 59/116: plesk-fail2ban-configurator.noarch 0:18.0-2.centos.7+p18.0.44.0+t220422.0554 - u
Verify: 60/116: psa-mod_proxy.x86_64 0:2.4.6-2.centos.7+p18.0.42.0+t220117.1118 - ud
Verify: 61/116: psa-selinux.noarch 0:18.0.20-2.centos.7+p18.0.43.0+t220406.1450 - ud
Verify: 62/116: psa-proftpd.x86_64 0:1.3.7c-2.centos.7+p18.0.43.0+t220406.1450 - ud
Verify: 63/116: psa-locale-base-en-US.noarch 0:18.0-2.centos.7+p18.0.43.1+t220414.1850 - ud
Verify: 64/116: psa.x86_64 0:18.0.43-2.centos.7+p18.0.43.1+t220414.1850 - ud
Verify: 65/116: psa-mod_aclr2.x86_64 0:14081815-2.centos.7+p18.0.43.0+t220406.1450 - ud
Verify: 66/116: sw-collectd.x86_64 0:5.11.0-2.centos.7+p18.0.43.0+t220406.1450 - ud
Verify: 67/116: plesk-repair-kit.x86_64 0:18.0-2.centos.7+p18.0.43.1+t220414.1850 - ud
.....

And at the end the update says

Congratulations!
The upgrade has been finished. Plesk is now running on your server.

Is this regular or there is someting wrong?
 
The warnings that you've reported are false-positive. They appear when installing psa-selinux on CentOS 7 while SELinux is in the Enforcing mode. The warnings can be safely ignored since they do not impact any functionality.
This behaviour was confirmed as a Plesk bug PPP-35269 and it is planned to be fixed in the future Plesk updates.
 
Thanks
but what is the difference between the final -u for the files verified before the "jump" and the -ud for those after the "jump"?
 
Back
Top