Description:
Installed MySQL 5.5.9. as an Administrator on a fresh Windows 2003 Server machine (no prev. MySQL installed). After walking through the Instance Config Wizard, the service would not start. I then started the mysqld daemon directly from a command window to see what's happening. The result is posted below:
C:\>mysqld --console --verbose --standalone
110314 15:18:02 [Note] Plugin 'FEDERATED' is disabled.
110314 15:18:02 InnoDB: The InnoDB memory heap is disabled
110314 15:18:02 InnoDB: Mutexes and rw_locks use Windows interlocked functions
110314 15:18:02 InnoDB: Compressed tables use zlib 1.2.3
110314 15:18:02 InnoDB: Initializing buffer pool, size = 8.0M
110314 15:18:02 InnoDB: Completed initialization of buffer pool
110314 15:18:02 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
110314 15:18:02 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
110314 15:18:02 InnoDB: Assertion failure in thread 2896 in file ..\..\..\mysql
-5.5.9\storage\innobase\fsp\fsp0fsp.c line 2101
InnoDB: Failing assertion: inode
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
110314 15:18:02 - mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.
key_buffer_size=8388608
read_buffer_size=65536
max_used_connections=0
max_threads=100
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 36517 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
0063D898 mysqld.exe!fseg_inode_get()[fsp0fsp.c:2101]
0063DA77 mysqld.exe!fseg_n_reserved_pages()[fsp0fsp.c:2436]
0060B5BA mysqld.exe!ibuf_init_at_db_start()[ibuf0ibuf.c:550]
006572C6 mysqld.exe!dict_boot()[dict0boot.c:450]
005EAD80 mysqld.exe!innobase_start_or_create_for_mysql()[srv0start.c:1699]
005E298F mysqld.exe!innobase_init()[ha_innodb.cc:2477]
0041BC9D mysqld.exe!ha_initialize_handlerton()[handler.cc:462]
004169A4 mysqld.exe!plugin_initialize()[sql_plugin.cc:1063]
0041ABB4 mysqld.exe!plugin_init()[sql_plugin.cc:1349]
00409B3F mysqld.exe!init_server_components()[mysqld.cc:3869]
0040A49B mysqld.exe!win_main()[mysqld.cc:4433]
0040A843 mysqld.exe!mysql_service()[mysqld.cc:4625]
0040AAF7 mysqld.exe!mysqld_main()[mysqld.cc:4811]
00713D97 mysqld.exe!__tmainCRTStartup()[crt0.c:266]
77E6F23B kernel32.dll!ProcessIdToSessionId()
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
C:\>
How to repeat:
Install MySQL 5.5.9. on Windows 2003 Server, run the Instance Configuration Wizard
