After moving a complete SQL dump from a MySQL 5.0 server to a MySQL 5.1 server I forgot about any issues stemming from the different versions of MySQL. Importing the old information_schema tables and any possible changes for the mysql table itself made it barf out the error message “ERROR 1577 (HY000) at line 1: Cannot proceed because system tables used by Event Scheduler were found damaged at server start” when trying to connect to the server.
The connection were still made, but obviously something were afoot. A few pages hinted in the direction of using mysql_upgrade to upgrade the now 5.0-compatible tables to the 5.1 format, but mysql_upgrade didn’t seem to want to run (maybe because of a new root password / debian-sys-maint password). The solution was to tell mysql_upgrade to ask for a password, which user it should connect as and which server it should connect to. You should run this command as root (preferrably through sudo) so that it can run mysql_fix_privilege_tables with the correct permissions:
sudo mysql_upgrade -u root -h localhost -p --verbose --force
The --force parameter will make the command run even if it thinks your server already has been upgraded to 5.1 (or the current version if you’re reading this at a later time). It may think this if you’ve already performed parts of the upgrade, but failed when trying to do the mysql_fix_privilege_tables-bit.
And away we went!
23 thoughts on “ERROR 1577 (HY000) at line 1: Cannot proceed because system tables used by Event Scheduler were found damaged at server start”
worked, thanks. just need two dashes on –verbose –force
Oh, sorry. That’s wordpress fubaring things up. Doesn’t seem like I can do very much about it without actually changing the wordpress code itself..
Thanks man, worked like a charm.
TQ, works well ;)
Worked beautiful mate, thanks a lot for your help!
Wish you well,
Thanks, that work good, and saved me a lot of time.
Cheers for that one, just bumped into the same issue when upgrading to Percona 5.5.
Thanks a lot Mats! This is the second time today you save my day!
Works fine, thx !!!
Thanks! That fixed ‘er right up!
And at least with Debian Squeeze to be “–force” the very first parameter in line!
That was exactly what I needed! By the way, Debian Squeeze does not require –force to be the first parameter.
Don’t forget to restart MySQL after running mysql_upgrade!
Thanks a lot, lost TWO days behind this migration. And you solved all that in seconds.
Thanks again :-)
After search in google, this was first.
Hi, you made my day too ;-)
(was after moving 5.0 mysql schemas to a brand new install of v5.1 from squeeze, so I had reimported old system shcemas into mysql, explaining the need for running the update script)
Thank you, friend.
Thanks you !