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

Selinux + RHEL5 problem during installation...

F

fgilain

Guest
Hi all,

I'm just installing a new plesk 8.20 server on a RHEL5 platform.
i did sentenfoce=0 as asked in installation guide before running the autoinstaller script, but i get message concerning SElinux very often, here is an extract of the installation log :

Creating initial database
Initial database created

Creating SSL certificate
Generating a 1024 bit RSA private key
.++++++
....................................................................++++++
writing new private key to '/etc/sso/sso.pem'
-----
problems making Certificate Request
32359:error:0D07A098:asn1 encoding routines:ASN1_mbstring_ncopy:string too short:a_mbstr.c:147:minsize=1
1024 semi-random bytes loaded
Generating DH parameters, 512 bit long safe prime, generator 2
This is going to take a long time
.......................+..............................+...............................+........................................................+............................+.......................+.......+......+.......................................................+.+..........................................+.+...........................+.........+............++*++*++*++*++*++*

SSL certificate created

Creating SSL CA certificate
Generating a 1024 bit RSA private key
............................................................++++++
..................++++++
writing new private key to '/etc/sso/sso-ca.pem'
-----
1024 semi-random bytes loaded
Generating DH parameters, 512 bit long safe prime, generator 2
This is going to take a long time
......................+.........................+.....+......+........................................................................................................+..........+............+.......++*++*++*++*++*++*

SSL CA certificate created

Create SSO config

SSO config created

Installation du package psa-sso-configurator-1.0.0-rhel5.build82070706.15.noarch
/etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /var/qmail/bin(/.*)? (system_u:eek:bject_r:sendmail_exec_t:s0 and system_u:eek:bject_r:bin_t:s0).
/etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /var/qmail/bin(/.*)? (system_u:eek:bject_r:sendmail_exec_t:s0 and system_u:eek:bject_r:bin_t:s0).
Installation du package psa-locale-fr-FR-8.2-build82070706.13.noarch
/etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /var/qmail/bin(/.*)? (system_u:eek:bject_r:sendmail_exec_t:s0 and system_u:eek:bject_r:bin_t:s0).
/etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /var/qmail/bin(/.*)? (system_u:eek:bject_r:sendmail_exec_t:s0 and system_u:eek:bject_r:bin_t:s0).
Trying to establish test connection... connected
done


Any idea of what happens and how to correct this ?
Will this make my server not working in the futur or something like that ?

thanks

Florent
 
I'm getting this notice as well, but SELinux is disabled:

From /etc/selinux/config

# 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 - SELinux is fully disabled.
SELINUX=disabled
# SELINUXTYPE= type of policy in use. Possible values are:
# targeted - Only targeted network daemons are protected.
# strict - Full SELinux protection.
SELINUXTYPE=targeted

~Matt
 
You can check your SELinux status by running 'sestatus'. If it is set to DISABLED in the config file, that doesn't necessarily mean it is disabled. If you reboot the machine, then it will read the config and not use SELinux. Running 'sestatus' gives you the definitive answer.
 
I have this same issue on CentOS 5. It started while installing Plesk. And now when I use yum to update something I get these warnings too. SELinux is disabled.
SELinux status: disabled
 
Yeah, I had that problem too on RHEL5.

What I did was open up :
/etc/selinux/targeted/contexts/files/file_contexts

and removed the line:
/var/qmail/bin(/.*)? system_ubject_r:sendmail_exec_t:s0

Good to go after that.

~Matt
 
Seeing this too

With CentOS 5, I see this:

/etc/selinux/targeted/contexts/files/file_contexts: Multiple different specifications for /var/qmail/bin(/.*)? (system_u:eek:bject_r:sendmail_exec_t:s0 and system_u:eek:bject_r:bin_t:s0).
/etc/selinux/targeted/contexts/files/file_contexts: Multiple same specifications for /usr/local/sitebuilder/tmp(/.*)?.


every time I do something with RPM. Selinux is disabled:

SELinux status: disabled

I think there is a problem with RHEL 5 / CentOS 5
 
Back
Top