Today I started a slave. Everything went ok, but after a few hours slave began to restarting constantly.
Error log has the following string
06:59:49 UTC - 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=1468006400
read_buffer_size=131072
max_used_connections=3
max_threads=230
thread_count=1
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1936701 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7e2fdc0
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 = 7fb812710818 thread_stack 0x30000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x7753fe]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x41a)[0x65e7da]
/lib/libpthread.so.0(+0xf8f0)[0x7fb943e938f0]
/lib/libc.so.6(+0x12def4)[0x7fb942a22ef4]
/usr/local/mysql/bin/mysqld(_Z23find_field_in_table_refP3THDP10TABLE_LISTPKcjS4_S4_S4_PP4ItembbPjbPS2_+0x272)[0x53f7f2]
/usr/local/mysql/bin/mysqld(_Z20find_field_in_tablesP3THDP10Item_identP10TABLE_LISTS4_PP4Item27find_item_error_report_typebb+0x22d)[0x54001d]
/usr/local/mysql/bin/mysqld(_ZN10Item_field10fix_fieldsEP3THDPP4Item+0x267)[0x671577]
/usr/local/mysql/bin/mysqld(_Z12setup_fieldsP3THDPP4ItemR4ListIS1_E17enum_mark_columnsPS5_b+0x110)[0x53aca0]
/usr/local/mysql/bin/mysqld(_ZN4JOIN7prepareEPPP4ItemP10TABLE_LISTjS1_jP8st_orderS7_S1_S7_P13st_select_lexP18st_select_lex_unit+0x24c)[0x59d31c]
/usr/local/mysql/bin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x7b3)[0x5a9153]
/usr/local/mysql/bin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x174)[0x5ae184]
/usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x3a1b)[0x577b3b]
/usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x189)[0x578529]
/usr/local/mysql/bin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0x9f4)[0x6fcb14]
/usr/local/mysql/bin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_info+0x12d)[0x51bced]
/usr/local/mysql/bin/mysqld[0x5208c0]
/usr/local/mysql/bin/mysqld(handle_slave_sql+0xa6a)[0x52382a]
/lib/libpthread.so.0(+0x69ca)[0x7fb943e8a9ca]
/lib/libc.so.6(clone+0x6d)[0x7fb9429db70d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fb80c394f72): is an invalid pointer
Connection ID (thread ID): 12
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.
120621 10:59:50 mysqld_safe Number of processes running now: 0
120621 10:59:50 mysqld_safe mysqld restarted
120621 10:59:50 InnoDB: The InnoDB memory heap is disabled
120621 10:59:50 InnoDB: Mutexes and rw_locks use GCC atomic builtins
120621 10:59:50 InnoDB: Compressed tables use zlib 1.2.3.3
120621 10:59:50 InnoDB: Using Linux native AIO
120621 10:59:50 InnoDB: Initializing buffer pool, size = 3.0G
120621 10:59:51 InnoDB: Completed initialization of buffer pool
120621 10:59:51 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 15882301722
120621 10:59:51 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...
InnoDB: Doing recovery: scanned up to log sequence number 15886240312
120621 11:00:02 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53
54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 704082290, file name ./mysql-bin.000023
120621 11:00:07 InnoDB: Waiting for the background threads to start
120621 11:00:08 InnoDB: 1.1.8 started; log sequence number 15886240312
120621 11:00:08 [Note] Recovering after a crash using mysql-bin
120621 11:00:17 [Note] Starting crash recovery...
120621 11:00:17 [Note] Crash recovery finished.
120621 11:00:19 [Note] Server hostname (bind-address): '0.0.0.0'; port: 3306
120621 11:00:19 [Note] - '0.0.0.0' resolves to '0.0.0.0';
120621 11:00:19 [Note] Server socket created on IP: '0.0.0.0'.
120621 11:00:19 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000003' at position 507205743, relay log './mysql-relay-bin.000002' position: 506875347
120621 11:00:19 [Note] Event Scheduler: Loaded 0 events
120621 11:00:19 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.25-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 Source distribution
120621 11:00:19 [Note] Event Scheduler: scheduler thread started with id 3
120621 11:00:19 [ERROR] /usr/local/mysql/bin/mysqld: Table './abakan/phpbb_users_birthday' is marked as crashed and should be repaired
And this repeats over and over again.
Maybye this would be helpfull. To me it's not a problem right now - I will recreate my slave, but i Believe it's a bug. I will copy the database files - so if needed I can give them.
Thanks
Edited 1 time(s). Last edit at 06/21/2012 04:29AM by Ilya Antipov.