Linux, Mageia, 64 bits

Please run CHECK TABLE mysql.proc.

Hi Elena, here is the output:

--------------

CHECK TABLE mysql.proc

--------------

+------------+-------+----------+----------+

| Table      | Op    | Msg_type | Msg_text |

+------------+-------+----------+----------+

| mysql.proc | check | status   | OK       |

+------------+-------+----------+----------+

Rows in set: 1. Elapsed time: 1 milliseconds.

And you are still getting that error after this?
If so, please attach your server error log, cnf file(s) and the full unabridged output from the client for

CHECK TABLE mysql.proc EXTENDED;

DROP FUNCTION IF EXISTS `UTN_EnvioCorreo`;

Yes I still get the error.

--------------

CHECK TABLE mysql.proc EXTENDED

--------------

+------------+-------+----------+----------+

| Table      | Op    | Msg_type | Msg_text |

+------------+-------+----------+----------+

| mysql.proc | check | status   | OK       |

+------------+-------+----------+----------+

Rows in set: 1. Elapsed time: 2 milliseconds.

--------------

DROP FUNCTION IF EXISTS `UTN_EnvioCorreo`;

--------------

+-------------------------------------------------------------------------------------------------------+

| Could not execute statement. Error: 1728 Cannot load from mysql.proc. The table is probably corrupted |

+-------------------------------------------------------------------------------------------------------+

+-------------------------------------------------------------------------------------------------------+

Rows in set: 0. Elapsed time: 0 seconds.

sql_errors.log my.cnf sql_errors.log

Okay, that's a bit of a mystery, on many levels. For one, your error log looks like you have a rather high log_warnings level, but nothing in the config file hints at that. Possible it's the only file, or not the only file, that the server actually uses. If that's the possibility, SHOW GLOBAL VARIABLES might help.

The partial error log is not particularly helpful, because the important part – server startup – is missing. Can you add a bigger portion, which includes at least the latest server start?
One thing you can see yourself from the error log is that IF EXISTS is irrelevant here, same error is produced on your instance on an attempt to create a function.

Could you please also paste the output of SHOW CREATE TABLE mysql.proc? And if possible, attach mysql/proc.frm, mysql/proc.MYI, mysql/proc.MYD. If you are worried that it might contain confidential information, then at least .frm (it's just the structure).

Was this instance upgraded from some other version of MariaDB/MySQL/whatever?

I attached the requested files, the error log is complete, I mean, I just Copy & Paste the whole file.

It is the default MariaDB version that comes with Mageia 6 64Bits

Hope it helps.

configFile.tar.gz global_variables.txt proc.frm proc.MYD proc.MYI

It does help, thanks.
The table is not corrupt, it just has a wrong structure, apparently coming from a different version, looks like from MySQL, even though created by MariaDB – maybe from a backup made by mysqldump?
Anyway, you need to run mysql_upgrade, it should solve the problem. If it refuses to run saying that the instance has already been upgraded, run mysql_upgrade --force.

Hi Elena,

mysql_upgrade --force fix the problem, sorry for your time and the false bug report.

Best regards
David