フジマルです。 今まで動いていたmysqlがldapをインストールし、authconfigでユーザー情報を” ldapを使用”、認証を”ldap認証を使用”に設定した後に、mysqlをstartさせると 下記のエラーを出すようになりました。 060424 00:06:15 mysqld started 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=8388600 read_buffer_size=131072 max_used_connections=0 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x83f4300 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... Bogus stack limit or frame pointer, fp=0xbfffa1d8, stack_bottom=0xa4a3a2a1, thread_stack=196608, aborting backtrace. Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x8f8e7e7d is invalid pointer thd->thread_id=0 The manual page at http://www.mysql.com/doc/en/Crashing.html contains information that should help you find out what is causing the crash. 060424 00:06:15 mysqld ended この現象はauthconfigでユーザー情報を”ldapを使用”、認証を”ldap認証を使用” をそれぞれはずしてからmysqlをstartし（この時点ではldapは走ったままで す）、その後authconfigの設定を元に戻すと（それぞれldap使用）問題はありま せん。mysql -u root -p などでmysqlモニターに入れます。 自身がauthconfigをよく理解していない事も理由ですが、解決方法が分かりませ ん。どうぞお知恵を貸してください。