開(kāi)發(fā)告知mysq測(cè)試環(huán)境l宕機(jī)，查看錯(cuò)誤日志，發(fā)現(xiàn)如下錯(cuò)誤： 130605 16:43:28 - 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=402653184 read_buffer_size=2097152 max_used_connections=3001 max_threads=2000 threads_connected=1341 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 8615684 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x2aad61449720 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 = 0x5b323f20 thread_stack 0x40000 Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x1e06cf80 = SELECT COUNT(*) as total FROM (select count(*) as total from ad_log_cpt_show where ad_info_id=1907122 and show_time>=2013-03-18 and show_time<=2013-03-18? GROUP BY TO_DAYS(FROM_UNIXTIME(show_time, '%Y-%m-%d'))) tmp thd->thread_id=186915794 thd->killed=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. 130605 16:43:29 mysqld_safe mysqld from pid file /data/my2/mysql/db25522.pid ended 這個(gè)bug 應(yīng)該是在4.0或5.0的版本，而我的數(shù)據(jù)庫(kù)版本5.4,應(yīng)該不錯(cuò)出現(xiàn)上述bug mysql> select version(); +----------------------+ | version()??????????? | +----------------------+ | 5.4.1-beta-community | +----------------------+ 1 row in set (0.00 sec) 目前確認(rèn)是兩個(gè)方面： 一有可能參數(shù)設(shè)置問(wèn)題? 二 sql語(yǔ)句導(dǎo)致 SELECT COUNT(*) as total FROM (select count(*) as total from ad_log_cpt_show where ad_info_id=1907122 and show_time>=2013-03-18 and show_time<=2013-03-18? GROUP BY TO_DAYS(FROM_UNIXTIME(show_time, '%Y-%m-%d'))) tmp； 這個(gè)sql語(yǔ)句寫(xiě)的很不規(guī)范，看一下表結(jié)構(gòu)便知 show_time 字段類(lèi)型 mysql> desc ad_log_cpt_show; +--------------+--------------+------+-----+---------+-------+ | Field??????? | Type???????? | Null | Key | Default | Extra | +--------------+--------------+------+-----+---------+-------+ | ad_info_id?? | int(11)????? | NO?? | MUL | 0?????? |?????? | | show_time??? | int(11)????? | NO?? | MUL | 0?????? |?????? | | permanent_id | varchar(255) | NO?? |???? |???????? |?????? | +--------------+--------------+------+-----+---------+-------+ 這個(gè)問(wèn)題持續(xù)關(guān)注一段時(shí)間，看mysql是否還會(huì)自動(dòng)崩潰。 有類(lèi)似問(wèn)題的朋友，歡迎交流。 參考資料 http://bugs.mysql.com/bug.php?id=3003 http://dev.mysql.com/doc/mysql/en/crashing.html contains

總結(jié)

以上是生活随笔為你收集整理的mysql got signal 11_mysql bug ： mysqld got signal 11的全部?jī)?nèi)容，希望文章能夠幫你解決所遇到的問(wèn)題。

如果覺(jué)得生活随笔網(wǎng)站內(nèi)容還不錯(cuò)，歡迎將生活随笔推薦給好友。