[groonga-dev,00680] Re: show create table時にmysqld got signal 11で落ちる

Back to archive index

kentoku kento****@gmail*****
2012年 1月 27日 (金) 11:36:11 JST


斯波と申します。

mroongaをご利用頂きありがとうございます。

早速ではございますが、本現象の切り分けの為に
http://mroonga.github.com/ja/docs/install.html#centos-5
の手順でインストールした場合にも同じ現象となるかを
お試し頂けませんでしょうか?

また、MySQL、groonga、mroongaのソースコードのバージョン、
ビルドに利用したオプションを頂くことはできますしょうか?

どうぞ、よろしくお願いいたします。


2012年1月26日23:55 katsuya utada <utada****@gmail*****>:
> utadaと申します。
>
> mroonga 1.11でshow create tableコマンドをうつとgot signal 11でmysqldが落ちてしまいます。
>
> ・環境
> CentOS release 5.5
>
> ・全てソースからのビルド
>
> mysql> CREATE TABLE IF NOT EXISTS `e` (
>  `id` int(11) NOT NULL AUTO_INCREMENT,
>   `body` longtext,
>  PRIMARY KEY (`id`),
>  FULLTEXT KEY `title` (`body`)
>  ) ENGINE=groonga DEFAULT CHARSET=utf8;
>
> mysql> show create table e;
> ERROR 2013 (HY000): Lost connection to MySQL server during query
>
> 既知でしたらすいません。
> うっかりコマンド発行してサーバ落ると焦ってしまうので、ご報告させていただきました。
>
> ==> groonga.log <==
> 2012-01-26 23:41:16.426740|n|447b0940|DDL:table_create e
> 2012-01-26 23:41:16.431267|n|447b0940|DDL:column_create e id
> 2012-01-26 23:41:16.435533|n|447b0940|DDL:column_create e body
> 2012-01-26 23:41:16.442525|n|447b0940|DDL:table_create e_title
> 2012-01-26 23:41:16.446776|n|447b0940|DDL:column_create e_title index
> 2012-01-26 23:41:16.488479|n|447b0940|DDL:set_source e_title.index e.body
>
> 2012-01-26 23:41:35.142150|n|5fbb3350|mroonga 1.11 started.
> 2012-01-26 23:41:35.142217|n|5fbb3350|log level is 'NOTICE'
>
> ==> エラーログ <==
> 14:41:33 UTC - 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.
> 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.
>
> key_buffer_size=8388608
> read_buffer_size=131072
> max_used_connections=1
> max_threads=151
> thread_count=1
> connection_count=1
> It is possible that mysqld could use up to
> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads =
> 338486 K  bytes of memory
> Hope that's ok; if not, decrease some variables in the equation.
>
> Thread pointer: 0xab51b10
> 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 = 447b00f0 thread_stack 0x40000
> /usr/local/mysql_mroonga/bin/mysqld(my_print_stacktrace+0x2e)[0x766b3e]
> /usr/local/mysql_mroonga/bin/mysqld(handle_fatal_signal+0x386)[0x650cc6]
> /lib64/libpthread.so.0[0x3f6460eb10]
> /usr/local/mysql_mroonga/bin/mysqld(_Z17store_create_infoP3THDP10TABLE_LISTP6StringP24st_ha_create_informationb+0x114f)[0x59dacf]
> /usr/local/mysql_mroonga/bin/mysqld(_Z18mysqld_show_createP3THDP10TABLE_LIST+0x6d5)[0x59fa45]
> /usr/local/mysql_mroonga/bin/mysqld(_Z21mysql_execute_commandP3THD+0x349a)[0x55c1da]
> /usr/local/mysql_mroonga/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0xfe)[0x55ec0e]
> /usr/local/mysql_mroonga/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1356)[0x55ffc6]
> /usr/local/mysql_mroonga/bin/mysqld(_Z10do_commandP3THD+0xc2)[0x5602f2]
> /usr/local/mysql_mroonga/bin/mysqld(_Z24do_handle_one_connectionP3THD+0xf2)[0x5eb442]
> /usr/local/mysql_mroonga/bin/mysqld(handle_one_connection+0x4a)[0x5eb51a]
> /lib64/libpthread.so.0[0x3f6460673d]
> /lib64/libc.so.6(clone+0x6d)[0x3f63ad3d1d]
>
> Trying to get some variables.
> Some pointers may be invalid and cause the dump to abort.
> Query (abdced0): show create table e
> Connection ID (thread ID): 7
> Status: NOT_KILLED
>
> 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.
> 120126 23:41:33 mysqld_safe Number of processes running now: 0
> 120126 23:41:33 mysqld_safe mysqld restarted
> 120126 23:41:33 InnoDB: The InnoDB memory heap is disabled
> 120126 23:41:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins
> 120126 23:41:33 InnoDB: Compressed tables use zlib 1.2.3
> 120126 23:41:33 InnoDB: Initializing buffer pool, size = 128.0M
> 120126 23:41:34 InnoDB: Completed initialization of buffer pool
> 120126 23:41:34 InnoDB: highest supported file format is Barracuda.
> InnoDB: The log sequence number in ibdata files does not match
> InnoDB: the log sequence number in the ib_logfiles!
> 120126 23:41:34  InnoDB: Database was not shut down normally!
> InnoDB: Starting crash recovery.
> InnoDB: Reading tablespace information from the .ibd files...
> InnoDB: Restoring possible half-written data pages from the doublewrite
> InnoDB: buffer...
> 120126 23:41:34  InnoDB: Waiting for the background threads to start
>
> _______________________________________________
> groonga-dev mailing list
> groon****@lists*****
> http://lists.sourceforge.jp/mailman/listinfo/groonga-dev




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