In Progress CPANEL-43328 - Elevate Issue : MySQL

[Michael Legg]

When I run the /scripts/elevate-cpanel --check --upgrade-to=almalinux script, it identifies MySQL 5.6 as a blocker ...

You are using MySQL 5.6 server. This version is not available for AlmaLinux 8. You first need to update your MySQL server to 8.0 or later. You can update to version 8.0 using the following command: /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0

I actually have a remote MySQL server, and don't run MySQL on the cPanel server. Just for fun I ran the suggested command "/usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=8.0" and the response was "API failure: (XID 8uxxzx) “selected_version” must be one of the following values: “10.6”"

10.6 is the version of MaraiDB that I run on the database server, AFAIK it has nothing to do with the MySQL version on the webserver.

Anyway, I tried /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 and got ...

[2023-09-11 14:31:16 +1000] warn [Internal Warning while parsing [stdin] 35950] Use of uninitialized value $mysqldatadir in quotemeta at /usr/local/cpanel/Whostmgr/Mysql/Upgrade/Warnings.pm line 108.
at /usr/local/cpanel/Whostmgr/Mysql/Upgrade/Warnings.pm line 108.
Whostmgr::Mysql::Upgrade::Warnings::get_upgrade_warnings(10.6, 10.6) called at /usr/local/cpanel/Whostmgr/Mysql/Upgrade.pm line 1030
Whostmgr::Mysql::Upgrade::_update_conf_with_current_version_and_check_for_blockers(HASH(0x32ea910)) called at /usr/local/cpanel/Whostmgr/Mysql/Upgrade.pm line 528
Whostmgr::Mysql::Upgrade::_validate_conf(HASH(0x32ea910)) called at /usr/local/cpanel/Whostmgr/Mysql/Upgrade.pm line 394
Whostmgr::Mysql::Upgrade::unattended_background_upgrade(HASH(0x32ea910)) called at /usr/local/cpanel/Whostmgr/API/1/Mysql.pm line 199
Whostmgr::API::1::Mysql::start_background_mysql_upgrade(HASH(0x2351408), Whostmgr::API::1::Utils::Metadata=HASH(0x2496260), HASH(0x3270d90)) called at whostmgr/bin/xml-api.pl line 5233
whostmgr::bin::xml_api::__ANON__(Whostmgr::API::1::Utils::Metadata=HASH(0x2496260), HASH(0x2351408), HASH(0x3270d90), CODE(0x325f3a8)) called at /usr/local/cpanel/Whostmgr/API/1/Data/Wrapper.pm line 240
Whostmgr::API::1::Data::Wrapper::__ANON__() called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Try/Tiny.pm line 100
eval {...} called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Try/Tiny.pm line 91
Try::Tiny::try(CODE(0x32ea460), Try::Tiny::Catch=REF(0x32ea5e0)) called at /usr/local/cpanel/Whostmgr/API/1/Data/Wrapper.pm line 259
Whostmgr::API::1::Data::Wrapper::execute_internal(CODE(0x3270148), HASH(0x2351408), HASH(0x3270d90), HASH(0x326e460), CODE(0x325f3a8)) called at whostmgr/bin/xml-api.pl line 5507
whostmgr::bin::xml_api::runapp(undef, "start_background_mysql_upgrade", HASH(0x3270d90), HASH(0x2351408), 0, CODE(0x325f3a8)) called at whostmgr/bin/xml-api.pl line 5074
whostmgr::bin::xml_api::script(CODE(0x325f3a8), "-json", "start_background_mysql_upgrade") called at whostmgr/bin/xml-api.pl line 5015


[2023-09-11 14:31:16 +1000] warn [Internal Warning while parsing [stdin] 35950] Use of uninitialized value $path in pattern match (m//) at /usr/local/cpanel/Whostmgr/Mysql/Upgrade/Warnings.pm line 456.
at /usr/local/cpanel/Whostmgr/Mysql/Upgrade/Warnings.pm line 456.
Whostmgr::Mysql::Upgrade::Warnings::_maria_systemd_protected_path(undef) called at /usr/local/cpanel/Whostmgr/Mysql/Upgrade/Warnings.pm line 180
Whostmgr::Mysql::Upgrade::Warnings::get_upgrade_warnings(10.6, 10.6) called at /usr/local/cpanel/Whostmgr/Mysql/Upgrade.pm line 1030
Whostmgr::Mysql::Upgrade::_update_conf_with_current_version_and_check_for_blockers(HASH(0x32ea910)) called at /usr/local/cpanel/Whostmgr/Mysql/Upgrade.pm line 528
Whostmgr::Mysql::Upgrade::_validate_conf(HASH(0x32ea910)) called at /usr/local/cpanel/Whostmgr/Mysql/Upgrade.pm line 394
Whostmgr::Mysql::Upgrade::unattended_background_upgrade(HASH(0x32ea910)) called at /usr/local/cpanel/Whostmgr/API/1/Mysql.pm line 199
Whostmgr::API::1::Mysql::start_background_mysql_upgrade(HASH(0x2351408), Whostmgr::API::1::Utils::Metadata=HASH(0x2496260), HASH(0x3270d90)) called at whostmgr/bin/xml-api.pl line 5233
whostmgr::bin::xml_api::__ANON__(Whostmgr::API::1::Utils::Metadata=HASH(0x2496260), HASH(0x2351408), HASH(0x3270d90), CODE(0x325f3a8)) called at /usr/local/cpanel/Whostmgr/API/1/Data/Wrapper.pm line 240
Whostmgr::API::1::Data::Wrapper::__ANON__() called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Try/Tiny.pm line 100
eval {...} called at /usr/local/cpanel/3rdparty/perl/536/cpanel-lib/Try/Tiny.pm line 91
Try::Tiny::try(CODE(0x32ea460), Try::Tiny::Catch=REF(0x32ea5e0)) called at /usr/local/cpanel/Whostmgr/API/1/Data/Wrapper.pm line 259
Whostmgr::API::1::Data::Wrapper::execute_internal(CODE(0x3270148), HASH(0x2351408), HASH(0x3270d90), HASH(0x326e460), CODE(0x325f3a8)) called at whostmgr/bin/xml-api.pl line 5507
whostmgr::bin::xml_api::runapp(undef, "start_background_mysql_upgrade", HASH(0x3270d90), HASH(0x2351408), 0, CODE(0x325f3a8)) called at whostmgr/bin/xml-api.pl line 5074
whostmgr::bin::xml_api::script(CODE(0x325f3a8), "-json", "start_background_mysql_upgrade") called at whostmgr/bin/xml-api.pl line 5015
---
metadata:
command: start_background_mysql_upgrade
reason: "API failure: (XID c53v3m) Provide the “target” parameter for the “Cpanel::DiskCheck::target_has_enough_free_space_to_fit_source_sizes” function."
result: 0
version: 1

Does anyone know how to get around this?

 

[andrew.n]

hm interesting. In WHM under MySQL profile try to disable the active profile and see how that goes then. Do you have enough space on the root partition of the web server?

 

[cPRex]

Even though MySQL is disabled locally, we still detect it and need to ensure it meets the requirements. If you update the local installation, I'd expect ELevate to work properly.

 

[Michael Legg]

Yes, I understand. But I'm a bit concerned that it says I have to upgrade to MySQL 10.6 when there is no such thing as MySQL 10.6.

It clearly has confused my remote MariaDB server with my local server.

Out of sheer optimism, I ran /usr/local/cpanel/bin/whmapi1 start_background_mysql_upgrade version=10.6 anyway and as expected it failed.

 

[Michael Legg]

hm interesting. In WHM under MySQL profile try to disable the active profile and see how that goes then. Do you have enough space on the root partition of the web server?

I'll have to wait until a public holiday or something to disable the active database profile.

 

[Michael Legg]

I noticed that the local MySQL service isn't running which is possibly why cPanel is getting info from my remote profile instead.
I tried to start the local service, but it won't start and there is nothing in the /var/lib/mysql/ error log since 2020.

 

[Michael Legg]

So ... I UNINSTALLED MySQL 5.6, then I installed MySQL 8, then I ran /scripts/elevate-cpanel --check --upgrade-to=almalinux again, and it said ...

You are using MySQL 5.6 server.
This version is not available for AlmaLinux 8.
You first need to update your MySQL server to 8.0 or later."

So there's REALLY something wrong if it thinks I"m running a package that I uninstalled.

Also, the brand new MYSQL 8 server wont start anyway. The error is "Job for mysqld.service failed because the control process exited with error code. See "systemctl status mysqld.service" and "journalctl -xe" for details."

So I thought ... why am i wasting all of this time trying to get software that I neither need nor want to work? So I just uninstalled MYSQL and ran /scripts/elevate-cpanel --check --upgrade-to=almalinux again, and this time it said ...

[WARN] MySQL is disabled. This must be enabled for MySQL upgrade to succeed.
We temporarily will enable it when it is needed to be enabled,
but we reccomend starting the process with MySQL enabled.

So I give up. If I can't even get past the relatively simple issue of upgrading a common piece of software, I don't hold out much hope of a complete change of OS being successful.

 

[cPRex]

Could you submit a ticket to our team so we can check this out directly?

 

[Michael Legg]

Could you submit a ticket to our team so we can check this out directly?

Ticket created # 95126178

 

[cPRex]

As I expected, our team created CPANEL-43328 to let our ELevate team know about this problem. While I don't have a workaround available, other than manually migrating your accounts to a different system, I'll be sure to post updates here if I hear them!