Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
5.5.46-galera
-
None
-
3.2.0-4-amd64 #1 SMP Debian 3.2.73-2+deb7u2 x86_64 GNU/Linux
Description
I get sporadic node crashes with :
160317 9:51:14 [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.46-MariaDB-1~wheezy-wsrep-log
|
key_buffer_size=16777216
|
read_buffer_size=131072
|
max_used_connections=180
|
max_threads=1202
|
thread_count=71
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2653835 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
Thread pointer: 0x0x7f6917697000
|
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...
|
160317 09:51:17 mysqld_safe Number of processes running now: 0
|
160317 09:51:17 mysqld_safe WSREP: not restarting wsrep node automatically
|
160317 09:51:17 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
|
in messages:
kernel: [3146277.804321] mysqld[7713] general protection ip:7f6b48f79730 sp:7f6afe4ed3d0 error:0 in libgcc_s.so.1[7f6b48f6a000+15000]
|