• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Update psa-selinux ... TypeError: an integer is required

Bitpalast

Plesk addicted!
Plesk Guru
Upgrade of Plesk 12.5.30 to 17.5.3 on a clean/default install CentOS 7.3 with latest OS patches from base, updates, epel repositories:

Code:
...
Updating: psa-selinux-17.5.3-cos7.build1705170314.17.noarch [83/168]

TypeError: an integer is required

FATAL ERROR: python callback <bound method RPMTransaction.callback of <yum.rpmtrans.RPMTransaction instance at 0x14827e8>> failed, aborting!

System is up and running. Several other issues occured (for example fail2ban must be excluded from epel, else it won't work after the upgrade; several issues with additional updates/upgrades after upgrade) but could all be solved.

But what's this thing with the psa-selinux issue? No more details given in logs. Does this need fixing? Consequences of the error?
 
Last edited:
Back
Top