[MDEV-7915] wsrep.foreign_key, wsrep.pool_of_threads, wsrep.mdev_6832 fail sporadically in buildbot Created: 2015-04-06  Updated: 2015-09-15  Resolved: 2015-09-15

Status: Closed
Project: MariaDB Server
Component/s: Galera, Tests
Affects Version/s: 10.1
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Elena Stepanova Assignee: Nirbhay Choubey (Inactive)
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Blocks
is blocked by MDEV-8208 Sporadic SEGFAULT on startup Closed
Relates
relates to MDEV-7069 Fix buildbot failures in main server ... Stalled
Sprint: 10.1.7-1, 10.1.8-1

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-deb-trusty-amd64/builds/1048/steps/test_4/logs/stdio

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



 Comments   
Comment by Elena Stepanova [ 2015-07-03 ]

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:16
 
CURRENT_TEST: wsrep.foreign_key
 
 
Failed to start mysqld.1
mysqltest 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_key
 
150702 16:49:16 [ERROR] mysqld got signal 11 ;
Attempting backtrace. You can use the following information to find out
 
worker[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 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.6-MariaDB-1~squeeze-log
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=0
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 = 62877 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x0x7fcc39812008
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...
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): 2
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

Comment by Elena Stepanova [ 2015-07-03 ]

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

Comment by Elena Stepanova [ 2015-07-19 ]

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

Comment by Elena Stepanova [ 2015-09-05 ]

Same for wsrep.binlog_format
http://buildbot.askmonty.org/buildbot/builders/kvm-deb-precise-amd64/builds/4877/steps/test_4/logs/stdio

Comment by Nirbhay Choubey (Inactive) [ 2015-09-15 ]

Closing as duplicate of MDEV-8208.

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