Alice Sherepa added a comment - 2017-08-15 07:30 spider/bg.ha_part failed in buildbot http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest/builds/9804/steps/test_5/logs/stdio spider/bg.ha_part w2 [ fail ] Test ended at 2017-08-14 17:48:51   CURRENT_TEST: spider/bg.ha_part mysqltest: In included file "/mnt/buildbot/build/mariadb-10.1.27/storage/spider/mysql-test/spider/bg/t/../include/../../include/deinit_spider.inc": included from /mnt/buildbot/build/mariadb-10.1.27/storage/spider/mysql-test/spider/bg/t/../include/ha_deinit_child3_2.inc at line 2: included from /mnt/buildbot/build/mariadb-10.1.27/storage/spider/mysql-test/spider/bg/t/ha_test_deinit.inc at line 27: included from /mnt/buildbot/build/mariadb-10.1.27/storage/spider/mysql-test/spider/bg/t/ha_part.test at line 1011: At line 10: query 'DROP TABLE IF EXISTS mysql.spider_link_mon_servers' failed: 2013: Lost connection to MySQL server during query   The result from queries just before the failure was: < snip > 8 g 2011-05-05 21:33:30 9 h 2011-05-05 22:32:10 DROP TABLE ta_l2;   deinit DROP DATABASE IF EXISTS auto_test_local; DROP DATABASE IF EXISTS auto_test_remote; DROP DATABASE IF EXISTS auto_test_remote2; DROP DATABASE IF EXISTS auto_test_remote3; DROP DATABASE IF EXISTS auto_test_local; DROP DATABASE IF EXISTS auto_test_local; DROP DATABASE IF EXISTS auto_test_local; for master_1 for child2 child2_1 child2_2 child2_3 for child3 child3_1 child3_2   More results from queries before failure can be found in /mnt/buildbot/build/mariadb-10.1.27/mysql-test/var/2/log/ha_part.log     Server [mysqld.3.2 - pid: 2149, winpid: 2149, exit: 256] failed during test run Server log from this test: ----------SERVER LOG START----------- 170814 17:48:50 [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 https://mariadb.com/kb/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.27-MariaDB 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 = 62909 K bytes of memory Hope that's ok; if not, decrease some variables in the equation.   Thread pointer: 0x7f80ffb0e008 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-------------  

Jacob Mathew (Inactive) added a comment - 2018-04-02 23:49 Kentoku, please review my fix for this problem in commit 986b651 on my branch .

Kentoku Shiba (Inactive) added a comment - 2018-04-03 17:48 Hi Jacob, I think this changes makes it impossible to uninstall plugin if plugin->ref_count is not 0 at do_uninstall(). Would you please check it?

Jacob Mathew (Inactive) added a comment - 2018-04-03 18:18 Kentoku, these changes are designed to ensure that Spider's plugin->ref_count is correct. They do not change the do_uninstall() function, which will issue the following warning if plugin->ref_count is not 0: Plugin is busy and will be uninstalled on shutdown

Jacob Mathew (Inactive) added a comment - 2018-04-04 19:16 Fix is pushed to 10.3.