Version: '5.5.9-log' socket: '/mysql2/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
110708 17:53:38 [Note] Event Scheduler: scheduler thread started with id 1
110708 17:54:07 InnoDB: Assertion failure in thread 1234340160 in file /export/home/pb2/build/sb_0-2859905-1295554989.11/rpm/BUILD/mysql-5.5.9/mysql-5.5.9/storage/innobase/btr/btr0pcur.c line 425
InnoDB: Failing assertion: btr_page_get_prev(next_page, mtr) == buf_block_get_page_no(btr_pcur_get_block(cursor))
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/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
110708 17:54:07 - 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=209715200
read_buffer_size=262144
max_used_connections=1
max_threads=2000
thread_count=2
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2787581 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.Thread pointer: 0x75b4fa0
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 = 0x499280d0 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x39)[0x7c9669]
/usr/sbin/mysqld(handle_segfault+0x379)[0x4fd889]
/lib64/libpthread.so.0[0x351a00eb10]
/lib64/libc.so.6(gsignal+0x35)[0x3519430265]
/lib64/libc.so.6(abort+0x110)[0x3519431d10]
/usr/sbin/mysqld[0x8983ff]
/usr/sbin/mysqld[0x8510ca]
/usr/sbin/mysqld[0x82d12c]
/usr/sbin/mysqld[0x59333d]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x70)[0x59b710]
/usr/sbin/mysqld[0x5a36d0]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x1298)[0x5b50a8]
/usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x1a9)[0x5b6509]
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x16d)[0x5b6ded]
/usr/sbin/mysqld[0x574fc5]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1b38)[0x577018]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x10b)[0x57b67b]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x14fb)[0x57cbdb]
/usr/sbin/mysqld(_Z10do_commandP3THD+0xc4)[0x57cf54]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x2a5)[0x614d05]
/usr/sbin/mysqld(handle_one_connection+0x54)[0x614e04]
/lib64/libpthread.so.0[0x351a00673d]
/lib64/libc.so.6(clone+0x6d)[0x35194d3d1d]Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7639950): SELECT COUNT(*) FROM `user_dept` LIMIT 0, 1000
Connection ID (thread ID): 2
Status: NOT_KILLEDThe 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.
110708 17:54:07 mysqld_safe Number of processes running now: 0
110708 17:54:07 mysqld_safe mysqld restarted
110708 17:54:07 [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-query-log'/'--slow-query-log-file' instead.
110708 17:54:07 [Note] Plugin 'FEDERATED' is disabled.
110708 17:54:07 InnoDB: The InnoDB memory heap is disabled
110708 17:54:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
110708 17:54:07 InnoDB: Compressed tables use zlib 1.2.3
110708 17:54:07 InnoDB: Using Linux native AIO
110708 17:54:07 InnoDB: Initializing buffer pool, size = 400.0M
110708 17:54:08 InnoDB: Completed initialization of buffer pool
110708 17:54:08 InnoDB: highest supported file format is Barracuda.
110708 17:54:08 InnoDB: Waiting for the background threads to start
110708 17:54:09 InnoDB: 1.1.5 started; log sequence number 3204333514
110708 17:54:09 [Note] Recovering after a crash using mysql-bin
110708 17:54:09 [Note] Starting crash recovery...
110708 17:54:09 [Note] Crash recovery finished.
110708 17:54:09 [Warning] 'proxies_priv' entry '@ root@mysql1' ignored in --skip-name-resolve mode.
110708 17:54:09 [Note] Event Scheduler: Loaded 0 events
110708 17:54:09 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.9-log' socket: '/mysql2/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
110708 17:54:09 [Note] Event Scheduler: scheduler thread started with id 1
110708 17:54:13 [ERROR] Cannot find or open table vgos/message_user from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.110708 17:54:28 InnoDB: Assertion failure in thread 1233684800 in file /export/home/pb2/build/sb_0-2859905-1295554989.11/rpm/BUILD/mysql-5.5.9/mysql-5.5.9/storage/innobase/btr/btr0pcur.c line 425
InnoDB: Failing assertion: btr_page_get_prev(next_page, mtr) == buf_block_get_page_no(btr_pcur_get_block(cursor))
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/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
110708 17:54:28 - 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=209715200
read_buffer_size=262144
max_used_connections=1
max_threads=2000
thread_count=2
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2787581 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.Thread pointer: 0xf454df0
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 = 0x498880d0 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x39)[0x7c9669]
/usr/sbin/mysqld(handle_segfault+0x379)[0x4fd889]
/lib64/libpthread.so.0[0x351a00eb10]
/lib64/libc.so.6(gsignal+0x35)[0x3519430265]
/lib64/libc.so.6(abort+0x110)[0x3519431d10]
/usr/sbin/mysqld[0x8983ff]
/usr/sbin/mysqld[0x8510ca]
/usr/sbin/mysqld[0x82d12c]
/usr/sbin/mysqld[0x59333d]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x70)[0x59b710]
/usr/sbin/mysqld[0x5a36d0]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x1298)[0x5b50a8]
/usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x1a9)[0x5b6509]
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x16d)[0x5b6ded]
/usr/sbin/mysqld[0x574fc5]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1b38)[0x577018]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x10b)[0x57b67b]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x14fb)[0x57cbdb]
/usr/sbin/mysqld(_Z10do_commandP3THD+0xc4)[0x57cf54]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x2a5)[0x614d05]
/usr/sbin/mysqld(handle_one_connection+0x54)[0x614e04]
/lib64/libpthread.so.0[0x351a00673d]
/lib64/libc.so.6(clone+0x6d)[0x35194d3d1d]Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0xf4d9880): SELECT COUNT(*) FROM `user_dept` LIMIT 0, 1000
Connection ID (thread ID): 2
Status: NOT_KILLEDThe 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.
110708 17:54:28 mysqld_safe Number of processes running now: 0现在数据库可以启动，但是user_dept,无法执行select count(*) from user_dept
只要执行select count(*) from user_dept，提示我Error Code : 2003
Can't connect to MySQL server on '192.168.5.91' (10061)
但是可以执行select * from user_dept
110708 17:53:38 [Note] Event Scheduler: scheduler thread started with id 1
110708 17:54:07 InnoDB: Assertion failure in thread 1234340160 in file /export/home/pb2/build/sb_0-2859905-1295554989.11/rpm/BUILD/mysql-5.5.9/mysql-5.5.9/storage/innobase/btr/btr0pcur.c line 425
InnoDB: Failing assertion: btr_page_get_prev(next_page, mtr) == buf_block_get_page_no(btr_pcur_get_block(cursor))
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/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
110708 17:54:07 - 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=209715200
read_buffer_size=262144
max_used_connections=1
max_threads=2000
thread_count=2
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2787581 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.Thread pointer: 0x75b4fa0
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 = 0x499280d0 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x39)[0x7c9669]
/usr/sbin/mysqld(handle_segfault+0x379)[0x4fd889]
/lib64/libpthread.so.0[0x351a00eb10]
/lib64/libc.so.6(gsignal+0x35)[0x3519430265]
/lib64/libc.so.6(abort+0x110)[0x3519431d10]
/usr/sbin/mysqld[0x8983ff]
/usr/sbin/mysqld[0x8510ca]
/usr/sbin/mysqld[0x82d12c]
/usr/sbin/mysqld[0x59333d]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x70)[0x59b710]
/usr/sbin/mysqld[0x5a36d0]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x1298)[0x5b50a8]
/usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x1a9)[0x5b6509]
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x16d)[0x5b6ded]
/usr/sbin/mysqld[0x574fc5]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1b38)[0x577018]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x10b)[0x57b67b]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x14fb)[0x57cbdb]
/usr/sbin/mysqld(_Z10do_commandP3THD+0xc4)[0x57cf54]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x2a5)[0x614d05]
/usr/sbin/mysqld(handle_one_connection+0x54)[0x614e04]
/lib64/libpthread.so.0[0x351a00673d]
/lib64/libc.so.6(clone+0x6d)[0x35194d3d1d]Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7639950): SELECT COUNT(*) FROM `user_dept` LIMIT 0, 1000
Connection ID (thread ID): 2
Status: NOT_KILLEDThe 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.
110708 17:54:07 mysqld_safe Number of processes running now: 0
110708 17:54:07 mysqld_safe mysqld restarted
110708 17:54:07 [Warning] The syntax '--log-slow-queries' is deprecated and will be removed in a future release. Please use '--slow-query-log'/'--slow-query-log-file' instead.
110708 17:54:07 [Note] Plugin 'FEDERATED' is disabled.
110708 17:54:07 InnoDB: The InnoDB memory heap is disabled
110708 17:54:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
110708 17:54:07 InnoDB: Compressed tables use zlib 1.2.3
110708 17:54:07 InnoDB: Using Linux native AIO
110708 17:54:07 InnoDB: Initializing buffer pool, size = 400.0M
110708 17:54:08 InnoDB: Completed initialization of buffer pool
110708 17:54:08 InnoDB: highest supported file format is Barracuda.
110708 17:54:08 InnoDB: Waiting for the background threads to start
110708 17:54:09 InnoDB: 1.1.5 started; log sequence number 3204333514
110708 17:54:09 [Note] Recovering after a crash using mysql-bin
110708 17:54:09 [Note] Starting crash recovery...
110708 17:54:09 [Note] Crash recovery finished.
110708 17:54:09 [Warning] 'proxies_priv' entry '@ root@mysql1' ignored in --skip-name-resolve mode.
110708 17:54:09 [Note] Event Scheduler: Loaded 0 events
110708 17:54:09 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.9-log' socket: '/mysql2/mysql/mysql.sock' port: 3306 MySQL Community Server (GPL)
110708 17:54:09 [Note] Event Scheduler: scheduler thread started with id 1
110708 17:54:13 [ERROR] Cannot find or open table vgos/message_user from
the internal data dictionary of InnoDB though the .frm file for the
table exists. Maybe you have deleted and recreated InnoDB data
files but have forgotten to delete the corresponding .frm files
of InnoDB tables, or you have moved .frm files to another database?
or, the table contains indexes that this version of the engine
doesn't support.
See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.html
how you can resolve the problem.110708 17:54:28 InnoDB: Assertion failure in thread 1233684800 in file /export/home/pb2/build/sb_0-2859905-1295554989.11/rpm/BUILD/mysql-5.5.9/mysql-5.5.9/storage/innobase/btr/btr0pcur.c line 425
InnoDB: Failing assertion: btr_page_get_prev(next_page, mtr) == buf_block_get_page_no(btr_pcur_get_block(cursor))
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/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
110708 17:54:28 - 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=209715200
read_buffer_size=262144
max_used_connections=1
max_threads=2000
thread_count=2
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2787581 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.Thread pointer: 0xf454df0
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 = 0x498880d0 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x39)[0x7c9669]
/usr/sbin/mysqld(handle_segfault+0x379)[0x4fd889]
/lib64/libpthread.so.0[0x351a00eb10]
/lib64/libc.so.6(gsignal+0x35)[0x3519430265]
/lib64/libc.so.6(abort+0x110)[0x3519431d10]
/usr/sbin/mysqld[0x8983ff]
/usr/sbin/mysqld[0x8510ca]
/usr/sbin/mysqld[0x82d12c]
/usr/sbin/mysqld[0x59333d]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x70)[0x59b710]
/usr/sbin/mysqld[0x5a36d0]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x1298)[0x5b50a8]
/usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x1a9)[0x5b6509]
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x16d)[0x5b6ded]
/usr/sbin/mysqld[0x574fc5]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1b38)[0x577018]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x10b)[0x57b67b]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x14fb)[0x57cbdb]
/usr/sbin/mysqld(_Z10do_commandP3THD+0xc4)[0x57cf54]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x2a5)[0x614d05]
/usr/sbin/mysqld(handle_one_connection+0x54)[0x614e04]
/lib64/libpthread.so.0[0x351a00673d]
/lib64/libc.so.6(clone+0x6d)[0x35194d3d1d]Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0xf4d9880): SELECT COUNT(*) FROM `user_dept` LIMIT 0, 1000
Connection ID (thread ID): 2
Status: NOT_KILLEDThe 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.
110708 17:54:28 mysqld_safe Number of processes running now: 0现在数据库可以启动，但是user_dept,无法执行select count(*) from user_dept
只要执行select count(*) from user_dept，提示我Error Code : 2003
Can't connect to MySQL server on '192.168.5.91' (10061)
但是可以执行select * from user_dept
select * from user_dept这个可以执行？
那就赶紧select * into outfile '/home/xxxx' from user_dept
再建个别的表 导入进去 删掉user_dept 最后rename新表
是我增量备份的时候，选错了其实日志序列号吗，不清楚啊。