mysqld got signal 11 Hit a bug ?
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MariaDB |
New
|
Undecided
|
Unassigned |
Bug Description
Dear,
This is the many time my server crashes with the same problem, 120819 12:04:11 [ERROR] mysqld got signal 11 ;
This could be because you hit a bug etc.
CentOs 6.2 64Bits.
mariadb-5.5.25
Intel(R) Xeon(R) CPU E31240 @ 3.30GHz
16Go Ram
2 x SSD 128Go SanDisk
1300req/sec average for 3500 DB.
Last crash :
120819 12:04:11 [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: 5.5.25-MariaDB-log
key_buffer_
read_buffer_
max_used_
max_threads=3002
thread_count=30
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x3b85cc0
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 = 0x7f01c4784d98 thread_stack 0x40000
??:0(my_
??:0(handle_
??:0(??
??:0(ha_
??:0(Item_
??:0(Item_
??:0(init_
??:0(JOIN:
??:0(mysql_
??:0(handle_
??:0(execute_
??:0(mysql_
??:0(mysql_
??:0(dispatch_
??:0(do_
??:0(handle_
??:0(??
??:0(??
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f00aa191cd8): is an invalid pointer
Connection ID (thread ID): 434408348
Status: NOT_KILLED
Optimizer switch: index_merge=
Old crash :
120714 23:37:45 [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: 5.5.25-MariaDB-log
key_buffer_
read_buffer_
max_used_
max_threads=3002
thread_count=21
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x43d21b0
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 = 0x7f7034508d98 thread_stack 0x40000
??:0(my_
??:0(handle_
??:0(??
??:0(ha_
??:0(Item_
??:0(Item_
??:0(init_
??:0(JOIN:
??:0(mysql_
??:0(handle_
??:0(execute_
??:0(mysql_
??:0(mysql_
??:0(dispatch_
??:0(do_
??:0(handle_
??:0(??
??:0(??
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f6f0d121fb8): is an invalid pointer
Connection ID (thread ID): 60462379
Status: NOT_KILLED
Optimizer switch: index_merge=
Old Crash :
120716 23:54:48 [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: 5.5.25-MariaDB-log
key_buffer_
read_buffer_
max_used_
max_threads=3002
thread_count=23
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x379e670
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 = 0x7f0f6c4cad98 thread_stack 0x40000
??:0(my_
??:0(handle_
??:0(??
??:0(ha_
??:0(Item_
??:0(Item_
??:0(init_
??:0(JOIN:
??:0(mysql_
??:0(handle_
??:0(execute_
??:0(mysql_
??:0(mysql_
??:0(dispatch_
??:0(do_
??:0(handle_
??:0(??
??:0(??
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f0e5994e648): is an invalid pointer
Connection ID (thread ID): 16992022
Status: NOT_KILLED
Hi,
Do you happen to have any idea what was executed on the server at the time it crashed? Maybe you have a process list monitor, or server general log (a.k.a. SQL log)? Whatever you could provide in regard to the offending query might help to find the reason of the error.
Is it a high-load production server? If not, and since you have been getting the crash repeatedly, maybe you could enable general log for a while and send it to us after the server crashes again?
Thank you.