Question Try our new tool to upgrade your old MariaDB server from Plesk UI

[3gm]

Hello
I have tried to update it but I get a 504 error after 10 minutes analyzing it with mysqlcheck.

Response not successful: Received status code 504

Does anyone know what parameter needs to be adjusted so that the timeout of this process does not interrupt mysqlcheck?

Thank you

 

[pleskpanel]

Probably there are issues on your system with the filesystem or SELinux.

No filesystem issues and the manual approach worked without a problem (no extra steps taken or needed) so we're going to hold off on using this for now in production environments.

 

[othmaqsa]

Hello,

I'm looking to upgrade MariaDB from 10.3.39 to 10.11 through Plesk UI. Is it safe ?

I have already backup all config + files locally.

Thanks.

 

[othmaqsa]

Quick update: I have upgraded to MariaDB 10.11 and all works fine.

 

[jeffersonbruno]

Love the new feature, but I've got a quick question. A few weeks back, I manually updated to version 10.11.6, which is the most recent one supported by Plesk, isn't it? On the Tools & Settings page, there's a message saying, "You are already on the LTS version. Plesk will automatically update to point releases." Is it okay to leave that setting as is, or should I not do that? Usually, I update things with 'apt get upgrade'.

Hi all,

In the latest Plesk Obsidian 18.0.58 we have released our new tool to upgrade MariaDB to a supported LTS branch from Plesk UI.
To upgrade your MariaDB server without this tool you need to execute a lot of steps in SSH terminal on the source and destination version of the MariaDB server.
Our tool checks configuration, performs DB backup, configures MariaDB package repositories, performs the upgrade, and runs necessary post-upgrade actions.

Currently, this function is in the public Beta stage, and would like to ask you to try it and send us your feedback.
To enable the feature, add the following lines to the panel.ini file. You can do it using the command line or our Panel Ini Editor Extension
[databaseManagement

 

[VNick]

Is it okay to leave that setting as is, or should I not do that? Usually, I update things with 'apt get upgrade'.

Should be OK. But you're free to update to point releases in whatever method is convenient for you.

 

[Apparire]

Quick update: I have upgraded to MariaDB 10.11 and all works fine.

I would like to do the same, what plesk version do you have?
I've Plesk Obsidian v18.0.60_build1800240421.18 os_Debian 10.13
Thanks!

 

[Kaspar]

@Apparire see the Plesk documentation on how to upgrade your MariaDB version with the help of the upgrade tool: (Plesk for Linux) Upgrading MariaDB to the Current Long-Term Support Version

 

[pik555]

Hello everyone ..
Plesk latest version with update tool and Centos 7.9
Got this error message on pre upgrade checks

Analyzing databases with mysqlcheck
Restarting MySQL server ...
Running mysqlcheck ...
igostart_igostar.u6mwx_quiz_indx
warning : Found row where the auto_increment column has the value 0
manageme_live.u6mwx_quiz_t_quiz
warning : Found row where the auto_increment column has the value 0
The command exit code: 0


any help ?

 

[othmaqsa]

I would like to do the same, what plesk version do you have?
I've Plesk Obsidian v18.0.60_build1800240421.18 os_Debian 10.13
Thanks!

I have the last update of Plesk: Version 18.0.60 Update #1
Regarding the OS: Ubuntu 20.04.6 LTS

 

[k_szewczuk]

Hello,
we have tried to upgrade MariaDB from 5.5 using the tool. Everything worked fine but it got stuck on "Upgrading the structure of all tables". Sites and server work fine. Is there a way to manually upgrade the structure of all tables or was it finished and just UI got stuck?

We got Plesk latest version and CentOS 7.9

 

[VNick]

Please be advised that we've identified a couple of issues with the latest MariaDB 10.11.8 release. So you might want to hold off MariaDB upgrades until further notice to ensure the upgrade process is smooth and doesn't require manual intervention.

The first is issue is only on Debian-based systems. Packages update may fail due to an incorrect attempt to start mariadb.service from package scripts with a configuration that is not up-to-date.

The second issue is only on systems with old kernel (presumably older than 3.10.0-408). It may also affect Docker installations. After upgrade the service cannot be started by SystemD with message "status=218/CAPABILITIES" as the new AmbientCapabilities specified in the unit file are not supported. To avoid this issue, make sure you're running the latest available kernel before the upgrade.

 

[nissulya]

Plesk Ubuntu 20.4 LTS
Was unabled to upgrade form mariadb 10.3 with the GUI. Got an error
"Running mysqlcheck ...
table nameXYZ
warning : Found row where the auto_increment column has the value 0"

I tried then to upgrade manually and while doing mysqldump got this error: mysqldump: Got error: 1356: "View 'sys.host_summary' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them" when using LOCK TABLES

 

[nissulya]

Plesk Ubuntu 20.4 LTS
Was unabled to upgrade form mariadb 10.3 with the GUI. Got an error
"Running mysqlcheck ...
table nameXYZ
warning : Found row where the auto_increment column has the value 0"

I tried then to upgrade manually and while doing mysqldump got this error: mysqldump: Got error: 1356: "View 'sys.host_summary' references invalid table(s) or column(s) or function(s) or definer/invoker of view lack rights to use them" when using LOCK TABLES

Probably the sys schema came along with the upgrade from mysql to mariadb, but I don't know if it's used anywhere or if I can just drop it safely.

 

[Kaspar@Plesk]

Probably the sys schema came along with the upgrade from mysql to mariadb, but I don't know if it's used anywhere or if I can just drop it safely.

Perhaps this helps: How to fix the sys.host_summary table in MariaDB 10.3.13

 

[nissulya]

Perhaps this helps: How to fix the sys.host_summary table in MariaDB 10.3.13

I did see this post already, my question was if plesk uses sys or can I drop it safely?