Description:
we have a replication setup in concern. till yesterday all are fine. today morning mysql db restarted abruptly. since then, whenever we use check table, show master status, show table staus commands, mysql restarts immediately.also lot of information entered in error log like below.
InnoDB: Last MySQL binlog file position 0 29986, file name ./Beacondbrw-bin.000052
100831 9:18:05 InnoDB: Started; log sequence number 0 331559693
100831 9:18:05 [Note] Recovering after a crash using Beacondbrw-bin
100831 9:18:05 [Note] Starting crash recovery...
100831 9:18:05 [Note] Crash recovery finished.
100831 9:18:05 [Warning] 'user' entry 'root@Beacondbrw' ignored in --skip-name-resolve mode.
100831 9:18:05 [Warning] 'user' entry '@Beacondbrw' ignored in --skip-name-resolve mode.
100831 9:18:05 [Warning] 'user' entry 'beacon@Beaconcore' ignored in --skip-name-resolve mode.
100831 9:18:05 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Pleas
e use '--relay-log=Beacondbrw-relay-bin' to avoid this problem.
100831 9:18:05 [Note] Event Scheduler: Loaded 0 events
100831 9:18:05 [Note] /usr/local/MySQL-5.1.34/bin/mysqld: ready for connections.
Version: '5.1.34-log' socket: '/tmp/mysql3306.sock' port: 3306 MySQL Community Server (GPL)
100831 9:19:01 - 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=1073741824
read_buffer_size=262144000
max_used_connections=4
max_threads=300
threads_connected=4
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3655542 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0xa549568
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 = 0x5da823b8 thread_stack 0x30000
/usr/local/MySQL-5.1.34/bin/mysqld(my_print_stacktrace+0x21)[0x84d6981]
/usr/local/MySQL-5.1.34/bin/mysqld(handle_segfault+0x381)[0x8200291]
[0x281420]
/usr/local/MySQL-5.1.34/bin/mysqld(_ZN10ha_archive8optimizeEP3THDP15st_ha_check_opt+0x2c0)[0x8385330]
/usr/local/MySQL-5.1.34/bin/mysqld(_ZN10ha_archive6repairEP3THDP15st_ha_check_opt+0x2a)[0x8382d1a]
/usr/local/MySQL-5.1.34/bin/mysqld(_ZN10ha_archive16check_and_repairEP3THD+0x30)[0x8383040]
/usr/local/MySQL-5.1.34/bin/mysqld(_ZN12ha_partition16check_and_repairEP3THD+0x24)[0x82f7604]
/usr/local/MySQL-5.1.34/bin/mysqld[0x824e4be]
/usr/local/MySQL-5.1.34/bin/mysqld(_Z10open_tableP3THDP10TABLE_LISTP11st_mem_rootPbj+0x5cc)[0x824eaec]
/usr/local/MySQL-5.1.34/bin/mysqld(_Z11open_tablesP3THDPP10TABLE_LISTPjj+0x678)[0x824fb38]
How to repeat:
have to have a replication setup and then we have to issue check table command in master db
Suggested fix:
none
