DROP DATABASE崩溃mysql服务器

时间:2014-04-18 10:57:27

标签: mysql

当我想要删除数据库时,我遇到了一些问题。

执行时:

DROP DATABASE `mydb`;

MySQL返回:

Error Code: 2013. Lost connection to MySQL server during query

(从phpmyadmin执行,我已断开连接并重定向到登录名/密码)

问题可能是一个幻想表。

如果我执行:

CHECK TABLE `mydb`.`mytable`

我有:

Error Code: 1146. Table 'mydb.mytable' doesn't exist

但如果我执行:

CREATE TABLE IF NOT EXISTS `mydb`.`mytable` ...

我有:

Error Code: 1050. Table '`mydb`.`mytable`' already exists

“SELECT *”表示它不存在。

我在执行DROP DATABASE时尝试过innodb_force_recovery:

InnoDB: Load table 'mydb/mytable' failed, the table has missing foreign key indexes. Turn off 'foreign_key_checks' and try again.140417 11:09:55 InnoDB: Assertion failure in thread 2797190000 in file row0mysql.c line 3683
InnoDB: Failing assertion: table
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/...-recovery.html
InnoDB: about forcing recovery.
09:09:55 UTC - mysqld got signal 6 ;
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=16777216
read_buffer_size=131072
max_used_connections=1
max_threads=151
thread_count=1
connection_count=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346075 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0xffffffffb9523670
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...
stack_bottom = ffffffffa6b9b32c thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x33)[0xb7329743]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0xb71ca984]
[0xb6e7f400]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(abort+0x182)[0xb6b8bd72]
/usr/sbin/mysqld(+0x4e1e3b)[0xb737fe3b]
/usr/sbin/mysqld(+0x4c8d6a)[0xb7366d6a]
/usr/sbin/mysqld(+0x32ca05)[0xb71caa05]
/usr/sbin/mysqld(_Z24plugin_foreach_with_maskP3THDPFcS0_P13st_plugin_intPvEijS3_+0x1d1)[0xb70ac121]
/usr/sbin/mysqld(_Z16ha_drop_databasePc+0x3f)[0xb71cbb9f]
/usr/sbin/mysqld(_Z11mysql_rm_dbP3THDPcbb+0xc13)[0xb707b073]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x4477)[0xb709fff7]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x254)[0xb70a2f54]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x2000)[0xb70a5910]
/usr/sbin/mysqld(_Z10do_commandP3THD+0xce)[0xb70a63de]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x123)[0xb7155983]
/usr/sbin/mysqld(handle_one_connection+0x50)[0xb7155ab0]
/lib/i386-linux-gnu/i686/cmov/libpthread.so.0(+0x5c39)[0xb6e5dc39]
/lib/i386-linux-gnu/i686/cmov/libc.so.6(clone+0x5e)[0xb6c34d4e]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (ffffffffb9599500): DROP DATABASE `mydb`
Connection ID (thread ID): 2
Status: 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.

想法?

3 个答案:

答案 0 :(得分:0)

可能数据文件或.frm文件已消失。

答案 1 :(得分:0)

数天以来,我一直试图为同一问题找到解决方案。之后,我通过禁用 InnoDB 解决了它。实际上,禁用 InnoDB 后,我可以再次创建表作为 MyISAM。然后我启用了 InnoDB。在MySql(MariaDB)的日志中,依然报错无法加载表。但是,我可以使用新的 MyISAM 表进行计算。

顺便说一下,我删除并重新创建了数据库,但并没有解决问题。删除数据库时,出现“连接丢失”错误。禁用 InnoDB 后,我成功删除了数据库。

要禁用 InnoDB,在 my.cnf 中写入以下几行并重新启动 mysql 服务。

[mysqld]
skip-innodb
default-storage-engine = myisam

将丢失的表重新创建为 MyISAM 后,我启用了 InnoDB。

答案 2 :(得分:-1)

请检查Windows max_allowed_packet内的my.ini值和Linux my.cnf,然后增加值,然后重新启动服务才能生效。这应该可以解决问题。