Server saya mogok hari ini saya pikir karena perintah tabel truncate bersamaan pada salah satu tabel INNODB kami. Server dapat di-restart, tetapi setelah dimulai, setiap kali saya mencoba mengeluarkan perintah SQL, saya mendapatkan kesalahan berikut:
ERROR 2006 (HY000): MySQL server has gone away
Inilah yang terjadi di log:
121206 01:11:12 mysqld restarted
121206 1:11:13 InnoDB: Started; log sequence number 275 559321759
InnoDB: !!! innodb_force_recovery is set to 1 !!!
121206 1:11:13 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.95-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
InnoDB: Error: trying to load index PRIMARY for table
InnoDB: but the index tree has been freed!
121206 1:11:37 - mysqld got signal 11 ;
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=134217728
read_buffer_size=1048576
max_used_connections=1
max_connections=400
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 950272 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x9900950
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...
Cannot determine thread, fp=0x46353fa0, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
(nil)
New value of fp=0x9900950 failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x993e500 =
thd->thread_id=1
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.
Saya telah mencari secara online dan saya mendapat petunjuk bahwa itu adalah bug MySQL, tetapi saya tidak tahu bagaimana menyelesaikannya. Saya menggunakan MySQL versi 5.0.95.
Sepertinya saya harus membuat database baru dan membuang data lama ke yang baru, tetapi bagaimana saya bisa melakukannya jika saya bahkan tidak bisa mengeluarkan perintah SQL apa pun ke yang sekarang?
--- PEMBARUAN ---
Versi: '5.0.95-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Distribusi sumber InnoDB: Kesalahan: mencoba memuat indeks PRIMARY untuk tabel InnoDB: tetapi pohon indeks telah dibebaskan! 121206 4:13:41 - mysqld mendapat sinyal 11; Ini bisa jadi karena Anda menekan bug. Mungkin juga biner ini atau salah satu perpustakaan yang dihubungkan dengannya rusak, tidak dibangun dengan benar, atau salah konfigurasi. Kesalahan ini juga bisa disebabkan oleh kerusakan perangkat keras. Kami akan mencoba yang terbaik untuk mengorek beberapa info yang diharapkan akan membantu mendiagnosis masalah, tetapi karena kami telah crash, ada sesuatu yang salah dan ini mungkin gagal.
key_buffer_size=134217728
read_buffer_size=1048576
max_used_connections=1
max_connections=400
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 950272 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x17fb8950
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...
Cannot determine thread, fp=0x464a3fa0, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
(nil)
New value of fp=0x17fb8950 failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x17ff6500 =
thd->thread_id=3
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.
Number of processes running now: 0
121206 04:13:41 mysqld restarted
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
121206 4:13:42 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...
121206 4:13:43 InnoDB: Started; log sequence number 275 559323148
121206 4:13:43 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.95-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution