这两天用MySql客户端ems mysql 去连接mysql时，会弹出"mysqld.exe [3500] 中发生未处理的win32异常"的提示窗口，然后mysql服务就停止了。再安装一个mysql-front还是有这个现象。而从cmd去连接是不会发生这样现象的。不知道是为什么。没有google到什么。有点郁闷。
有劳各路英雄了。 ----------------------------------------------------------- 100613 9:57:12 [Note] Plugin 'FEDERATED' is disabled. 100613 9:57:12 InnoDB: Started; log sequence number 0 2761952 100613 9:57:13 [Note] Event Scheduler: Loaded 0 events 100613 9:57:13 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections. Version: '5.1.45-community' socket: '' port: 3306 MySQL Community Server (GPL) 100613 9:57:57 InnoDB: MySQL and InnoDB data dictionaries are out of sync. InnoDB: Unable to find the AUTOINC column id in the InnoDB table tea/t_equtype. InnoDB: We set the next AUTOINC column value to 0, InnoDB: in effect disabling the AUTOINC next value generation. InnoDB: You can either set the next AUTOINC value explicitly using ALTER TABLE InnoDB: or fix the data dictionary by recreating the table. 100613 9:57:57 InnoDB: Assertion failure in thread 1256 in file .\handler\ha_innodb.cc line 7931 InnoDB: Failing assertion: auto_inc > 0 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-recovery.html InnoDB: about forcing recovery. 100613 9:57:57 - 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=11534336 read_buffer_size=65536 max_used_connections=1 InnoDB: Thread 168 stopped in file .\os\os0sync.c line 501 max_threads=100 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 43895 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.thd: 0x1edc4d0 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... InnoDB: Thread 2168 stopped in file .\os\os0sync.c line 574 InnoDB: Thread 3852 stopped in file .\os\os0sync.c line 271 005AF1D0 mysqld.exe!ha_innobase::innobase_peek_autoinc()[ha_innodb.cc:7931] 005B0ED3 mysqld.exe!ha_innobase::info()[ha_innodb.cc:6542] 00470D1D mysqld.exe!get_schema_tables_record()[sql_show.cc:3718] 0047A6AC mysqld.exe!get_all_tables()[sql_show.cc:3487] 0047BFD3 mysqld.exe!get_schema_tables_result()[sql_show.cc:6134] 00529A69 mysqld.exe!JOIN::exec()[sql_select.cc:1814] 0052A9A2 mysqld.exe!mysql_select()[sql_select.cc:2487] 0052ACDB mysqld.exe!handle_select()[sql_select.cc:269] 0045610C mysqld.exe!execute_sqlcom_select()[sql_parse.cc:5052] 00457E40 mysqld.exe!mysql_execute_command()[sql_parse.cc:2248] 0045C278 mysqld.exe!mysql_parse()[sql_parse.cc:5975] 0045CC93 mysqld.exe!dispatch_command()[sql_parse.cc:1235] 0045D6D7 mysqld.exe!do_command()[sql_parse.cc:878] 0047DEE0 mysqld.exe!handle_one_connection()[sql_connect.cc:1127] 0067E62B mysqld.exe!pthread_start()[my_winthread.c:85] 0065DB33 mysqld.exe!_callthreadstart()[thread.c:293] 2E302E30 Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 03B60180=SELECT * FROM `information_schema`.`TABLES` WHERE `TABLE_SCHEMA`='tea';SELECT * FROM `information_schema`.`ROUTINES` WHERE `ROUTINE_SCHEMA`='tea';SELECT * FROM `information_schema`.`TRIGGERS` WHERE `EVENT_OBJECT_SCHEMA`='tea';SELECT * FROM `information_schema`.`EVENTS` WHERE `EVENT_SCHEMA`='tea' thd->thread_id=1 thd->killed=NOT_KILLED 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 server的bin目录下的libmysql.dll复制到ems mysql相关目录下边。再试试。
-----------------------------------------------------------
100613 9:57:12 [Note] Plugin 'FEDERATED' is disabled.
100613 9:57:12 InnoDB: Started; log sequence number 0 2761952
100613 9:57:13 [Note] Event Scheduler: Loaded 0 events
100613 9:57:13 [Note] C:\Program Files\MySQL\MySQL Server 5.1\bin\mysqld: ready for connections.
Version: '5.1.45-community' socket: '' port: 3306 MySQL Community Server (GPL)
100613 9:57:57 InnoDB: MySQL and InnoDB data dictionaries are out of sync.
InnoDB: Unable to find the AUTOINC column id in the InnoDB table tea/t_equtype.
InnoDB: We set the next AUTOINC column value to 0,
InnoDB: in effect disabling the AUTOINC next value generation.
InnoDB: You can either set the next AUTOINC value explicitly using ALTER TABLE
InnoDB: or fix the data dictionary by recreating the table.
100613 9:57:57 InnoDB: Assertion failure in thread 1256 in file .\handler\ha_innodb.cc line 7931
InnoDB: Failing assertion: auto_inc > 0
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-recovery.html
InnoDB: about forcing recovery.
100613 9:57:57 - 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=11534336
read_buffer_size=65536
max_used_connections=1
InnoDB: Thread 168 stopped in file .\os\os0sync.c line 501
max_threads=100
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 43895 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.thd: 0x1edc4d0
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...
InnoDB: Thread 2168 stopped in file .\os\os0sync.c line 574
InnoDB: Thread 3852 stopped in file .\os\os0sync.c line 271
005AF1D0 mysqld.exe!ha_innobase::innobase_peek_autoinc()[ha_innodb.cc:7931]
005B0ED3 mysqld.exe!ha_innobase::info()[ha_innodb.cc:6542]
00470D1D mysqld.exe!get_schema_tables_record()[sql_show.cc:3718]
0047A6AC mysqld.exe!get_all_tables()[sql_show.cc:3487]
0047BFD3 mysqld.exe!get_schema_tables_result()[sql_show.cc:6134]
00529A69 mysqld.exe!JOIN::exec()[sql_select.cc:1814]
0052A9A2 mysqld.exe!mysql_select()[sql_select.cc:2487]
0052ACDB mysqld.exe!handle_select()[sql_select.cc:269]
0045610C mysqld.exe!execute_sqlcom_select()[sql_parse.cc:5052]
00457E40 mysqld.exe!mysql_execute_command()[sql_parse.cc:2248]
0045C278 mysqld.exe!mysql_parse()[sql_parse.cc:5975]
0045CC93 mysqld.exe!dispatch_command()[sql_parse.cc:1235]
0045D6D7 mysqld.exe!do_command()[sql_parse.cc:878]
0047DEE0 mysqld.exe!handle_one_connection()[sql_connect.cc:1127]
0067E62B mysqld.exe!pthread_start()[my_winthread.c:85]
0065DB33 mysqld.exe!_callthreadstart()[thread.c:293]
2E302E30
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 03B60180=SELECT * FROM `information_schema`.`TABLES` WHERE `TABLE_SCHEMA`='tea';SELECT * FROM `information_schema`.`ROUTINES` WHERE `ROUTINE_SCHEMA`='tea';SELECT * FROM `information_schema`.`TRIGGERS` WHERE `EVENT_OBJECT_SCHEMA`='tea';SELECT * FROM `information_schema`.`EVENTS` WHERE `EVENT_SCHEMA`='tea'
thd->thread_id=1
thd->killed=NOT_KILLED
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.
请参考数据修复文挡，未必能100%成功
http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html