宕库

2016-12-13 10:17:28 7f7de8469700  InnoDB: Assertion failure in thread 140178744579840 in file row0mysql.cc line 1700
InnoDB: Failing assertion: node->pcur->rel_pos == BTR_PCUR_ON
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
02:17:28 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=268435456
read_buffer_size=268435456
max_used_connections=152
max_threads=151
thread_count=3

connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 79436405 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f7d8c0399d0
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 = 7f7de8468e20 thread_stack 0x40000
/data/eh/mysql5/bin/mysqld(my_print_stacktrace+0x35)[0x8f8e95]
/data/eh/mysql5/bin/mysqld(handle_fatal_signal+0x3e8)[0x66cba8]
/lib64/libpthread.so.0[0x30b120f790]
/lib64/libc.so.6(gsignal+0x35)[0x30b0e32625]
/lib64/libc.so.6(abort+0x175)[0x30b0e33e05]
/usr/local/mysql/bin/mysqld[0x998bb7]
/usr/local/mysql/bin/mysqld[0x9123fe]
/usr/local/mysql/bin/mysqld(_ZN7handler13ha_delete_rowEPKh+0xb2)[0x58ec42]
/usr/local/mysql/bin/mysqld(_ZN21Delete_rows_log_event11do_exec_rowEPK14Relay_log_info+0x2c)[0x88830c]
/usr/local/mysql/bin/mysqld(_ZN14Rows_log_event12do_apply_rowEPK14Relay_log_info+0x2f)[0x88561f]
/usr/local/mysql/bin/mysqld(_ZN14Rows_log_event24do_table_scan_and_updateEPK14Relay_log_info+0x14d)[0x88e51d]
/usr/local/mysql/bin/mysqld(_ZN14Rows_log_event14do_apply_eventEPK14Relay_log_info+0xd30)[0x8909b0]
/usr/local/mysql/bin/mysqld(_ZN9Log_event11apply_eventEP14Relay_log_info+0x6d)[0x88a30d]
/usr/local/mysql/bin/mysqld(_Z26apply_event_and_update_posPP9Log_eventP3THDP14Relay_log_info+0x17b)[0x8cd99b]
/usr/local/mysql/bin/mysqld[0x8ce4c8]
/usr/local/mysql/bin/mysqld(handle_slave_sql+0xcb9)[0x8cf7e9]
/usr/local/mysql/bin/mysqld(pfs_spawn_thread+0x13b)[0xabfb3b]
/lib64/libpthread.so.0[0x30b1207a51]
/lib64/libc.so.6(clone+0x6d)[0x30b0ee893d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 536054
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.

转载于:https://www.cnblogs.com/HarveyBing/p/6170528.html