|
楼主 |
发表于 2014-2-13 12:23:20
|
显示全部楼层
yinlun 发表于 2014-2-13 11:38
在命令控制台里运行mysql服务,再看看服务关闭的信息
或者可以打开mysql的日志看 ...
140213 12:21:29 [ERROR] Innodb could not find key n 0 with name SYS_C0026460 f
rom dict cache for table justep_oa/oa_am_fonds
140213 12:21:29 - 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=268435456
read_buffer_size=1048576
max_used_connections=3
max_connections=100
threads_connected=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 466944
K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=150A4D90
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...
0066A975 mysqld.exe!???
0043FC03 mysqld.exe!???
004407A9 mysqld.exe!???
00440D26 mysqld.exe!???
00551C61 mysqld.exe!???
0055146F mysqld.exe!???
005644AF mysqld.exe!???
00565585 mysqld.exe!???
00565BC4 mysqld.exe!???
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 1509D940=SELECT count(*) FROM OA_AM_FONDS OA_AM_Fonds
thd->thread_id=4
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.
|
|