Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.0(EOL), 10.1(EOL), 10.2(EOL)
-
None
-
10.0.20, 2017-02, 10.3.6-1
Description
spider/bg.ha w3 [ fail ]
|
Test ended at 2015-04-04 02:59:26
|
|
CURRENT_TEST: spider/bg.ha
|
|
|
The server [mysqld.3.2 - pid: 5373, winpid: 5373, exit: 256] crashed while running 'check warnings'
|
Server log from this test:
|
----------SERVER LOG START-----------
|
150404 2:59:25 [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: 10.1.4-MariaDB-1~precise-wsrep-log
|
key_buffer_size=1048576
|
read_buffer_size=131072
|
max_used_connections=2
|
max_threads=153
|
thread_count=2
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61901 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
Thread pointer: 0x0xaea8e008
|
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...
|
----------SERVER LOG END-------------
|
mysqltest failed but provided no output
|
The result from queries just before the failure was:
|
< snip >
|
for master_1
|
for child2
|
child2_1
|
child2_2
|
child2_3
|
for child3
|
child3_1
|
child3_2
|
child3_3
|
for master_1
|
for child2
|
child2_1
|
child2_2
|
child2_3
|
for child3
|
child3_1
|
child3_2
|
child3_3
|
|
end of test
|
|
|
|
- saving '/run/shm/var/3/log/spider/bg.ha/' to '/run/shm/var/log/bg.ha/'
|
Attachments
Issue Links
- blocks
-
MDEV-10231 mysqld got signal 11 without visible problem
- Closed
- causes
-
MDEV-27575 Spider: UBSAN member access within null pointer of type 'struct st_plugin_int and SIGSEGV in intern_plugin_lock on SHUTDOWN when setting Spider as default storage engine (temporary or global)
- Closed
-
MDEV-32796 Spider uninstall fails with "plugin busy"
- Open
- relates to
-
MDEV-8474 InnoDB sets per-connection data unsafely
- Closed
-
MDEV-12900 spider tests failed in buildbot with valgrind
- Closed
-
MDEV-7069 Fix buildbot failures in main server trees
- Stalled