MySQL Bugs: #11573: Can't Start Server. Got signal 11

Bug #11573	Can't Start Server. Got signal 11
Submitted:	25 Jun 2005 16:11	Modified:	25 Jun 2005 16:58
Reporter:	Bennett Yip Yip	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	4.1.12	OS:	Windows (WinXP)
Assigned to:		CPU Architecture:	Any

Description:
When I install MySQL 4.1.12 into my XP machine, I use the MySQL Server Instance Configuration Wizard 1.0.4 to create a new service.

I can always create a new instance which crash with Signal 11!
and I can also creatw a new instance without crash.

How to repeat:
1. I try to create server instance to run with latin1 as default character set. The wizard fails with "Start service". And I get "Got Signal 11" in the Event viewer.
The following are the options I use in the first instance:
1. Detailed Configuration
2. Developer Machine
3. Multifunctional Database
4. C: \MySQL InnoDB Datadiles\
5. Decision Support (DSS)/ OLAP
6. Enable TCP/IP Networking (Port Number 3306)
7. Standard Character Set
8. Install As Windows Service
9. Include Bin Directory in Windows Path

2. I try to create server instance to run with UTF8 as default character set. The wizard completes the setting and the MySQL is running properly now.
The following are the options I use in the first instance:
1. Detailed Configuration
2. Developer Machine
3. Multifunctional Database
4. C: \MySQL InnoDB Datadiles\
5. Decision Support (DSS)/ OLAP
6. Enable TCP/IP Networking (Port Number 3306)
7. Best Support For Multilingualism
8. Install As Windows Service
9. Include Bin Directory in Windows Path

The only differece in the setting is the selection of default character set. I hope this can solve the "Signal 11" problem.

Environment:
Windows XP Traditional Chinese Home Edition (With SP2 installed)
- My locale is Chinese (Hong Kong SAR). For non-unicode program, it will use Chinese (Taiwan).

Are you trying to upgrade or to install over an older installation ?
Start the server as standalone for to see the error messages:

mysqld-nt --defaults-file=\path_for_my.ini\my.ini --standalone --console

and take a look in the error messages why the server's start is aborting.

I install over an older installation.

As the wizard create backup file of the my.ini, I found the problem ini file.

I rename the backup file to my.ini and run the server as standalone. I see a long error messages with a lots of ZERO and end with the following message:

                                                      ;InnoDB: End of page dump
050626 19:11:25  InnoDB: Page checksum 1575996416, prior-to-4.0.14-form checksum
 1371122432
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
050626 19:11:25 [ERROR] mysqld-nt: Got signal 11. Aborting!

050626 19:11:25 [ERROR] Aborting

050626 19:11:25 [Note] mysqld-nt: Shutdown complete

Remove entirely.  After removing delete any remnants (including the bin directory).

Reboot.

Reinstall.