150827 5:28:54 [ERROR] 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.
To report this bug, see http:
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.
Server version: 10.0.20-MariaDB-log
key_buffer_size=536870912
read_buffer_size=131072
max_used_connections=62
max_threads=1502
thread_count=34
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3822319 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x19a89bf8
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 = 0x7f8e7a7dcd78 thread_stack 0x48000
mysys/stacktrace.c:247(my_print_stacktrace)[0xb81c6e]
sql/signal_handler.cc:153(handle_fatal_signal)[0x726cab]
/lib64/libpthread.so.0(+0xf710)[0x7f8eafa8d710]
sql/sql_plist.h:128(I_P_List<MDL_ticket, I_P_List_adapter<MDL_ticket, &(MDL_ticket::next_in_lock), &(MDL_ticket::prev_in_lock)>, I_P_List_null_counter, I_P_List_fast_push_back<MDL_ticket> >::remove(MDL_ticket*))[0x68c800]
sql/sql_plist.h:126(I_P_List<MDL_ticket, I_P_List_adapter<MDL_ticket, &(MDL_ticket::next_in_context), &(MDL_ticket::prev_in_context)>, I_P_List_null_counter, I_P_List_no_push_back<MDL_ticket> >::remove(MDL_ticket*))[0x68c968]
sql/sql_parse.cc:5196(mysql_execute_command(THD*))[0x5acb05]
sql/sql_parse.cc:6529(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x5b325d]
sql/sql_parse.cc:1310(dispatch_command(enum_server_command, THD*, char*, unsigned int))[0x5b4f49]
sql/sql_connect.cc:1378(do_handle_one_connection(THD*))[0x68218e]
sql/sql_connect.cc:1295(handle_one_connection)[0x682262]
/lib64/libpthread.so.0(+0x79d1)[0x7f8eafa859d1]
/lib64/libc.so.6(clone+0x6d)[0x7f8eae19f8fd]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f8b14004c60): is an invalid pointer
Connection ID (thread ID): 1357300
Status: NOT_KILLED
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=on,exists_to_in=on
The manual page at http:information that should help you find out what is causing the crash.
150827 05:28:55 mysqld_safe Number of processes running now: 0
150827 05:28:55 mysqld_safe mysqld restarted
150827 5:28:56 [Note] /usr/sbin/mysqld (mysqld 10.0.20-MariaDB-log) starting as process 25031 ...
150827 5:28:56 [Note] InnoDB: Using mutexes to ref count buffer pool pages
150827 5:28:56 [Note] InnoDB: The InnoDB memory heap is disabled
150827 5:28:56 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
150827 5:28:56 [Note] InnoDB: Memory barrier is not used
150827 5:28:56 [Note] InnoDB: Compressed tables use zlib 1.2.3
150827 5:28:56 [Note] InnoDB: Using Linux native AIO
150827 5:28:56 [Note] InnoDB: Using CPU crc32 instructions
150827 5:28:56 [Note] InnoDB: Initializing buffer pool, size = 12.0G
150827 5:28:56 [Note] InnoDB: Completed initialization of buffer pool
150827 5:28:57 [Note] InnoDB: Highest supported file format is Barracuda.
150827 5:28:57 [Note] InnoDB: Log scan progressed past the checkpoint lsn 114661609834
150827 5:28:57 [Note] InnoDB: Database was not shutdown normally!
150827 5:28:57 [Note] InnoDB: Starting crash recovery.
150827 5:28:57 [Note] InnoDB: Reading tablespace information from the .ibd files...
150827 5:28:58 [Note] InnoDB: Restoring possible half-written data pages
150827 5:28:58 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 114661791274
150827 5:28:59 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
150827 5:29:00 [Note] InnoDB: 128 rollback segment(s) are active.
150827 5:29:00 [Note] InnoDB: Waiting for purge to start
150827 5:29:00 [Note] InnoDB: Percona XtraDB (http:150827 5:29:00 [Note] Plugin 'FEEDBACK' is disabled.
150827 5:29:00 [Note] Server socket created on IP: '::'.
150827 5:29:00 [ERROR] mysqld: Table './mysql/event' is marked as crashed and should be repaired
150827 5:29:00 [Warning] Checking table: './mysql/event'
150827 5:29:00 [ERROR] mysql.event: 1 client is using or hasn't closed the table properly
150827 5:29:00 [Note] Event Scheduler: Loaded 1 event
150827 5:29:00 [Note] Event Scheduler: scheduler thread started with id 1
150827 5:29:00 [Note] /usr/sbin/mysqld: ready for connections.
Hi, I'm attached event, procedure that started at 4 am and file with variables that we used. Now we also have general log enabled for a logging new crashes.