Forwarded to devs MySQL Governer with Plesk

[Hex]

TITLE:

Mysql Governer with Plesk​

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:

Product version: Plesk Obsidian 18.0.15
Build date: 2019/06/19 17:00
OS version: CloudLinux 7.6
Revision: 14308f04385f62a24c8b44566486625d16ad9738
Architecture: 64-bit
Wrapper version: 1.2

Tested on MariaDB Version: 5.5.6 & 10.2.25

Product version: Plesk Onyx 17.8.11 Update #56
Update date: 2019/06/23 08:42
Build date: 2019/06/05 06:43
OS version: CloudLinux 7.6
Revision: 388af031cc753ceca2cd81d6db5847338429dd4b
Architecture: 64-bit
Wrapper version: 1.2

Tested on MariaDB Version: 5.5.6 (Default)​

PROBLEM DESCRIPTION:

Mariadb service stopped after installing Mysql Governer
I'm unable to start the service

[root@vultr ~]# service mariadb status
Redirecting to /bin/systemctl status mariadb.service
● mariadb.service - MariaDB database server
   Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/mariadb.service.d
           └─migrated-from-my.cnf-settings.conf
        /usr/lib/systemd/system/mariadb.service.d
           └─respawn.conf
   Active: activating (auto-restart) (Result: exit-code) since Sun 2019-06-23 07:57:19 UTC; 1s ago
  Process: 6043 ExecStartPost=/usr/sbin/mariadb-wait-ready $MAINPID (code=exited, status=1/FAILURE)
  Process: 6042 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0/SUCCESS)
  Process: 6012 ExecStartPre=/usr/sbin/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS)
 Main PID: 6042 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/mariadb.service

Jun 23 07:57:19 vultr.guest systemd[1]: mariadb.service: control process exited, code=exited status=1
Jun 23 07:57:19 vultr.guest systemd[1]: Failed to start MariaDB database server.
Jun 23 07:57:19 vultr.guest systemd[1]: Unit mariadb.service entered failed state.
Jun 23 07:57:19 vultr.guest systemd[1]: mariadb.service failed.
[root@vultr ~]# service mariadb start
Redirecting to /bin/systemctl start mariadb.service
Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.

Plesk Onyx 17.8

[root@vultr ~]# service mariadb start
Redirecting to /bin/systemctl start mariadb.service
Job for mariadb.service failed because the control process exited with error code. See "systemctl status mariadb.service" and "journalctl -xe" for details.
[root@vultr ~]# service mariadb status
Redirecting to /bin/systemctl status mariadb.service
● mariadb.service - MariaDB database server
   Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/mariadb.service.d
           └─migrated-from-my.cnf-settings.conf
   Active: failed (Result: exit-code) since Sun 2019-06-23 09:25:33 UTC; 11s ago
  Process: 3126 ExecStartPost=/usr/sbin/mariadb-wait-ready $MAINPID (code=exited, status=1/FAILURE)
  Process: 3125 ExecStart=/usr/bin/mysqld_safe --basedir=/usr (code=exited, status=0/SUCCESS)
  Process: 3095 ExecStartPre=/usr/sbin/mariadb-prepare-db-dir %n (code=exited, status=0/SUCCESS)
 Main PID: 3125 (code=exited, status=0/SUCCESS)

Jun 23 09:25:31 vultr.guest systemd[1]: Starting MariaDB database server...
Jun 23 09:25:31 vultr.guest mariadb-prepare-db-dir[3095]: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
Jun 23 09:25:32 vultr.guest mysqld_safe[3125]: 190623 09:25:32 mysqld_safe Logging to '/var/log/mariadb/mariadb.log'.
Jun 23 09:25:32 vultr.guest mysqld_safe[3125]: 190623 09:25:32 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
Jun 23 09:25:33 vultr.guest systemd[1]: mariadb.service: control process exited, code=exited status=1
Jun 23 09:25:33 vultr.guest systemd[1]: Failed to start MariaDB database server.
Jun 23 09:25:33 vultr.guest systemd[1]: Unit mariadb.service entered failed state.
Jun 23 09:25:33 vultr.guest systemd[1]: mariadb.service failed.

STEPS TO REPRODUCE:

1- Install Cloudlinux 7.6
2- Reboot
3- Install CageFS
4- Reboot
5- Install MySQL Governer
6- Reboot​

ACTUAL RESULT:

Plesk Obsidian

Server Error
500
Plesk\Exception\Database
DB query failed: SQLSTATE[HY000] [2002] Connection refused

Type Plesk\Exception\Database
Message DB query failed: SQLSTATE[HY000] [2002] Connection refused
File Mysql.php
Line 60

Plesk Onyx

Server Error
500
Zend_Db_Adapter_Exception
SQLSTATE[HY000] [2002] Connection refused

Type Zend_Db_Adapter_Exception
Message SQLSTATE[HY000] [2002] Connection refused
File Abstract.php
Line 144

EXPECTED RESULT:

Working Setup even after uninstalling mysql-governer.​

ANY ADDITIONAL INFORMATION:

* This is a new server
* The same error appears even after Uninstalling Mysql Governer
MySQL Governor | Documentation

* service mariadb/mysql start result in the same error.
* Plesk repair cannot start without mariadb service.
* The same results happened with mariadb 10.2.24 (Cloudlinux through Warining during mysql-governer installation for inconsistency with 10.2.24 due to their repository only supports 10.2.25)
* Somehow on another server I've managed to test mysql-governer without issues but the same error results happen when I tried to uninstall the governor.

* Finally : the same result occur even after uninstalling the entire Cloudlinux system​

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:

Confirm bug​

 

[IgorG]

I see no relation with Plesk - you just installed some MySQL addon and MySQL server doesn't start anymore.
The questions should be addressed to CloudLinux support.

 

[Hex]

IgorG I'll not argue about this but this is Plesk rule to communicate with Cloudlinux team about the possible issues.

 

[IgorG]

@Hextrator why do you think so? What exact rule do you mean?
I suppose that you have to contact CloudLinux with regarding this issue.

 

[Hex]

@IgorG

Either way is possible ,What I mean here, B2B communication is more efficient than C2B (3rd party Business)
And we're talking about Cloudlinux here, not some extension.

They will get more information's from Plesk about the product and the new updates they will take it more seriously than me (1 customer).

Besides my report here is not on my own servers, these are three clean installation with different versions of database engines.

You know what... I'll do it your way.

Regards,