[MDEV-9356] innodb.innodb_bug53290 fails (crashes) on sol10-64 in buildbot Created: 2016-01-04  Updated: 2016-06-22  Resolved: 2016-06-22

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.0
Fix Version/s: 10.0.26

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Blocks
blocks MDEV-7069 Fix buildbot failures in main server ... Stalled
Relates
relates to MDEV-8774 Test innodb.innodb_bug53290 failures ... Closed
Sprint: 10.0.24

 Description   

http://buildbot.askmonty.org/buildbot/builders/sol10-64/builds/4614/steps/test/logs/stdio

innodb.innodb_bug53290 'innodb_plugin'   [ fail ]
        Test ended at 2016-01-03 09:35:10
 
CURRENT_TEST: innodb.innodb_bug53290
mysqltest: At line 20: query 'alter table bug53290 add unique index `idx` (x)' failed: 2013: Lost connection to MySQL server during query
 
The result from queries just before the failure was:
create table bug53290 (x bigint) engine=innodb;
insert into bug53290 () values (),(),(),(),(),(),(),(),(),(),(),();
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
insert into bug53290 select * from bug53290;
alter table bug53290 add unique index `idx` (x);
 
 
Server [mysqld.1 - pid: 3456, winpid: 3456, exit: 256] failed during test run
Server log from this test:
----------SERVER LOG START-----------
160103  9:34: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://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.0.23-MariaDB-log
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=3
max_threads=153
thread_count=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62741 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x0x945edf8
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...
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.0.23/sql/mysqld:my_print_stacktrace+0x1e
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.0.23/sql/mysqld:handle_fatal_signal+0x426
/lib/amd64/libc.so.1:0xdc2e6
/lib/amd64/libc.so.1:0xd0bc2
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.0.23/storage/innobase/ha_innodb.so:0x1750d2 [ Signal 11 (SEGV)]
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.0.23/storage/innobase/ha_innodb.so:0x1758f3
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.0.23/storage/innobase/ha_innodb.so:0xfce40
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.0.23/sql/mysqld:_Z17mysql_alter_tableP3THDPcS1_P14HA_CREATE_INFOP10TABLE_LISTP10Alter_infojP8st_orderb+0x30f7
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.0.23/sql/mysqld:_ZN19Sql_cmd_alter_table7executeEP3THD+0x4ce
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.0.23/sql/mysqld:_Z21mysql_execute_commandP3THD+0x809
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.0.23/sql/mysqld:_Z11mysql_parseP3THDPcjP12Parser_state+0x1b0
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.0.23/sql/mysqld:_Z16dispatch_command19enum_server_commandP3THDPcj+0xeca
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.0.23/sql/mysqld:_Z10do_commandP3THD+0xe7
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.0.23/sql/mysqld:_Z24do_handle_one_connectionP3THD+0x144
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.0.23/sql/mysqld:handle_one_connection+0x42
/export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.0.23/sql/mysqld:pfs_spawn_thread+0x126
/lib/amd64/libc.so.1:0xdbfbb
/lib/amd64/libc.so.1:0xdc1e0
Please read http://dev.mysql.com/doc/refman/5.1/en/resolve-stack-dump.html
and follow instructions on how to resolve the stack trace.
Resolved stack trace is much more helpful in diagnosing the
problem, so please do resolve it
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x8d9ee10): alter table bug53290 add unique index `idx` (x)
 
Connection ID (thread ID): 52
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://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
Writing a core file
----------SERVER LOG END-------------

Possibly something similar was fixed in 10.1 tree in scope of MDEV-8774. However, it's unclear whether 10.1 is currently affected, because the test only fails with InnoDB plugin, and in 10.1 it is not built on sol10-64.



 Comments   
Comment by Jan Lindström (Inactive) [ 2016-06-20 ]

Crash is strange as buildbot tries to compile with argv: ['sh', '-c', u'cd mariadb-10.0.23 && BUILD/compile-solaris-amd64 --extra-configs=--without-plugin_innodb_plugin'], I would assume that means no innodb_plugin ? But this looks like -O2 and nonnull issue.

Comment by Elena Stepanova [ 2016-06-20 ]

As crazy as it is, WITHOUT_PLUGIN_xxx=ON only means "don't build it statically". If there is no WITH_PLUGIN_xxx=OFF option, it means the plugin will be built dynamically if possible.

Comment by Jan Lindström (Inactive) [ 2016-06-21 ]

commit fa10a65dc293c9222687b33379cebf240cc4bf29
Author: Jan Lindström <jan.lindstrom@mariadb.com>
Date: Tue Jun 21 12:37:39 2016 +0300

MDEV-9356: innodb.innodb_bug53290 fails (crashes) on sol10-64 in buildbot

Analysis: In storage/innobase/row/row0merge.cc InnoDB calls
thd_progress_init, thd_progress_report and thd_progress_end
functions. These seem to cause crash on solaris 10 64-bit.

Fix: Disable progress reporting on UNIV_SOLARIS until the
actual issue causing the crash is fixed. The actual bug
is not on InnoDB code base.

Generated at Thu Feb 08 07:34:03 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.