MySQL 数据库服务器启动不了

检查一下MYSQL的错误日志，贴出来看一下。

碰到此类问题，建议楼主，首要的是把对应的err日志文件帖出来，甚至你自己都可以发现问题的根源。

下载MYSQL手册，然后执行错误日志。

feizhang666 (feizhang666)
'截至2011-05-13 21:43:02 用户结帖率0.00%当您的问题得到解答后请及时结贴.
http://topic.csdn.net/u/20090501/15/7548d251-aec2-4975-a9bf-ca09a5551ba5.html
http://topic.csdn.net/u/20100428/09/BC9E0908-F250-42A6-8765-B50A82FE186A.html
http://topic.csdn.net/u/20100626/09/f35a4763-4b59-49c3-8061-d48fdbc29561.html8、如何给分和结贴？
http://community.csdn.net/Help/HelpCenter.htm#结帖

如果这样，建议楼主还是先学习一些基础技巧，比如如何在帮助手册中查找东西，如何使用GOGOLE。

前段时间遇到和你一样的问题困惑了我好久。。清理注册表，卸载重装都没好。。最后连系统也重装了问题一个一个的排出最后换了个安装版本（mysql-5.0.22-win32）成功了！！！，你试试吧

110514 14:26:33 [Note] Plugin 'FEDERATED' is disabled.
110514 14:26:33  InnoDB: Initializing buffer pool, size = 47.0M
110514 14:26:33  InnoDB: Completed initialization of buffer pool
InnoDB: The first specified data file D:\MySQL Datafiles\ibdata1 did not exist:
InnoDB: a new database to be created!
110514 14:26:33  InnoDB: Setting file D:\MySQL Datafiles\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.
110514 14:26:33 [ERROR] Plugin 'InnoDB' init function returned error.
110514 14:26:33 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
110514 14:26:33 [ERROR] Unknown/unsupported table type: INNODB
110514 14:26:33 [ERROR] Aborting110514 14:26:33 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: Shutdown complete
式不是这个东西?但是还是有点看不懂呀

下面的是   卸载了mysql重装后的日志文件   还是启动服务器有问题110514 14:52:05 [Note] Plugin 'FEDERATED' is disabled.
110514 14:52:05  InnoDB: Initializing buffer pool, size = 47.0M
110514 14:52:06  InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
110514 14:52:06  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...
InnoDB: Page directory corruption: infimum not pointed to
110514 14:52:06  InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex 中间好多00000000000然后是：                            ;InnoDB: End of page dump
110514 14:52:06  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
InnoDB: Page may be a freshly allocated page
InnoDB: Page directory corruption: supremum not pointed to
110514 14:52:06  InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex
中间好多00000000000                                                                                                                                                                                                                                                                 ;InnoDB: End of page dump
110514 14:52:07  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
InnoDB: Page may be a freshly allocated page
110514 14:52:07InnoDB: Error: trying to access a stray pointer 83483FF8
InnoDB: buf pool start is at 03474000, end at 06374000
InnoDB: Probable reason is database corruption or memory
InnoDB: corruption. If this happens in an InnoDB database recovery, see
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: how to force recovery.
110514 14:52:07  InnoDB: Assertion failure in thread 2496 in file G:\mysql-5.1.55-winbuild\mysql-community-nt-5.1.55-build\storage\innobase\include\buf0buf.ic line 264
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.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
110514 14:52:07 - 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=26214400
read_buffer_size=65536
max_used_connections=0
max_threads=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 58241 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...
005F1E40    mysqld.exe!buf_frame_align()[buf0buf.ic:264]
005D72FC    mysqld.exe!page_dir_slot_get_rec()[page0page.ic:503]
006227B6    mysqld.exe!page_cur_search_with_match()[page0cur.c:351]
005DD5BC    mysqld.exe!btr_cur_search_to_nth_level()[btr0cur.c:521]
00607570    mysqld.exe!btr_pcur_open()[btr0pcur.ic:494]
00608246    mysqld.exe!btr_pcur_open_on_user_rec()[btr0pcur.c:548]
005FDCBA    mysqld.exe!dict_load_indexes()[dict0load.c:610]
005FE027    mysqld.exe!dict_load_sys_table()[dict0load.c:1025]
00613478    mysqld.exe!dict_boot()[dict0boot.c:389]
005C5A8A    mysqld.exe!innobase_start_or_create_for_mysql()[srv0start.c:1529]
005B3778    mysqld.exe!innobase_init()[ha_innodb.cc:2002]
0047FE08    mysqld.exe!ha_initialize_handlerton()[handler.cc:435]
00429CD8    mysqld.exe!plugin_initialize()[sql_plugin.cc:1041]
0042DA24    mysqld.exe!plugin_init()[sql_plugin.cc:1268]
00418346    mysqld.exe!init_server_components()[mysqld.cc:3997]
00418A01    mysqld.exe!win_main()[mysqld.cc:4466]
00418D3B    mysqld.exe!mysql_service()[mysqld.cc:4644]
00661D93    mysqld.exe!_callthreadstart()[thread.c:293]
00661E2C    mysqld.exe!_threadstart()[thread.c:275]
76041194    kernel32.dll!BaseThreadInitThunk()
774BB429    ntdll.dll!RtlInitializeExceptionChain()
774BB3FC    ntdll.dll!RtlInitializeExceptionChain()
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.

调试易

MySQL 数据库服务器启动不了

解决方案 »