Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 5.5.34-galera
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Environment:Centos 6.5 (Final)
Kernel: 2.6.32-431.1.2.0.1.el6.x86_64
Installed on freshly installed server via MariaDB Yum repo
Description
3 server cluster system, identical hardware.
Mysql crash when running the following query:
create table billarchive.inbox2011 select * from billast.inbox where calldate > '2011-01-01 00:00:00' AND calldate < '2012-01-01 00:00:00';
Error reported in mysql.log:
140102 13:51:07 [Note] WSREP: New COMPONENT: primary = yes, bootstrap = no, my_idx = 2, memb_num = 3
140102 13:51:07 [Note] WSREP: STATE EXCHANGE: Waiting for state UUID.
140102 13:51:07 [Note] WSREP: STATE EXCHANGE: sent state msg: 2aa6db6b-73a4-11e3-80a6-bbdf80f27129
140102 13:51:07 [Note] WSREP: STATE EXCHANGE: got state msg: 2aa6db6b-73a4-11e3-80a6-bbdf80f27129 from 0 (cl3.my.server)
140102 13:51:07 [Note] WSREP: STATE EXCHANGE: got state msg: 2aa6db6b-73a4-11e3-80a6-bbdf80f27129 from 2 (cl4.my.server)
140102 13:51:07 [Note] WSREP: STATE EXCHANGE: got state msg: 2aa6db6b-73a4-11e3-80a6-bbdf80f27129 from 1 (cl2.my.server)
140102 13:51:07 [Note] WSREP: Quorum results:
version = 2,
component = PRIMARY,
conf_id = 45,
members = 3/3 (joined/total),
act_id = 2438,
last_appl. = 0,
protocols = 0/4/2 (gcs/repl/appl),
group UUID = 511c6eec-535a-11e3-b65e-c7a157b2072f
140102 13:51:07 [Note] WSREP: Flow-control interval: [28, 28]
140102 13:51:07 [Note] WSREP: New cluster view: global state: 511c6eec-535a-11e3-b65e-c7a157b2072f:2438, view# 46: Primary, number of nodes: 3, my index: 2, protocol version 2
140102 13:51:07 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
140102 13:51:07 [Note] WSREP: Assign initial position for certification: 2438, protocol version: 2
140102 13:51:07 [Note] WSREP: Member 0 (cl3.my.server) synced with group.
140102 13:56:50 [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://kb.askmonty.org/en/reporting-bugs
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: 5.5.34-MariaDB-wsrep
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=20
max_threads=153
thread_count=20
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 466777 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x7f7f6d60b000
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 = 0x7f7f588d4d68 thread_stack 0x48000
??:0(my_print_stacktrace)[0xaad6ee]
??:0(handle_fatal_signal)[0x6ecccb]
??:0(??)[0x7f83bfd1a710]
??:0(MYSQL_BIN_LOG::write(Log_event*, char*))[0x7a7a06]
??:0(THD::binlog_query(THD::enum_binlog_query_type, char const*, unsigned long, bool, bool, bool, int))[0x5673ce]
??:0(select_insert::send_eof())[0x576b81]
??:0(select_create::send_eof())[0x57b15f]
??:0(do_select(JOIN*, List<Item>*, TABLE*, Procedure*))[0x5c6646]
??:0(JOIN::exec())[0x5e7779]
??:0(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*))[0x5e9108]
??:0(handle_select(THD*, LEX*, select_result*, unsigned long))[0x5e9da3]
??:0(mysql_execute_command(THD*))[0x59971e]
??:0(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x599885]
??:0(wsrep_mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x59ab04]
??:0(dispatch_command(enum_server_command, THD*, char*, unsigned int))[0x59ca60]
??:0(do_command(THD*))[0x59d38d]
??:0(do_handle_one_connection(THD*))[0x6595e3]
??:0(handle_one_connection)[0x65979c]
??:0(??)[0x7f83bfd129d1]
??:0(??)[0x7f83be631b6d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f7f6bc5b018): is an invalid pointer
Connection ID (thread ID): 20
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=off
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.
140102 13:56:50 mysqld_safe Number of processes running now: 0
140102 13:56:50 mysqld_safe WSREP: not restarting wsrep node automatically
140102 13:56:50 mysqld_safe mysqld from pid file /var/lib/mysql/cl4.my.server.pid ended
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
Hi Nirbhay.
Thank you for the reply.
Table inbox:
MariaDB [billast]> describe inbox;
--------------------------------------------------------+
| Field | Type | Null | Key | Default | Extra |
--------------------------------------------------------+
| calldate | datetime | NO | MUL | 0000-00-00 00:00:00 | |
| clid | varchar(80) | YES | NULL | ||
| src | varchar(80) | YES | MUL | NULL | |
| dst | varchar(80) | YES | MUL | NULL | |
| dcontext | varchar(80) | YES | NULL | ||
| channel | varchar(80) | YES | NULL | ||
| dstchannel | varchar(80) | YES | NULL | ||
| lastapp | varchar(80) | YES | NULL | ||
| lastdata | varchar(80) | YES | NULL | ||
| duration | int(11) | YES | 0 | ||
| billsec | int(11) | YES | 0 | ||
| disposition | varchar(45) | YES | MUL | NULL | |
| amaflags | int(11) | YES | 0 | ||
| accountcode | varchar(20) | NO | MUL | ||
| uniqueid | varchar(32) | NO | PRI | ||
| userfield | varchar(255) | YES | NULL |
--------------------------------------------------------+
16 rows in set (0.00 sec)
I would provide sample records, but it should not be publicly visible.
Access to cluster is also available.
Hi DIeter,
I am still not able to reproduce this issue.
Can you please post a test case which leads to this problem?
Hi Dieter, Did you notice a similar crash lately? If so, can you try it with the latest server version?
Hi there.
I am currently using Server version: 5.5.36-MariaDB-wsrep MariaDB
Server, wsrep_25.9.r3961.
Do not have any further incidents like this.
Thank you for following up!
Kind regards,
Dieter Smith
Hi Dieter,
Could you please provide us with the table structure and some sample data (records)?