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.
LVL 8
Reece DoddsAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Reece DoddsAuthor Commented:
An update on this... If I change the default database engine in my.ini from InnoDB to MyISAM and enable the skip_innodb option, the MySQL service starts.  But none of the websites work properly.  (eg. If I go to a wordpress site, it loads the Wordpress installation wizard instead of the existing website).
0
arnoldCommented:
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.
0
Julian HansenCommented:
Also check the Windows Event log to see if there is any information reported there.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

Tomas Helgi JohannssonCommented:
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
0
Reece DoddsAuthor Commented:
I managed to get it working again late yesterday afternoon by removing the existing ib_logfile* files, the existing MYSERVER.err file (which was 981KB by the way) and making the following changes to the my.ini file:

increased innodb_additional_mem_pool_size from 2M to 100M
increased innodb_buffer_pool_size from 47M to 100M
increased innodb_log_file_size from 24M to 50M

I don't know what possessed me to change these, but I was at a "almost at last resort" stage (which would've been to build a new VM guest and configure IIS/MySQL/PHP from scratch.  How or why these changes made a difference, I don't know.

The old .err file shows (for the last few entries):

Version: '5.1.66-community'  socket: ''  port: 3306  MySQL Community Server (GPL)
130829  9:47:27 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Normal shutdown

130829  9:47:27 [Note] Event Scheduler: Purging the queue. 0 events
130829  9:47:27  InnoDB: Starting shutdown...
130829  9:47:29  InnoDB: Shutdown completed; log sequence number 0 725928381
130829  9:47:29 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Shutdown complete

130829 11:49:13 [Note] Plugin 'FEDERATED' is disabled.
130829 11:49:14  InnoDB: Initializing buffer pool, size = 47.0M
130829 11:49:15  InnoDB: Completed initialization of buffer pool
130829 11:49:18  InnoDB: Started; log sequence number 0 725928381
130829 12:04:26 [Note] Event Scheduler: Loaded 0 events
130829 12:04:26 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections.
Version: '5.1.66-community'  socket: ''  port: 3306  MySQL Community Server (GPL)
130829 12:14:22 [Note] Plugin 'FEDERATED' is disabled.
130829 12:14:22 [Note] Plugin 'InnoDB' is disabled.
130829 12:14:23 [Note] Event Scheduler: Loaded 0 events
130829 12:14:23 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections.
Version: '5.1.66-community'  socket: ''  port: 3306  MySQL Community Server (GPL)
130829 12:28:45 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Normal shutdown

130829 12:28:45 [Note] Event Scheduler: Purging the queue. 0 events
130829 12:28:45 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Shutdown complete

Open in new window


It first failed startup at around 10am after a hardware restart.
0
arnoldCommented:
The entries you included deal with the attempt after you disabled innodb.

There are mysql tunning scripts.
Get phpmyadmin and check its recommendations on how to tune your setup.

Since you use mysql/php not sure why you did not choose to use a Linux VM (centos)
The OS overhead is higher in windows as compared to a Linux.

I'd recommend you try setting up a Linux VM and then use stress test tools to compare the performance of each.
0
Tomas Helgi JohannssonCommented:
Hi!

Consider a mysql upgrade from 5.1.66 to some newer release

http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-67.html
http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-69.html
http://dev.mysql.com/doc/relnotes/mysql/5.1/en/news-5-1-70.html

InnoDB has many bug fixes related to crash recovery in 5.1.67 and 5.1.70

Regards,
     Tomas Helgi
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Reece DoddsAuthor Commented:
self resolved, but a newer release might be the best solution.
1
Reece DoddsAuthor Commented:
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!
0
Tomas Helgi JohannssonCommented:
You're  welcome.

Regards,
    Tomas Helgi
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
MySQL Server

From novice to tech pro — start learning today.