Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Duplicate
-
10.1(EOL)
-
None
-
10.1.7-1, 10.1.8-1
Description
wsrep.foreign_key 'innodb_plugin' w3 [ fail ]
|
Test ended at 2015-04-04 01:49:53
|
|
|
CURRENT_TEST: wsrep.foreign_key
|
|
|
|
|
Failed to start mysqld.1
|
mysqltest failed but provided no output
|
|
|
|
|
- saving '/run/shm/var/3/log/wsrep.foreign_key-innodb_plugin/' to '/run/shm/var/log/wsrep.foreign_key-innodb_plugin/'
|
|
|
Retrying test wsrep.foreign_key, attempt(2/3)...
|
|
|
worker[3] > Restart - not started
|
***Warnings generated in error logs during shutdown after running tests: wsrep.foreign_key
|
|
|
150404 1:49:51 [ERROR] mysqld got signal 11 ;
|
Attempting backtrace. You can use the following information to find out
|
|
|
wsrep.foreign_key 'innodb_plugin' worker[3] > Restart [mysqld.1 - pid: 30605, winpid: 30605] - running with different options '--log-bin=master-bin --binlog-format=row --innodb_autoinc_lock_mode=2 --wsrep-provider=/usr/lib/galera/libgalera_smm.so --wsrep-cluster-address=gcomm://' != '--ignore-builtin-innodb --plugin-load-add=ha_innodb.so --innodb --innodb-cmpmem --innodb-cmp-per-index --innodb-trx --innodb-locks --innodb-buffer-pool-stats --innodb-buffer-page --innodb-buffer-page-lru --innodb-sys-foreign --innodb-sys-foreign-cols --innodb-sys-tables --innodb-metrics --log-bin=master-bin --binlog-format=row --innodb_autoinc_lock_mode=2 --wsrep-provider=/usr/lib/galera/libgalera_smm.so --wsrep-cluster-address=gcomm://'
|
w3 [ retry-pass ] 12
|
Attachments
Issue Links
Activity
Same for wsrep.pool_of_threads
http://buildbot.askmonty.org/buildbot/builders/kvm-deb-debian6-amd64/builds/3868/steps/test_4/logs/stdio
http://buildbot.askmonty.org/buildbot/builders/kvm-deb-debian6-amd64/builds/3868/steps/test_4/logs/mysqld.1.err.3
Same for wsrep.mdev_6832
http://buildbot.askmonty.org/buildbot/builders/kvm-deb-precise-amd64/builds/4669/steps/test_4/logs/stdio
http://buildbot.askmonty.org/buildbot/builders/kvm-deb-precise-amd64/builds/4669/steps/test_4/logs/mysqld.1.err.1
Same for wsrep.binlog_format
http://buildbot.askmonty.org/buildbot/builders/kvm-deb-precise-amd64/builds/4877/steps/test_4/logs/stdio
It still fails.
http://buildbot.askmonty.org/buildbot/builders/kvm-deb-debian6-amd64/builds/3868/steps/test_4/logs/stdio
worker[2] mysql-test-run: WARNING: Process [mysqld.1 - pid: 26740, winpid: 26740, exit: 256] died after mysql-test-run waited 0.7 seconds for /dev/shm/var/2/run/mysqld.1.pid to be created.wsrep.foreign_key 'innodb_plugin' w2 [ fail ]Test ended at 2015-07-02 16:49:16CURRENT_TEST: wsrep.foreign_keyFailed to start mysqld.1mysqltest failed but provided no output- saving '/dev/shm/var/2/log/wsrep.foreign_key-innodb_plugin/' to '/dev/shm/var/log/wsrep.foreign_key-innodb_plugin/'Retrying test wsrep.foreign_key, attempt(2/3)...worker[2] > Restart - not started***Warnings generated in error logs during shutdown after running tests: wsrep.foreign_key150702 16:49:16 [ERROR] mysqld got signal 11 ;Attempting backtrace. You can use the following information to find outworker[3] mysql-test-run: WARNING: Process [mysqld.1 - pid: 26778, winpid: 26778, exit: 256] died after mysql-test-run waited 0.7 seconds for /dev/shm/var/3/run/mysqld.1.pid to be created.http://buildbot.askmonty.org/buildbot/builders/kvm-deb-debian6-amd64/builds/3868/steps/test_4/logs/mysqld.1.err.2
150702 16:49:16 [ERROR] mysqld got signal 11 ;This could be because you hit a bug. It is also possible that this binaryor 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-bugsWe will try our best to scrape up some info that will hopefully helpdiagnose the problem, but since we have already crashed,something is definitely wrong and this may fail.Server version: 10.1.6-MariaDB-1~squeeze-logkey_buffer_size=1048576read_buffer_size=131072max_used_connections=0max_threads=153thread_count=2It is possible that mysqld could use up tokey_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62877 K bytes of memoryHope that's ok; if not, decrease some variables in the equation.Thread pointer: 0x0x7fcc39812008Attempting backtrace. You can use the following information to find outwhere mysqld died. If you see no messages after this, something wentterribly wrong...2015-07-02 16:49:16 140515160876800 [Note] WSREP: Member 0.0 () synced with group.2015-07-02 16:49:16 140515160876800 [Note] WSREP: Shifting JOINED -> SYNCED (TO: 0)stack_bottom = 0x7fcc3bbfca38 thread_stack 0x48000/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7fcc5199cdae]/usr/sbin/mysqld(handle_fatal_signal+0x4ac)[0x7fcc5150203c]/lib/libpthread.so.0(+0xeff0)[0x7fcc50ad1ff0]/usr/sbin/mysqld(+0x9a1bdc)[0x7fcc518a0bdc]/usr/sbin/mysqld(+0x60c905)[0x7fcc5150b905]/usr/sbin/mysqld(_Z21ha_enable_transactionP3THDb+0x2d)[0x7fcc5150bd5d]/usr/sbin/mysqld(_ZN3THD16init_for_queriesEv+0x94)[0x7fcc51300c24]/usr/sbin/mysqld(start_wsrep_THD+0x44a)[0x7fcc5149c61a]/lib/libpthread.so.0(+0x68ca)[0x7fcc50ac98ca]/lib/libc.so.6(clone+0x6d)[0x7fcc4f01686d]Trying to get some variables.Some pointers may be invalid and cause the dump to abort.Query (0x0):Connection ID (thread ID): 2Status: NOT_KILLEDOptimizer 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