Can’t start Mysql error 1067

By Knight | February 26, 2005

If you install mysql under windows system, sometime it will suddenly unable to start the service,
i face this issue quite a few times already, finally i found a solution for it,

1st step check the error, under your installation path for mysql, check the data/mysql.err, it the error showing you something like this ..

050213 20:43:37 InnoDB: Starting shutdown…
050213 20:43:40 InnoDB: Shutdown completed; log sequence number 0 1051715
050213 20:43:40 [Note] C:\Web\mysql\bin\mysqld-nt: Shutdown complete

this should be the log file having problem !

2nd step remove the ib_logfile0 or ib_logfile1 in the same folder

3rd step restart the mysql …

da da da … mysql service is running again

Tags: mysql

49 Comments

  1. ZEO
    Posted Mon 28th-Feb-2005 at 11:43 pm | Permalink

    use GNU/LINUX b0x for LAMP development

  2. Jean-Yves
    Posted Fri 22nd-Jul-2005 at 5:56 am | Permalink

    THANK YOU! OH THANK YOU!!!!! :)

    You have no idea how long I have been trawling the web trying to get my installation working again.

    I am very grateful to you for solving this.

    Jean-Yves

  3. Sameer
    Posted Tue 25th-Oct-2005 at 2:55 pm | Permalink

    Thanks a lot.

  4. Knight
    Posted Tue 25th-Oct-2005 at 8:27 pm | Permalink

    Welcome glad that help !

  5. KPatrick
    Posted Thu 22nd-Dec-2005 at 7:01 am | Permalink

    First of all, Thank you Thank you Thank you.

    Second, “Holy cow, what a cryptic message.” Is this anywhere in the main documentation of MySQL? I looked quite a bit, but maybe I missed it given my frustration level. I also have spent about four hours trying to figure the problem. It would be nice if the ERROR message gave a bit more information.

  6. Knight
    Posted Thu 22nd-Dec-2005 at 11:47 pm | Permalink

    welcome Patrick, glad that help you

  7. OMac
    Posted Fri 23rd-Dec-2005 at 7:55 am | Permalink

    Thanks a lot for the solution. Does anyone know why it suddenly stops working?

  8. OMac
    Posted Fri 23rd-Dec-2005 at 7:58 am | Permalink

    … I should add that for me the problem seemed to start when I was executing a stored procedure.

  9. Knight
    Posted Fri 23rd-Dec-2005 at 6:06 pm | Permalink

    i have no idea how it start, for me it start when one day i try to run the program ..

  10. alok agarwal
    Posted Fri 5th-May-2006 at 10:45 am | Permalink

    Hi,
    Also the problem is because when you try to insert the columns having a space in the name then also the service cannot get started.

  11. cat
    Posted Fri 14th-Jul-2006 at 5:53 pm | Permalink

    Thanks, had no clue why it was suddenly not working :)

  12. Karim Nagy
    Posted Sun 6th-Aug-2006 at 9:58 pm | Permalink

    Really i dont know how to thank you ..
    i had the same problem .. and it fixed now ..

    Thanks To Much

  13. Marius
    Posted Fri 18th-Aug-2006 at 2:58 am | Permalink

    Thanks for the help, I even tried re-installing mySql
    without luck. Deleted files and mySq

  14. Sergio
    Posted Thu 21st-Sep-2006 at 5:44 pm | Permalink

    I was able to solve my problem with this hint!! Very good!!

  15. Knight
    Posted Sun 24th-Sep-2006 at 10:26 am | Permalink

    Glad this help !

  16. John
    Posted Sun 8th-Oct-2006 at 1:27 am | Permalink

    Thank you! Thank you! Thank you! I was about to have a nervious breakdown until I found this solution. I had NO idea what could have happened!

  17. Bilal Ahmed
    Posted Sun 29th-Oct-2006 at 2:59 pm | Permalink

    i got the same error but my problem was a bit different
    i had a previous installation on my system on C drive and the new one on D drive. i just had to change the my.ini file in c:/windows and its working

  18. Knight
    Posted Fri 3rd-Nov-2006 at 10:41 pm | Permalink

    Bilal , thx for sharing

  19. dEric
    Posted Sat 2nd-Dec-2006 at 4:27 pm | Permalink

    Wow! this helped me a lot… and it was real quick just by doing that. Thanks Knight!

  20. Knight
    Posted Sun 3rd-Dec-2006 at 7:04 am | Permalink

    Welcome dEric

  21. Vicky
    Posted Wed 10th-Jan-2007 at 2:33 am | Permalink

    THANK YOU

    Im happy XD

  22. Slapo
    Posted Sun 14th-Jan-2007 at 4:22 am | Permalink

    After deleting the ib_logfile0 and ib_logfile1 files, I still had the error.
    Guess what helped: adding path to mysql binaries to the system path.
    Thanks for the deleting tip, though :)

  23. Knight
    Posted Sun 14th-Jan-2007 at 10:46 pm | Permalink

    Thanks Slapo, i sure your tips others too

  24. Xster
    Posted Mon 29th-Jan-2007 at 9:24 am | Permalink

    Thx for the tips…
    its really works!
    i’ve been in dilemma around 3 days tries to
    get any solution…and because ur tips mysql is connected again..thx ya!

    p/s: really appreciated! XD

  25. Jonathan Sampson
    Posted Tue 13th-Feb-2007 at 4:26 am | Permalink

    Thank you so much for posting this :) It has been forever since I had to mess with MySQL, and I got a bit rusty ;) I had to go in and change the root password because a buddy of mine had forgotten what he set it to…and then I was faced with a “Sorry…we no wanna boot” issue.

    This worked very well.

    Jonathan Sampson
    http://www.SampsonVideos.com

  26. Aditya Mittal
    Posted Mon 5th-Mar-2007 at 5:48 pm | Permalink

    Wow, thanks a bunch…

  27. gilad fitoussi
    Posted Tue 6th-Mar-2007 at 5:06 am | Permalink

    I had the path in my system path but with no “” so when I have added, it solved the problem

  28. TRolander
    Posted Fri 30th-Mar-2007 at 7:42 am | Permalink

    THANKS!!!!
    Exactly the fix we needed. Our production server was down.

  29. Antonio
    Posted Wed 30th-May-2007 at 11:58 pm | Permalink

    Why ?

    I find this hit from google. After remove any file i find the problem.
    (is my problem).

    After shutdown the machine (launch hour) all is ok but i change one parameter in mysql administrator (only for test).
    Before launch the mysql service not run any way.
    Compare my.ini and my.bak and only have 1 new line

    default-storage-engine=innodb

    remove this line -> mysql OK now

  30. Ben
    Posted Sun 1st-Jul-2007 at 3:06 am | Permalink

    Thanks a bunch Antonio, I’ve had this error several times but deleting the log files always helped. This time I installed it on server 2003 and got this dreaded error.

  31. jesse
    Posted Wed 4th-Jul-2007 at 11:11 am | Permalink

    amazing, thank you.

  32. jesse
    Posted Wed 4th-Jul-2007 at 11:13 am | Permalink

    This error is so strange. I followed a lot of the suggestions offered and it didn’t seem to work. Then I did what they suggested and when it failed I clicked ‘retry’ on the error message and suddenly it worked. Someone in the same situation might give that a try.

  33. Anna Skawi?ska
    Posted Tue 10th-Jul-2007 at 6:09 pm | Permalink

    Unbelievable. 3 years are over, version 5 arrived, yet the bug is still there. I have no idea what could possibly happen, either. Yesterday the service run like hell, and the only thing I did was creating an empty database. Today - it refused to launch, just like yours.

    Thank you very much for your solution.

  34. Steve
    Posted Thu 9th-Aug-2007 at 5:23 am | Permalink

    Just tried to upgrade from 5.0.18 to current - 5.0.45.

    Shutdown the mysql service, installed .msi file yada yada - service wouldn’t start.

    Looked at the log files, did what you suggested and removed (I renamed ib_logfile0 and ib_logfile1, now my err log has this:

    070808 17:17:37 InnoDB: Log file .\ib_logfile0 did not exist: new to be created
    InnoDB: Setting log file .\ib_logfile0 size to 10 MB
    InnoDB: Database physically writes the file full: wait…
    070808 17:17:38 InnoDB: Log file .\ib_logfile1 did not exist: new to be created
    InnoDB: Setting log file .\ib_logfile1 size to 10 MB
    InnoDB: Database physically writes the file full: wait…
    InnoDB: Cannot initialize created log files because
    InnoDB: data files are corrupt, or new data files were
    InnoDB: created when the database was started previous
    InnoDB: time but the database was not shut down
    InnoDB: normally after that.
    070808 17:17:38 [ERROR] Default storage engine (InnoDB) is not available
    070808 17:17:38 [ERROR] Aborting

    Only when I deleted everything (i.e. bye bye databases) was I able to start it up. No huge deal, it’s just a local test/development machine but damn - it should be a more stable process to do a version upgrade!!

  35. steve
    Posted Thu 23rd-Aug-2007 at 1:45 am | Permalink

    Thanks for posting this, worked like a charm.

  36. sajesh_Kerala_india
    Posted Sat 22nd-Sep-2007 at 1:15 pm | Permalink

    Thank you very much for your solution

    but only the problem is that i cannot access it on network……………..pls. help me.

    thanks
    sajesh

  37. Simone
    Posted Sat 29th-Sep-2007 at 9:00 pm | Permalink

    thank you very much!!!

  38. NICKLEZ
    Posted Tue 9th-Oct-2007 at 7:23 pm | Permalink

    COOL. U ARE DA BEST!!!

  39. Dan
    Posted Wed 10th-Oct-2007 at 4:00 pm | Permalink

    Thank you for help. Fixed my problem straight away.

    Many thanks indeed.
    Dan.

  40. Viki
    Posted Thu 11th-Oct-2007 at 1:28 am | Permalink

    Fixed my problem as well! Thanks so much!!!

  41. Roadskater
    Posted Sat 15th-Dec-2007 at 1:31 pm | Permalink

    Hi: There are some other reasons and fixes. If you have no host.MYD (use notepad to create a blank file with that name but you may have others missing too, see below) or if you change the size of the InnoDB log files in my.ini (deleting log files fixes this because it regenerates them). Also if you type alt-fs like I do a lot to save files and goof, like I do, you get “fs” in your my.ini, and mysql will sometimes fail to start for that reason (or any goof in the my.ini). Please see my full descriptions, plus my story of trying to figure it out, here:

    http://roadskater.net/index.php?q=mysql-error-1067-innodb-privilege-tables-host-myd-not-found-fix-plus-ib-logfile0-log-file-different-size
    or:
    http://roadskater.net/index.php?q=node/640

    Hope this helps.
    Roadskater

  42. Sean
    Posted Sun 16th-Dec-2007 at 2:05 pm | Permalink

    Thanks! Got my local development environment back up and running :)

    As a side note, in addition to the _logfile0 and _logfile1 files, I also had to delete my ibdata1 file (which deletes all of the innoDB data). Just a heads up for other people that they may have to delete this file too (my local data didn’t matter, but if you need yours, you really should back up the ibdata1 file somewhere first).

  43. Amardeep
    Posted Thu 24th-Jan-2008 at 7:07 pm | Permalink

    Thanks ,
    it worked like a magic….
    We are using Mysql database for Bugzilla..
    Yesterday I moved the install to new machine..
    I order to Import database in new machine I just copied old data folder in new blank database program files.
    But could not restart the service ..
    when i deleted the log files the service restarted and working fine.

  44. ploft
    Posted Wed 7th-May-2008 at 5:40 am | Permalink

    Grazie;)

  45. Martin
    Posted Thu 10th-Jul-2008 at 7:37 pm | Permalink

    when i start MY sql.. its showing
    could not start Mysql service on local computer
    error:1067 the process terminated unexpectedly

  46. Omar
    Posted Sat 23rd-Aug-2008 at 1:24 am | Permalink

    I think I found a solution. In this case the problem was that the temporal dir was not seted. So after a lot intents just added the tmpdir=C:/temp sentence at my.ini file and it work OK.

    Good luck

    http://dev.mysql.com/doc/refman/5.0/en/cannot-create.html

  47. Joe
    Posted Sat 23rd-Aug-2008 at 2:25 am | Permalink

    TKS TKS TKS!! I reinstalled mysql several times… and no usefull info on foruns! Glad i found your tip!!! You saved my job hehehe!

  48. karen
    Posted Fri 19th-Sep-2008 at 1:13 pm | Permalink

    At first I only removed the ib_logfiles (0 and 1 in my case) and the xxx.err.
    I restarted the mysql service, but got the same error. I then deleted all files in the folder and it worked like a charm.

    Thanks

  49. Alex
    Posted Fri 7th-Nov-2008 at 2:54 pm | Permalink

    Thanks

2 Trackbacks

  1. By The HumaN Post (THP) mysql Error-1067 damn « on Sat 28th-Apr-2007 at 3:56 pm

    [...] can get more details on this error in here. Posted in [...]

  2. By P3VCreation » Blog Archive » Impossible de démarrer mysql : erreur 1067 on Tue 8th-May-2007 at 6:22 pm

    [...] recherches sur le web, j’ai fini par trouver la solution du problème sur le blog “Ah Knight’s Blog” : une erreur dans l’un des fichiers de [...]

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*