0x80000003+mysql_MYSQL服务开启后不到30秒自动关闭 附ERR LOG

thd=00000000Attemptingbacktrace.Youcanusethefollowinginformationtofindoutwheremysqlddied.Ifyouseenomessagesafterthis,somethingwentterriblywrong...0067C04Dmysqld.exe!???Th...

thd=00000000

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...

0067C04D mysqld.exe!???

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.

141017 17:04:24 InnoDB: Started; log sequence number 0 174249098

141017 17:04:24 [Note] MySQL: ready for connections.

Version: '5.0.96-community' socket: '' port: 3306 MySQL Community Edition (GPL)

InnoDB: Dump of the tablespace extent descriptor: len 40; hex 00000000000000cdffffffff00000000000006b600000004baeaaaaaaaaaaaaaabfeffffffffffff; asc ;

InnoDB: Serious error! InnoDB is trying to free page 3744

InnoDB: though it is already marked as free in the tablespace!

InnoDB: The tablespace free space info is corrupt.

InnoDB: You may need to dump your InnoDB tables and recreate the whole

InnoDB: database!

InnoDB: Please refer to

InnoDB: http://dev.mysql.com/doc/refman/5.0/en/forcing-recovery.html

InnoDB: about forcing recovery.

141017 17:04:25InnoDB: Assertion failure in thread 3404 in file .\fsp\fsp0fsp.c line 2981

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.0/en/forcing-recovery.html

InnoDB: about forcing recovery.

141017 17:04:25 - 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=10485760

read_buffer_size=65536

max_used_connections=0

max_connections=1000

threads_connected=0

It is possible that mysqld could use up to

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 330240 K

bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

展开

本文来自互联网用户投稿，文章观点仅代表作者本人，不代表本站立场，不承担相关法律责任。如若转载，请注明出处。 如若内容造成侵权/违法违规/事实不符，请点击【内容举报】进行投诉反馈！