• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Selinux shows warnings in centOS

Azurel

Silver Pleskian
System: CentOS Linux 7.6.1810 (Core)‬ with Plesk Onyx Version 17.8.11

with yum update I get this warnings
ValueError: SELinux policy is not managed or store cannot be accessed.
warning: %postun(bind-32:9.9.4-72.el7.x86_64) scriptlet failed, exit status 1
Non-fatal POSTUN scriptlet failure in rpm package 32:bind-9.9.4-72.el7.x86_64

OSError: No such file or directory
ValueError: SELinux policy is not managed or store cannot be accessed.
warning: %posttrans(bind-32:9.9.4-73.el7_6.x86_64) scriptlet failed, exit status 1
Non-fatal POSTTRANS scriptlet failure in rpm package 32:bind-9.9.4-73.el7_6.x86_64

So I take a look in selinux config "/etc/selinux/config" its disabled by default
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of these two values:
# targeted - Targeted processes are protected,
# minimum - Modification of targeted policy. Only selected processes are protected.
# mls - Multi Level Security protection.
SELINUXTYPE=targeted

# rpm -qa | grep selinux
selinux-policy-devel-3.13.1-229.el7_6.9.noarch
selinux-policy-targeted-3.13.1-229.el7_6.9.noarch
libselinux-python-2.5-14.1.el7.x86_64
selinux-policy-3.13.1-229.el7_6.9.noarch
libselinux-2.5-14.1.el7.x86_64
libselinux-utils-2.5-14.1.el7.x86_64
psa-selinux-17.8.11-cos7.build1708181031.14.noarch

What can I do to fix the yum warnings?
 
Just for reference in case anyone else comes across this post looking for an answer...

I also got this error running a YUM update:

"
OSError: No such file or directory
ValueError: SELinux policy is not managed or store cannot be accessed.
warning: %posttrans(bind-32:9.9.4-73.el7_6.x86_64) scriptlet failed, exit status 1
Non-fatal POSTTRANS scriptlet failure in rpm package 32:bind-9.9.4-73.el7_6.x86_64
"

Bind did work without issue after the update.

Googling suggests this is a bug with SELinux and occurs if SELinux is installed but not enabled - related links:

Oracle Linux 7.6 - bind package update error | Oracle Community
1633108 – yum --installroot=/tmp/XXXXXX , ValueError: SELinux policy is not managed, rpmbooleans.custom: No such file or directory
Warnings after CentOS upgrade

General advice seems to be the error can be safely ignored if your not using SELinux, 48 hours on from the update - I have not seen any issues on a busy server with 300+ web hosting / email accounts.

Thanks
Rob
 
Back
Top