Mysql Error 1577
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more
Cannot Proceed Because System Tables Used By Event Scheduler
about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered myisamchk repair Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign mysqlcheck repair up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top MySQL damaged system tables up vote 6 down vote favorite 2 I ran a
Cannot Load From Mysql.proc. The Table Is Probably Corrupted
query that hung my mysql dameon pretty bad. Still not sure what thats about. When I tried to restart MySQL, I was getting errors that the service could not be stopped, so I killed the process (probably not a good idea in hindsight). When I tried to restart the MySQL service I get: $ ERROR 1577 (HY000) at line 1: Cannot proceed because system tables used by Event Scheduler were found damaged at server start Any ideas? mysql event-scheduler share|improve this question edited Jan 23 '15 at 0:54 HopelessN00b 44.4k1798168 asked May 1 '12 at 19:04 TechplexEngineer 16516 add a comment| 1 Answer 1 active oldest votes up vote 9 down vote accepted Go to your MySQL database directory (usually /var/lib/mysql/mysql), and then do a myisamchk to repair all the tables, then try again. It is likely that more than 1 tables were damaged in this case, and you want to fix them all. If you really cannot, you would have to copy it from a backup or an equivalent setup. Please don't say you have no backups :-) share|improve this answer edited Apr 22 '14 at 13:19 famousgarkin 1266 answered May 1 '12 at 19:08 johnshen64 4,733912 4 Thanks! I ended up running $ mysqlcheck --auto-repair --all-databases --password –TechplexEngineer May 1 '12 at 19:24 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Not the answer you're looking for? Browse other questions tagged mysql event-scheduler or ask your own question. asked 4 years ago viewed 5504 times active 1 year ago Related 6Cannot proceed because system tables used by Event Sche
used by Event Scheduler were found damaged at server start" After migrating databases data from FreeBSD MySQL 5.0.83 server to a Debian Squeeze Linux MySQL version 5.1.61, below is a mysql -version issued on both the FreeBSD and the Debian servers freebsd# mysql --version
mysql Ver 14.12 Distrib 5.0.83, for portbld-freebsd7.2 (i386) using 5.2
debian:~# mysql --version
mysql Ver 14.14 Distrib 5.1.61, for debian-linux-gnu (i486) using readline 6.1
The data SQL dump from http://serverfault.com/questions/385015/mysql-damaged-system-tables the FreeBSD server was dumped with following command arguments: freebsd# mysqldump --opt --allow-keywords --add-drop-table --all-databases -u root -p > complete_db_dump.sql
Then I used sftp to transfer complete_db_dump.sql dump to the a brand new installed latest Debian Squeeze 6.0.2. The Debian server was installed using a "clean Debian install" without graphical environment with CD downloaded from debian.org's site. On the http://www.pc-freak.net/blog/how-to-fix-error-1577-hy000-at-line-1-cannot-proceed-because-system-tables-used-by-event-scheduler-were-found-damaged-at-server-start/ Debian machine I imported the dump with command: debian:~# mysq -u root -p < complete_db_dump.sql
Right After the dump was imported I re-started SQL server which was previously installed with: debian:~# apt-get install mysql-server
The error I got after restarting the mysql server: debian:~# #/etc/init.d/mysql restart
was: ERROR 1577 (HY000) at line 1: Cannot proceed because system tables used by Event Scheduler were found damaged at server start
ERROR 1547 (HY000) at line 1: Column count of mysql.proc is wrong. Expected 20, found 16. The table is probably corrupted
This error cost me a lot of nerves and searching in google to solve. It took me like half an hour of serious googling ,until I finally found the FIX!!!: debian:~# mysql_upgrade -u root -h localhost -p --verbose --force
Enter password:
Looking for 'mysql' as: mysql
Looking for 'mysqlcheck' as: mysqlcheck
Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost'
Running 'mysqlcheck' with connection arguments: '--port=3306' '--socket=/var/run/mysqld/mysqld.sock' '--host=localhost'
bible.holy_bible OK
bible.holybible OK
Instagram Involved with Tapte Minner pwned.no Spillhistorie Gamer.no License This work by Mats Lindh is licensed under a Creative Commons http://e-mats.org/2010/04/error-1577-hy000-at-line-1-cannot-proceed-because-system-tables-used-by-event-scheduler-were-found-damaged-at-server-start/ Attribution 3.0 Norway License. About me I’m a PHP and Python developer currently located in Fredrikstad, Norway where I do consulting work and work as a technical lead. My interest include http://tonkersten.com/2012/08/126-mysql-backup-error/ web application development (PHP since 1998), the demoscene (since 1997) and I have a weird fascination for interesting problems and digital maps. Contact me at mats
route to host The remote host or network may be down. Please try the request again. Your cache administrator is webmaster. Generated Fri, 21 Oct 2016 02:17:29 GMT by s_wx1011 (squid/3.5.20)