MySQL Bugs: #16079: Could not start the service MySQL5.Error:0

Bug #16079	Could not start the service MySQL5.Error:0
Submitted:	29 Dec 2005 23:39	Modified:	1 Jan 2006 21:52
Reporter:	Ven Grollmus	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	5.0	OS:	Windows (Windows XP Professional SP2)
Assigned to:		CPU Architecture:	Any

Description:
Installing MySQL Server 5.0, and on the Instance Configuration Screen I receive the error 'Could not start the service MySQL5.Error:0"

What can I do to complete the installation?

How to repeat:
Unistalled, and tried re-installing with the same error.

Could you please do the below instructions:

1- Open a DOS prompt console screen.
2- Go to the install \bin directory
3- Issue the below command i.e:

C:\Arquivos de programas\MySQL\MySQL Server 5.0\bin>mysqld-nt --defaults-file="c:\Arquivos de programas\MySQL\MySQL Server 5.0\my.ini" --standalone --console
051229 22:35:53  InnoDB: Started; log sequence number 0 43655
051229 22:35:53 [Note] mysqld-nt: ready for connections.
Version: '5.0.17-nt'  socket: ''  port: 3306  MySQL Community Edition (GPL)

4- Then take a look for a message error, instead of the above ready for connections message.

Thanks in advance.

Based on instructions given, the following results were returned:-

InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
051230 11:58:09 [ERROR] mysqld-nt: Got signal 11. Aborting!

051230 11:58:09 [ERROR] Aborting

051230 11:58:09 [Note] mysqld-nt: Shutdown complete

So you did an upgrade? installing 5.0 server over the older install directory
directory?

If yes, then you have 2 options:

1- If you don't want to keep the older data, then just delete the InnoDB files
    using the Windows explorer and start the server for to create new ones
    according configuration on your my.ini.
2- Uninstall 5.0 and re-install 4.1.XX and perform a dump of your data, then
    install 5.0 on another location and import the data dumped before.

Would be nice you read the upgrade section of our Manual.

No I didn't do an upgrade.

Then we have here an unrelated InnoDB error message while aborting.
Could you please provide the content of your my.ini. Also assuming
that you don't have data for to keep, then delete the InnoDB files:

i.e:

C:\Arquivos de programas\MySQL\MySQL Server 5.0\data>dir
 O volume na unidade C não tem nome.
 O número de série do volume é E8BA-3E5D

 Pasta de C:\Arquivos de programas\MySQL\MySQL Server 5.0\data

29/12/2005  22:42    <DIR>          .
29/12/2005  22:42    <DIR>          ..
29/12/2005  22:42        10.485.760 ibdata1 <<<<<< this
29/12/2005  22:42        10.485.760 ib_logfile0 <<<<<<< this
15/12/2005  13:46        10.485.760 ib_logfile1 <<<<<<< this
29/12/2005  22:35             2.541 light.err
15/12/2005  13:45    <DIR>          mysql
29/12/2005  22:30    <DIR>          test
               4 arquivo(s)     31.459.821 bytes
               4 pasta(s) 17.915.539.456 bytes disponíveis

and start the server how I asked you the first time. If now InnoDB is
able to create the files correctly or display an error message while
creating please provide it.

If the server start, then you shutdown the server with:

\bin>mysqladmin shutdown -uroot

and try to start the service with:

net start mysql

mysql is the service name.

Thanks in advance.

I removed the directories, and re-installed and it installed fine this time.  Thanks for the help.  Do you still require the information out of the INI file?

Thank you for the feedback. I am changing the status for can't repeat
because on my side I was unable to repeat the behavior you experienced,
however would be nice if you can describe the initial situation which provoked
that wrong InnoDB message error, I just assume it was a corrupt InnoDB's files.

It isn't necessary you provide the my.ini file.

The only thing I can think off, was after running the installation, I went through and installed the admin tools, then the Essential installation.  With the Essential installation is when I started getting problems.

I have an experience: error in my.ini (probably mine). Wrong drive for location of  Data file directory. It could help to revise my.ini and correct such mistake.

Okay I have found out that using the default path with the installation causes the installation to fail and the service to not start. If you change the path to the following it will work with no errors

Install path C:\MYSQL5
Data path C:\MYSQL5\Data

if you use the root and don't use long file names it appears to work. Usually in tries to install in "c:\document and setting\username\Application data\MYSQL Server 5.x\" and this causes the error

I had the same error after uninstalling and then a renewed installing of MySQL 5.1

Removing the folder "MySQL" in both "C:\Documents and settings\All Users\Application Data" and "C:\Documents and settings\myprofile\Application Data" (mark: "Application Data" is usually a hidden folder!) solved the problem for me. In those folders there was a subfolder "Data" which I didn't find in the "C:\Program Files\MySQL\MySQL Server 5.1" folder as suggested in some other threads. Te latter appears to be the applicable with version 5.0 but not 5.1.

Obviously uninstalling MySQL 5.1 does not affect the folders in the profile folders (C:\Documents and settings\...")

Regards,

Bert Rievers,
Venlo

Check your Computer Name. It should not be any name which is reserved word by Windows OS like COM1, COM2, etc.

Hi,

I had the same, uninstalled and reinstalled etc...
I have bitdefender 2009, and i thought that it could be blocking the port, so i unchecked the block port scan option and then it worked...
So, check your firewall settings...

Hope it helps.

MYSQL service creates a process called "mysqld.exe"- which you can locate under the running processes of task manager. If MYSQL service is not running you will not be able to find the "mysqld.exe" in processes list- under task manager.

To check whats wrong with the MYSQL service use this command:
mysqld --console. this command should be run from the bin directory of installed MYSQL .

Go to the c:\program files\ mysql\ mysql server 5.1\ bin > directrory and run the command mysqld --console. plz see the screenshot. "This command will tell you anything wrong with the MYSQL SERVICE".

screenshot :

C:\Program Files\MySQL\MySQL Server 5.1>cd bin

C:\Program Files\MySQL\MySQL Server 5.1\bin>mysqld --console
100305 19:40:12 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: Error: log file .\ib_logfile0 is of different size 0 36700160 bytes
InnoDB: than specified in the .cnf file 0 10485760 bytes!
100305 19:40:12 [ERROR] Plugin 'InnoDB' init function returned error.
100305 19:40:12 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

100305 19:40:12 [ERROR] Unknown/unsupported table type: INNODB
100305 19:40:12 [ERROR] Aborting

100305 19:40:12 [Note] mysqld: Shutdown complete

in this case the ib_logfile0 file was bigger then the predfined size.

Solution : is to delete ib_logfile0 and ib_logfile1 files from the C:\Program Files\MySQL\MySQL Server 5.1\data folder and then try to restart the MYSQL service manually. the MYSQL Service wil come up and you will see mysqld.exe process running under process list.
IF YOU GET THE SAME ERROR IN COMAND PROMPT AFTER RUNNING THIS COMMAND THEN U DONT HAVE TO SEARCH NYTHING JUST APPLY THIS SOLUTION N IT WILL WORK .

try to log in using MYSQL ADMINISTRATOR , it will work and if not then configure a new instance and this time it will allow you to create a new instance sucessfully.

NOTE:IF YOUR MYSQL SERVICE NOT RUNNING OR FAILING ->RUN THE "MYSQLD -- CONSOLE" COMMAND IN THE GIVEN DIRECTORY ONLY AND IT WILL SHOW YOU THE ERROR YOUR MYSQL SERVICE IS CONTAING. N WHATEVER ERROR YOU GET IN THE COMMAND PROMPT - SERACH THAT ERROR ON GOOGLE. COZ THERE CAN BE DIFFERENT ERRORS WITH MY SQL SERVICE. MYSQLD -- CONSOLE COMMAND WILL GIVE YOU THE RIGHT DIRECTION TO TROUBLESHOOT.

NOTE ; IF YOU PLAN TO UNINSTALL YOUR MYSQL THEN FIRST STOP THE MYSQL SERVICE FROM SERVICES.MSC IN START - RUN - CMD ,,,,, AND ALSO MAKE SURE U DELETE IT FROM ADD/REMOVE PROGRAMS AND MANUALLY DELETE FROM C:\PROGRAM FILES\ MYSQL SERVER. AND MAKE SURE U RUN "REGEDIT" TO CONFIRM THAT THE MYSQL SERVICE IS REMOVED.

MYSQL service creates a process called "mysqld.exe"- which you can locate under the running processes of task manager. If MYSQL service is not running you will not be able to find the "mysqld.exe" in processes list- under task manager.

To check whats wrong with the MYSQL service use this command:
mysqld --console. this command should be run from the bin directory of installed MYSQL .

Go to the c:\program files\ mysql\ mysql server 5.1\ bin > directrory and run the command mysqld --console. plz see the screenshot. "This command will tell you anything wrong with the MYSQL SERVICE".

screenshot :

C:\Program Files\MySQL\MySQL Server 5.1>cd bin

C:\Program Files\MySQL\MySQL Server 5.1\bin>mysqld --console
100305 19:40:12 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: Error: log file .\ib_logfile0 is of different size 0 36700160 bytes
InnoDB: than specified in the .cnf file 0 10485760 bytes!
100305 19:40:12 [ERROR] Plugin 'InnoDB' init function returned error.
100305 19:40:12 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

100305 19:40:12 [ERROR] Unknown/unsupported table type: INNODB
100305 19:40:12 [ERROR] Aborting

100305 19:40:12 [Note] mysqld: Shutdown complete

in this case the ib_logfile0 file was bigger then the predfined size.

Solution : is to delete ib_logfile0 and ib_logfile1 files from the C:\Program Files\MySQL\MySQL Server 5.1\data folder and then try to restart the MYSQL service manually. the MYSQL Service wil come up and you will see mysqld.exe process running under process list.
IF YOU GET THE SAME ERROR IN COMAND PROMPT AFTER RUNNING THIS COMMAND THEN U DONT HAVE TO SEARCH NYTHING JUST APPLY THIS SOLUTION N IT WILL WORK .

try to log in using MYSQL ADMINISTRATOR , it will work and if not then configure a new instance and this time it will allow you to create a new instance sucessfully.

NOTE:IF YOUR MYSQL SERVICE NOT RUNNING OR FAILING ->RUN THE "MYSQLD -- CONSOLE" COMMAND IN THE GIVEN DIRECTORY ONLY AND IT WILL SHOW YOU THE ERROR YOUR MYSQL SERVICE IS CONTAING. N WHATEVER ERROR YOU GET IN THE COMMAND PROMPT - SERACH THAT ERROR ON GOOGLE. COZ THERE CAN BE DIFFERENT ERRORS WITH MY SQL SERVICE. MYSQLD -- CONSOLE COMMAND WILL GIVE YOU THE RIGHT DIRECTION TO TROUBLESHOOT.

NOTE ; IF YOU PLAN TO UNINSTALL YOUR MYSQL THEN FIRST STOP THE MYSQL SERVICE FROM SERVICES.MSC IN START - RUN - CMD ,,,,, AND ALSO MAKE SURE U DELETE IT FROM ADD/REMOVE PROGRAMS AND MANUALLY DELETE FROM C:\PROGRAM FILES\ MYSQL SERVER. AND MAKE SURE U RUN "REGEDIT" TO CONFIRM THAT THE MYSQL SERVICE IS REMOVED.

GURANTEED SOLUTION - IT WILL WORK.

MYSQL service creates a process called "mysqld.exe"- which you can locate under the running processes of task manager. If MYSQL service is not running you will not be able to find the "mysqld.exe" in processes list- under task manager.

To check whats wrong with the MYSQL service use this command:
mysqld --console. this command should be run from the bin directory of installed MYSQL .

Go to the c:\program files\ mysql\ mysql server 5.1\ bin > directrory and run the command mysqld --console. plz see the screenshot. "This command will tell you anything wrong with the MYSQL SERVICE".

screenshot :

C:\Program Files\MySQL\MySQL Server 5.1>cd bin

C:\Program Files\MySQL\MySQL Server 5.1\bin>mysqld --console
100305 19:40:12 [Note] Plugin 'FEDERATED' is disabled.
InnoDB: Error: log file .\ib_logfile0 is of different size 0 36700160 bytes
InnoDB: than specified in the .cnf file 0 10485760 bytes!
100305 19:40:12 [ERROR] Plugin 'InnoDB' init function returned error.
100305 19:40:12 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

100305 19:40:12 [ERROR] Unknown/unsupported table type: INNODB
100305 19:40:12 [ERROR] Aborting

100305 19:40:12 [Note] mysqld: Shutdown complete

in this case the ib_logfile0 file was bigger then the predfined size.

Solution : is to delete ib_logfile0 and ib_logfile1 files from the C:\Program Files\MySQL\MySQL Server 5.1\data folder and then try to restart the MYSQL service manually. the MYSQL Service wil come up and you will see mysqld.exe process running under process list.
IF YOU GET THE SAME ERROR IN COMAND PROMPT AFTER RUNNING THIS COMMAND THEN U DONT HAVE TO SEARCH NYTHING JUST APPLY THIS SOLUTION N IT WILL WORK .

try to log in using MYSQL ADMINISTRATOR , it will work and if not then configure a new instance and this time it will allow you to create a new instance sucessfully.

NOTE:IF YOUR MYSQL SERVICE NOT RUNNING OR FAILING ->RUN THE "MYSQLD -- CONSOLE" COMMAND IN THE GIVEN DIRECTORY ONLY AND IT WILL SHOW YOU THE ERROR YOUR MYSQL SERVICE IS CONTAING. N WHATEVER ERROR YOU GET IN THE COMMAND PROMPT - SERACH THAT ERROR ON GOOGLE. COZ THERE CAN BE DIFFERENT ERRORS WITH MY SQL SERVICE. MYSQLD -- CONSOLE COMMAND WILL GIVE YOU THE RIGHT DIRECTION TO TROUBLESHOOT.

NOTE ; IF YOU PLAN TO UNINSTALL YOUR MYSQL THEN FIRST STOP THE MYSQL SERVICE FROM SERVICES.MSC IN START - RUN - CMD ,,,,, AND ALSO MAKE SURE U DELETE IT FROM ADD/REMOVE PROGRAMS AND MANUALLY DELETE FROM C:\PROGRAM FILES\ MYSQL SERVER. AND MAKE SURE U RUN "REGEDIT" TO CONFIRM THAT THE MYSQL SERVICE IS REMOVED.

I am using MySQL 5.1.49 (windows XP) and while installing MySQL i got this error..

I fixed it as follows ...
- uninstall MySQL database using control panel
- delete installed MySQL folder manually (i.e. C:\Program Files\MySQL\MySQL Server 5.1 in my case)
- delete MySQL service from registry (i.e. regedit > HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > SErvices > MySQL)
- restart your system
- search MySQL 'application data/allusers/...data' folder and delete MySQL folder having all datafiles and db related files)
- install MySQL .. this time it will be installed

thanks
hina-

For what it is worth, this error will be fixed in MySQL 5.6.8:

InnoDB: Error: log file .\ib_logfile0 is of different size 0 36700160 bytes
InnoDB: than specified in the .cnf file 0 10485760 bytes!

In the case of a size mismatch, we would apply the old logs and then rewrite new ones. Also, with this change, the log file creation and database startup should be more crash-safe. Previously, if mysqld was killed while it was creating the files, it would not recover, and you would have to delete all files before restarting.