• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved Upgrading from MariaDB version 10.3.39 to MariaDB version 10.11.5

Feruz

Basic Pleskian
Server operating system version
Almalinux 8
Plesk version and microupdate number
Plesk Obsidian 18.0.56.3
Hello everyone,


I had one question to you about upgrading the old version of MariaDB 10.3.39 to the new version of MariaDB 10.11.5.

Currently I am using Plesk version Plesk Obsidian 18.0.56.3 and Almalinux 8 operating system.

So in my server MariaDB to new version 10.11.5 was upgraded but after the upgrade when I wanted to backup my site but unfortunately during backup I get an error ( Unable to make database dump. Error: Failed to execute mysqldump: Exit code: 2: mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db. Cannot load from mysql.proc. The table is probably corrupted (1728 )

Has anyone among you had this problem and could you help me find a solution for this problem?


Thank you very much for your reply.
 
Hello everyone,


I had one question to you about upgrading the old version of MariaDB 10.3.39 to the new version of MariaDB 10.11.5.

Currently I am using Plesk version Plesk Obsidian 18.0.56.3 and Almalinux 8 operating system.

So in my server MariaDB to new version 10.11.5 was upgraded but after the upgrade when I wanted to backup my site but unfortunately during backup I get an error ( Unable to make database dump. Error: Failed to execute mysqldump: Exit code: 2: mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db. Cannot load from mysql.proc. The table is probably corrupted (1728 )

Has anyone among you had this problem and could you help me find a solution for this problem?


Thank you very much for your reply.

Try:

Code:
MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql_upgrade -uadmin
 
Back
Top