MySQL Bugs: #12234: Signal 11 Service Startup Abort For New Installation

Bug #12234	Signal 11 Service Startup Abort For New Installation
Submitted:	27 Jul 2005 23:38	Modified:	29 Jul 2005 12:28
Reporter:	Richard Collette	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0.9	OS:	Windows (Windows XP)
Assigned to:		CPU Architecture:	Any

Description:
Signal 11 error when starting mySql service after fresh installation on Windows XP SP2

Deinstall and reinstall does not work.

How to repeat:
Install Typical
Configure Instance
Developer
Decision Support
Install InoDB to C:\MySQL InnoDB Datafiles
Set root password

Starting service from instance creation or manually gives the following in the application log:

C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-nt: Got signal 11. Aborting!

The system log shows:

The MySQL service was successfully sent a start control.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The MySQL service entered the running state.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The MySQL service terminated unexpectedly.  It has done this 2 time(s).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I guess some problems happens with the InnoDB path or something
related.

Try to start the server using a DOS prompt for to see the errors
messages:

mysqld-nt --defaults-file=the_path_for_my.ini_file --standalone --console

Starting from the command line worked using:

mysqld-nt --defaults-file="c:\Program Files\MySQL\MySQL Server 5.0\my.ini" --standalone --console

The service command was:

"C:\Program Files\MySQL\MySQL Server 5.0\bin\mysqld-max-nt" --defaults-file="C:\Program Files\MySQL\MySQL Server 5.0\my.ini" "MySQL"

I removed the max part and now the service starts.   The install script must be a bit off.

Thanks for your help.
Rich

Could you please explane me a couple of things.
Did you have installed previous version of mysql before ?
if yes: did you deinstall service of  previous version ?

It was a wrong service image path.

I have experienced the same problem and have managed to reproduce and fix the problem.
This problem occurs when you, given the option to change the InnoDB storage path, choose anything else than "Installation Path".
What happens if you don't is; the appropriate path is created and ibdata1 is placed within.
Additionally, ibdata1, ib_logfile0 and ib_logfile1 is created under InstallationPath\data
When reconfiguring (just clicking through all options and respecifying the password), starting the service fails and leaves a message in the log InstallationPath\computername.err:
060324 17:13:58  InnoDB: Setting file C:\Data\ibdata1 size to 10 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Error: all log files must be created at the same time.
InnoDB: All log files must be created also in database creation.
InnoDB: If you want bigger or smaller log files, shut down the
InnoDB: database and make sure there were no errors in shutdown.
InnoDB: Then delete the existing log files. Edit the .cnf file
InnoDB: and start the database again.
060324 17:13:59 [ERROR] Default storage engine (InnoDB) is not available
060324 17:13:59 [ERROR] Aborting

The windows event log system says mysqld-nt got a signal 11.

The issue was solved by manually removing InstallationPath\data\ib_data1, ib_logfile0 and ib_logfile1 before reconfiguring the server.

thanks for the info.. this is the problem I had.. I had it put the databases on another drive and am not using the "Installation Path".

The last comment is confusing.. How is this repaired??  where do i "manually remove the InstallationPath\.....??  Thanks..

Thenx a lot...
i manually (going to the folder where i installed MySql) deleted (choose the files, right click, delete) the files that you mentioned n worked like a charm!
;)