«
»

ERROR 1577 (HY000) at line 1: Cannot proceed because system tables used by Event Scheduler were found damaged at server start

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:

  1. 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!

Tags: , , , ,

This entry was posted on Friday, April 2nd, 2010 at 16:09 and is filed under MySQL. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

11 Responses to “ERROR 1577 (HY000) at line 1: Cannot proceed because system tables used by Event Scheduler were found damaged at server start”

  1. david Says:
    June 13th, 2010 at 17:15

    worked, thanks. just need two dashes on –verbose –force

  2. Mats Says:
    June 13th, 2010 at 21:40

    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..

  3. brent Says:
    August 23rd, 2010 at 02:23

    Thanks man, worked like a charm.

  4. Super Says:
    September 30th, 2010 at 14:26

    TQ, works well ;)

  5. xdanx Says:
    October 12th, 2010 at 00:23

    Worked beautiful mate, thanks a lot for your help!

    Wish you well,
    Dan

  6. kfb Says:
    January 4th, 2011 at 12:20

    Thanks, that work good, and saved me a lot of time.

    KFB

  7. Torstein Krause Johansen Says:
    June 16th, 2011 at 05:55

    Cheers for that one, just bumped into the same issue when upgrading to Percona 5.5.

  8. Sten Says:
    September 19th, 2011 at 15:52

    Thanks a lot Mats! This is the second time today you save my day!

  9. Oopsbuzz Says:
    December 18th, 2011 at 21:10

    Works fine, thx !!!

  10. C.J. Adams-Collier Says:
    December 22nd, 2011 at 19:31

    Thanks! That fixed ‘er right up!

  11. sebastian Says:
    January 25th, 2012 at 08:59

    And at least with Debian Squeeze to be “–force” the very first parameter in line!

Leave a Reply