MySQL fails to start. Error 1053. Windows Server 2008 R2
I did a server restart for my web server and on restart, MySQL won't start. If I use taskmanager to kill mysqld.exe and try the start from services console, it gets about 50% through the startup, stalls for a long time, and when it eventually finishes it shows the message:
"Windows could not start the MySQL service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion."
I had this once before and from memory all I had to do to correct it was delete the ib_logfile0 and ib_logfile1 files.
This has not helped this time.
Please help! I have 9 websites down and need them backup ASAP.
"Windows could not start the MySQL service on Local Computer. Error 1053: The service did not respond to the start or control request in a timely fashion."
I had this once before and from memory all I had to do to correct it was delete the ib_logfile0 and ib_logfile1 files.
This has not helped this time.
Please help! I have 9 websites down and need them backup ASAP.
Look at the mysql error log.
You might have an error in the my.ini file that is preventing the startup.
Post the my.ini file.
You might have an error in the my.ini file that is preventing the startup.
Post the my.ini file.
Also check the Windows Event log to see if there is any information reported there.
Hi!
Look both into the default mysql log file and the Windows event log file.
If you have an InnoDB storage engine for your tables you will need to the correct crash recovery steps depending on the errors you have.
For some ideas on InnoDB recovery
http://dev.mysql.com/doc/refman/5.5/en/innodb-backup.html
http://tech.amikelive.com/node-36/mysql-50-recovering-crashedcorrupted-innodb-database/
http://dba.stackexchange.com/questions/21146/mysql-innodb-keeps-crashing-how-to-recover
http://dracoblue.net/dev/mysql-with-innodb-crashes-always-on-startup/190/
Regards,
Tomas Helgi
Look both into the default mysql log file and the Windows event log file.
If you have an InnoDB storage engine for your tables you will need to the correct crash recovery steps depending on the errors you have.
For some ideas on InnoDB recovery
http://dev.mysql.com/doc/refman/5.5/en/innodb-backup.html
http://tech.amikelive.com/node-36/mysql-50-recovering-crashedcorrupted-innodb-database/
http://dba.stackexchange.com/questions/21146/mysql-innodb-keeps-crashing-how-to-recover
http://dracoblue.net/dev/mysql-with-innodb-crashes-always-on-startup/190/
Regards,
Tomas Helgi
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
self resolved, but a newer release might be the best solution.
ASKER
Just an update on this... I did an upgrade to 5.1.70 and after cleaning up a little bit of a mess, I have found MySQL to be much more stable and really like the system tray monitor feature of the new version.
Thanks for the suggestion Tomas!
Thanks for the suggestion Tomas!
You're welcome.
Regards,
Tomas Helgi
Regards,
Tomas Helgi
ASKER