that just doesn’t sound right, does it. I just now noticed it when I ran my cron backup manually. Complete error is:
mysqldump: Couldn’t execute ‘SHOW FUNCTION STATUS WHERE Db = ‘your-db-here”: Column count of mysql.proc is wrong. Expected 20, found 16. Created with MySQL 50077, now running 50152. Please use mysql_upgrade to fix this error. (1558)
so I ran mysql_upgrade , errored about password, then I ran mysql_upgrade -p and all was ok. Well, at least from the script point of view.
Running the backup again revealed another error:
Cannot proceed because system tables used by Event Scheduler were found damaged at server start (1577)
Reading about it on the net, somebody suggested a mysql restart after running the mysql_upgrade script adn what do you know, it did it.
Do note that you need to be logged as root for that command line to work. Otherwise, make sure to specify root user in the command line.
One thing that I did notice a while ago was that the “all” backup (which dumps all tables) was failing, but I didn’t give it too much attention since the per-table backups were ok. Seems this upgrade thing solved that issue as well.
This one was simple 🙂