problem with mariadb103 to 105 and mysqlgovernor

[dzamanakos]

Hi, i'm using cloudlinux with mysqlgovernor and tried to upgrade mariadb from 103 to 105.
As always i used the instructions from CloudLinux OS Shared components

When i entered the
/usr/share/lve/dbgovernor/mysqlgovernor.py --mysql-version=mariadb104
i got the message that cpanel does not support 104 and run the
/usr/share/lve/dbgovernor/mysqlgovernor.py --mysql-version=mariadb105

After a while the new packages were installed but in the last steps that the script upgrades dbs etc, i got an error :

sys.x$schema_tables_with_full_table_scans OK
sys.x$session OK
sys.x$statement_analysis OK
sys.x$statements_with_errors_or_warnings OK
sys.x$statements_with_full_table_scans OK
sys.x$statements_with_runtimes_in_95th_percentile OK
sys.x$statements_with_sorting OK
sys.x$statements_with_temp_tables OK
sys.x$user_summary OK
sys.x$user_summary_by_file_io OK
sys.x$user_summary_by_file_io_type OK
sys.x$user_summary_by_stages OK
sys.x$user_summary_by_statement_latency OK
sys.x$user_summary_by_statement_type OK
sys.x$wait_classes_global_by_avg_latency OK
sys.x$wait_classes_global_by_latency OK
sys.x$waits_by_host_by_latency OK
sys.x$waits_by_user_by_latency OK
sys.x$waits_global_by_latency OK
Phase 4/7: Running 'mysql_fix_privilege_tables'
ERROR 2013 (HY000) at line 448: Lost connection to MySQL server during query
ERROR 2006 (HY000) at line 458: MySQL server has gone away
FATAL ERROR: Upgrade failed
The installation of MySQL for db_governor completed
---
metadata:
command: configureservice
reason: Enabled monitoring for mysql.
result: 1
version: 1
Give mysql service time to start before service checking(15 sec)
Installation of mysql for db_governor completed

The mariadb105 (and the websites that use databases) is working for some days now but it seems that it didnt complete all the steps.

One thing i noticed is that no mariadb105 repo is in /etc/yum.repos.d
One other that after mariadb upgrade, cpanel is installing a new my.cnf, that didnt happened after my upgrade.
I'm worrying that the mariadb105 is running, but some stuff may be unfinished.

I opened a ticket to cloudlinux and the reply was :

-------------------------------------------------------------------------------------------
I've checked your server and can't find any DB Governor-related issues. Please note, that we can provide support to DB Governor-related issues only, and we aren't MySQL experts.
I've run the following command on the server:
mysql_upgrade

And no issues reported:
Phase 7/7: Running 'FLUSH PRIVILEGES'
OK

I would recommend you contact the MySQL database experts in order to update your databases correctly.
---------------------------------------------------------------------------------------------

and

---------------------------------------------------------------------------------------------
In this situation, I can only recommend remove DB Governor, open the ticket with cPanel in order to upgrade MariaDB from 10.3 to 10.5 safely, and then install DB Governor back.
---------------------------------------------------------------------------------------------

If i uninstall at that time (after the upgrade) mysqlgovernor, the version will be on 105. Is there a way to reinstall cpanel's mariadb105 with all the meta-installation scripts running to be sure that the upgrade will be completed and then reinstall mysqlgovernor?


best,

 

[cPRex]

Hey there! I checked a test server using MySQL Governor and found that it does not add an entry to /etc/yum.repos.d, so that in itself is not an issue as it is expected behavior. Here's my test machine showing this:

[[email protected] yum.repos.d]# ll
total 88
-rw-r--r--  1 root root   329 Aug 23 08:01 centos-extras.repo
-rw-r--r--. 1 root root   406 Jul 21 04:51 clmirror.repo
-rw-r--r--  1 root root   391 Sep 16 13:32 cl-mysql.repo
-rw-r--r--. 1 root root   755 Feb 16  2021 cloudlinux-ea4-experimental.repo
-rw-r--r--. 1 root root   660 Feb 16  2021 cloudlinux-ea4.repo
-rw-r--r--. 1 root root 12737 Feb 16  2021 cloudlinux-ea4-rollout.repo
-rw-r--r--. 1 root root   734 Feb 16  2021 cloudlinux-ea4-testing.repo
-rw-r--r--  1 root root   232 Aug 23 08:01 cloudlinux-imunify360.repo
-rw-r--r--  1 root root  2895 Aug 23 08:01 cloudlinux.repo
-rw-r--r--  1 root root 12467 Aug 23 08:01 cloudlinux-rollout.repo
-rw-r--r--  1 root root   257 Sep  8 22:50 cPAddons.repo
-rw-------  1 root root   241 Sep 20 03:28 cpanel-plugins.repo
-rw-r--r--  1 root root   204 Jun 22 17:25 EA4.repo
-rw-r--r--  1 root root  1050 Oct 31  2020 epel.repo
-rw-r--r--  1 root root  1149 Oct 31  2020 epel-testing.repo
-rw-r--r--  1 root root   771 Sep  8 22:38 Mysql57.repo
[[email protected] yum.repos.d]# mysql --version
mysql  Ver 15.1 Distrib 10.3.31-MariaDB, for Linux (x86_64) using readline 5.1

If everything is currently working well it's hard for me to recommend changing anything. If you'd like to submit a ticket to our team we could at least check the system and make sure everything is in place that we expect to be there.

 

[dzamanakos]

Thank you, for now no users reported any problems so i'll not do any changes.

Just in case, if anyone wants to upgrade from 103 to 105 and is using mysqlgovernor, the only way, at that time, to do that (final ticket reply from cloudlinux) is to :

- uninstall mysqlgovernor
- update mariadb through WHM menu
- install mysqlgovernor

best,

 

[cPRex]

That's very interesting as they don't mention that in their documentation, and I've been able to switch back and forth without issues. I'm wondering if that is for your specific situation, or if they really mean that to be in general.

CloudLinux OS components

Reseller limits LVE-Stats 2 CageFS MySQL Governor PHP Selector Python Selector Ruby Selector Node.js Selector Apache mod_lsapi PRO Additional integration components Apache suexec module

docs.cloudlinux.com

 

[HostXNow_Chris]

That's very interesting as they don't mention that in their documentation, and I've been able to switch back and forth without issues. I'm wondering if that is for your specific situation, or if they really mean that to be in general.

CloudLinux OS components

Reseller limits LVE-Stats 2 CageFS MySQL Governor PHP Selector Python Selector Ruby Selector Node.js Selector Apache mod_lsapi PRO Additional integration components Apache suexec module

docs.cloudlinux.com

Is this still the same issue i.e have to

- uninstall mysqlgovernor
- update mariadb through WHM menu
- install mysqlgovernor

Or does it upgrade properly now without having to uninstall mysqlgovernor first? I think cPanel created a password updater-script in the end?

 

[cPanelAnthony]

Hello! I have reached out to CloudLinux for confirmation. As long as you are on cPanel version 98 or higher, and have the latest MySQLgovernor packages, you shouldn't need to perform these steps. Please let me know if you run into any issues.

 

[HostXNow_Chris]

Hello! I have reached out to CloudLinux for confirmation. As long as you are on cPanel version 98 or higher, and have the latest MySQLgovernor packages, you shouldn't need to perform these steps. Please let me know if you run into any issues.

Which are those? How to check?

 

[mtindor]

End Goal: CloudLinux 6 ELS + WHM + MySQL Governor + MariaDB 10.5 (since MariaDB 10.3 will be EOL shortly)
Current: CloudLinux 6 ELS + WHM + MySQL Governor + MariaDB 10.3

I had been running this box without MySQL Governor for all of its years. I recently installed MySQL Governor and re-installed MariaDB 10.3 using MySQL Governor so that the MariaDB packages being used are now from CL. WHM doesn't support upgrading MariaDB on servers not running MySQL Governor. And MySQL Governor must be installed on CL 6 ELS servers in order to do any MariaDB upgrades at all.

So I'm concerned about upgrading from MariaDB 10.3 to MariaDB 10.5 (using latest MySQL Governor 1.88 on WHM 108) based upon information I've read where critical changes were made to MySQL tables and/or schema starting with 10.4.

I have a ticket open with Cloudlinux looking for some assurance that upgrading from MariadB 10.3 to MariaDB 10.5 on a CL6 ELS box running MySQL Governor 1.88 and WHM 108 will not be an issue. But I'm wondering if cPanel can provide any assurances from their end that this process should go smoothly without any steps being missed (by upgrading from 10.3 to 10.5 using MySQL Governor).

Anyone at cPanel want to bite on this?

Mike

 

[cPRex]

I would expect the upgrade to go just fine. The issue more about if your databases/tables/queries will support the newer version, which is more difficult to determine.

 

[mtindor]

I would expect the upgrade to go just fine. The issue more about if your databases/tables/queries will support the newer version, which is more difficult to determine.

Fortunately 99% of our PHP sites are Wordpress. Unfortunately, that doesn't necessarily mean they are all running the latest 6.2.x version of Wordpress. But we're probably safe. The mere fact that MariaDB 10.3 is going to be EOL'd suggests to me that if there were any issues with (in my case, Wordpress) and MariaDB 10.5, Wordpress sure as hell should have / would have addressed those (even on older versions) by now. Fingers crossed of course.

But I understand what you are saying and appreciate that you have some confidence that the upgrade process itself should occur without much fanfare from the standpoint of the upgrade scripts properly doing what they need to do.

Thanks

Mike