[groonga-dev,03103] mariadbへmroongaプラグインインストール時にLost connection発生

Back to archive index

wakis****@gmail***** wakis****@gmail*****
2015年 2月 21日 (土) 16:09:59 JST


いつもお世話になっております。

わきすけです。


何度もすいません、、、


以前、mariadb 5.5.41ではmroongaが対応していないということで、

ダウングレードを行い次の環境を作りました。


[root @ wakisuke mysql]# yum list installed | grep "mariadb"
mariadb.x86_64                         1:5.5.40-2.el7_0                @updates
mariadb-devel.x86_64                   1:5.5.40-2.el7_0                @updates
mariadb-libs.x86_64                    1:5.5.40-2.el7_0                @updates
mariadb-mroonga.x86_64                 4.10-2.el7.centos               @groonga
mariadb-server.x86_64                  1:5.5.40-2.el7_0                @updates



しかし、mroongaのプラグインをインストールする際に次の通りになります。


[root @ wakisuke mysql]# mysql -u root -p < /usr/share/mroonga/install.sql
Enter password:
ERROR 2013 (HY000) at line 3: Lost connection to MySQL server during query



どうも、install pluginでこけてしまうみたいです。


MariaDB [(none)]> INSTALL PLUGIN mroonga SONAME 'ha_mroonga.so';
ERROR 2013 (HY000): Lost connection to MySQL server during query



Lost connection to MySQL server during queryの原因はmax_allowed_packetという情報があったので試してみましたが、なにも変わりませんでした。

mariadbのインストールバグかと思い、他のプラグインのインストールを試したところ、正常にインストールできることを確認しました。


Lost connection to MySQL server during query発生時のmariadb.logは次のとおりです。


150221 16:17:12 [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: 5.5.40-MariaDB
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=1
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 = 466712 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.


Thread pointer: 0x0x7f03f1fc0640
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...
stack_bottom = 0x7f03e862fdc0 thread_stack 0x48000
/usr/libexec/mysqld(my_print_stacktrace+0x3d)[0x7f03ef2f706d]
/usr/libexec/mysqld(handle_fatal_signal+0x515)[0x7f03eef0d9b5]
/lib64/libpthread.so.0(+0xf130)[0x7f03ee63f130]
/usr/libexec/mysqld(+0x37c3e4)[0x7f03eedeb3e4]
/usr/libexec/mysqld(+0x37c840)[0x7f03eedeb840]
/usr/libexec/mysqld(_Z20mysql_install_pluginP3THDPK19st_mysql_lex_stringS3_+0x314)[0x7f03eedef7e4]
/usr/libexec/mysqld(_Z21mysql_execute_commandP3THD+0x3cb3)[0x7f03eede2023]
/usr/libexec/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x125)[0x7f03eede5a05]
/usr/libexec/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1737)[0x7f03eede7a47]
/usr/libexec/mysqld(_Z24do_handle_one_connectionP3THD+0x1c2)[0x7f03eee985d2]
/usr/libexec/mysqld(handle_one_connection+0x4a)[0x7f03eee9867a]
/lib64/libpthread.so.0(+0x7df3)[0x7f03ee637df3]
/lib64/libc.so.6(clone+0x6d)[0x7f03eceb81ad]


Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f03b8004bf8): INSTALL PLUGIN Mroonga SONAME 'ha_mroonga.so'
Connection ID (thread ID): 1
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=off


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.
150221 16:17:13 mysqld_safe Number of processes running now: 0
150221 16:17:13 mysqld_safe mysqld restarted
150221 16:17:13 InnoDB: The InnoDB memory heap is disabled
150221 16:17:13 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150221 16:17:13 InnoDB: Compressed tables use zlib 1.2.7
150221 16:17:13 InnoDB: Using Linux native AIO
150221 16:17:13 InnoDB: Initializing buffer pool, size = 128.0M
150221 16:17:13 InnoDB: Completed initialization of buffer pool
150221 16:17:13 InnoDB: highest supported file format is Barracuda.
150221 16:17:13  InnoDB: Waiting for the background threads to start
150221 16:17:14 Percona XtraDB (http://www.percona.com) 5.5.40-MariaDB-36.1 started; log sequence number 1598476
150221 16:17:14 [Note] Plugin 'FEEDBACK' is disabled.
150221 16:17:14 [Note] Server socket created on IP: '0.0.0.0'.
150221 16:17:14 [Note] Event Scheduler: Loaded 0 events
150221 16:17:14 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.5.40-MariaDB'  socket: '/mysql/mysql.sock'  port: 3306  MariaDB Server


よろしくお願い致します。


--

わきすけ



groonga-dev メーリングリストの案内
Back to archive index