• 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.

Issue psa-selinux-policy-trigger fails in Enforcing mode during a dnf update of selinux-policy on AlmaLinux 10.3

GoranN

New Pleskian
Server operating system version
AlmaLinux 10.3
Plesk version and microupdate number
18.0.82 Update #3
Hi all,

After a regular dnf update on AlmaLinux (10.2 to 10.3) with SELinux in Enforcing mode, the Plesk SELinux trigger reported a problem. I would like to know whether this is a known issue or expected behavior, and whether any action is needed on my side.

Environment:
- Plesk Obsidian 18.0.82 (psa-18.0.82-2.redhat.10+p18.0.82.x+t261110.0851)
- psa-selinux-18.0.53-2.redhat.10+p18.0.82.x+t261110.0851
- AlmaLinux 10.3, selinux-policy 42.1.18-4.el10_2.4 upgraded to 42.1.27-2.el10_3.2
- SELinux: Enforcing, targeted policy

The update was started manually with dnf, not through the Plesk installer. From /var/log/dnf.rpm.log:

Code:
03:29:11 Upgrade: selinux-policy-targeted-extra-42.1.27-2.el10_3.2.noarch
03:29:12 Upgrade: selinux-policy-42.1.27-2.el10_3.2.noarch
03:29:44 Failed to resolve typeattributeset statement at /var/lib/selinux/targeted/tmp/modules/100/antivirus/cil:134
         Failed to resolve AST
         semodule:  Failed!
         (these three lines appear 3 times)
          Trying to install Plesk SELinux policy module ... restorecon: Could not set context for /usr/local/psa/admin/sbin/deployer:  Permission denied
         Warning: Error while setting SELinux types. Command was: restorecon -i -R /usr/local/psa
         ***** installation problem report *****
03:29:48 Upgrade: selinux-policy-targeted-42.1.27-2.el10_3.2.noarch

Plesk logs:
Code:
plesk_18.0.82_installation_problems.log:
START psa-selinux-policy-trigger-18.0.53 installing AT Tue Nov 17 03:29:12 CET 2026
STOP psa-selinux-policy-trigger-18.0.53 installing AT Tue Nov 17 03:29:44 CET 2026: PROBLEMS FOUND

plesk_18.0.82_installation.log:
**** Package psa-selinux-policy-trigger scriptlet failed.

audit.log has two denials like this one:
Code:
avc:  denied  { getattr } for  comm=restorecon name=deployer dev="sda4" scontext=unconfined_u:unconfined_r:setfiles_t:s0-s0:c0.c1023 tcontext=system_u:object_r:plesk_deployer_t:s0 tclass=file permissive=0

What I noticed:
- rpm -q --triggers psa-selinux shows a triggerin on selinux-policy. In this transaction the trigger started right after selinux-policy and selinux-policy-targeted-extra were upgraded, and before selinux-policy-targeted was upgraded. The antivirus module is shipped in selinux-policy-targeted-extra.
- Earlier runs of the same trigger (Nov 1 and Nov 13, during Plesk updates) completed successfully. In those runs the Plesk installer had switched SELinux to Permissive ("Set selinux into the Permissive mode" and later "Set selinux into the Enforcing mode" in the installation log).
- After the transaction, the final policy build succeeded, the deployer file has the label plesk_deployer_t (same as matchpathcon), and restorecon -n reports no change for it.

Questions:
1. Is this a known issue with psa-selinux on EL10 when selinux-policy is updated with dnf while SELinux is Enforcing?
2. Is any manual action recommended after such an update, for example re-running the trigger, or is it safe to leave it since the final state looks correct?

Thanks!
 
Thanks, Martin,
that's a very useful pointer. In my case the label on /usr/local/psa/admin/sbin/deployer was already correct after the update (ls -Z shows plesk_deployer_t and matchpathcon agrees), and restorecon -n on that file now runs without any denial. The denial only happened while the dnf transaction was running, before selinux-policy-targeted was upgraded, so we did not need restorecon -F or a Plesk installer rerun.

I will check again on the next selinux-policy update.

Thank you, Goran.
 
Back
Top