Resolved SELinux is preventing /opt/plesk/php/8.3/sbin/php-fpm from connectto access on the unix_stream_socket /var/lib/mysql/mysql.sock

[pleskuser67553]

Username:

TITLE

SELinux is preventing /opt/plesk/php/8.3/sbin/php-fpm from connectto access on the unix_stream_socket /var/lib/mysql/mysql.sock

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

CPU: AMD EPYC-Milan Processor (4 core(s))
Version: Plesk Obsidian v18.0.73_build1800251009.17 os_RedHat el9
Operating System: AlmaLinux 9.6 (Sage Margay)
Database: MariaDB 10.11.15
PHP 8.3.27 and 8.4.14

PROBLEM DESCRIPTION

After system auto-update of MariaDB packages, websites cannot connect to database.

STEPS TO REPRODUCE

Do nothing, wait for server to auto-update.

Apply workaround in Issue - Latest 'beta' feature to Plesk to upgrade Mariadb is giving problems

ACTUAL RESULT

Websites cannot connect to database because of SELinux

EXPECTED RESULT

Websites should be able to connect to database

ANY ADDITIONAL INFORMATION

I will include screenshots by reply since this form does not enable uploading of images.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[pleskuser67553]

Email notification output circa 03:30 UTC



System logs when attempting to access a website:

 

[pleskuser67553]

Before applying the workaround I tried MySQL repair in the Diagnose & Repair UI. No issues detected.

 

[Sebahat.hadzhi]

Thank you for the provided details. Our team recently published an article about this issue and the same is caused by a bug in MariaDB as their packages are not fully compatible with the system SELinux policy.. Please find the details and the workaround here:

• https://support.plesk.com/hc/en-us/...ELinux-is-enabled-on-a-Plesk-for-Linux-server

 

[pleskuser67553]

Thank you @Sebahat.hadzhi. Given that [MDEV-24941] SElinux incorrect label for server socket - Jira says that the bug is fixed and closed, and that one of the fix versions is 10.11.15 (my version since Plesk's auto-update), can I therefore expect the resolution in Plesk's support article to be a one-time thing? Are you able to explain please how could this error have occured when the update to MariaDB' 10.11.15 supposedly contained the fix?

 

[Sebahat.hadzhi]

From what I understand, the MySQL SELinux package version 1.0.13-1 did not set a policy for /usr/sbin/mariadbd. Thus, in scope of PPPM-14846 what our team did was to set SElinux context for /usr/sbin/mariadbd on AlmaLinux 9. They also ensured that the SELinux policies provided by Plesk do not conflict with those from older versions of the package.

As for the workaround from the article, the restoration should be permanent.