maria-discuss team mailing list archive

[Frank Röhm <francwalter@xxxxxxx>]

>> Am 20.12.2013 13:22, schrieb Frank Röhm:
>>> day before yesterday I updated my MySQL Server 5.5.34 to MariaDB 5.5.34
>>> on my Ubuntu 12.04 Server.
>>>
>>> All went fine but next day, I noticed that the automatic backup script
>>> (automysqlbackup) had errors, I read:
>>>
>>> mysqldump: Couldn't execute 'SELECT /*!40001 SQL_NO_CACHE */ * FROM
>>> `EVENTS`': Cannot proceed because system tables used by Event Scheduler
>>> were found damaged at server start (1577)
>>> mysqldump: Couldn't execute 'show events': Cannot proceed because system
>>> tables used by Event Scheduler were found damaged at server start (1577)
>>
>> looks like you *did not* run "mysql_upgrade -u root -p" after the
migration!
>> you should do this after *any* mysql/mariadb update directly after the
>> service was restarted to prevent from hidden *serious* problems like
>> root not allowed to use several grant-commands because missing columns
>> in the permission tables and such nasty things
>>
>
> You are right, I did the mysql_upgrade only the next day after I noticed
> this issue and after a research about it.
>
> What can I do now?
> Can I play back the information_schema db or ist this not a solution?

And when I had done a mysql_upgrade command the next day, I got this:

This installation of MySQL is already upgraded to 5.5.34-MariaDB, use
--force if you still need to run mysql_upgrade

I guess that means, that this command was already done by the installer
(aptitude). Anyway I haven't read in any of the many MySQL to MariaDB
Upgrade documentations that this command is needed.

Could it be an incompatibility?