| Bug #52920 | Mysqld got signal 11 | ||
|---|---|---|---|
| Submitted: | 17 Apr 2010 17:50 | Modified: | 24 May 2010 9:34 |
| Reporter: | Marek Zakrzewski | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Server | Severity: | S1 (Critical) |
| Version: | 5.1.45 | OS: | Linux (CentOS 5.4 64-bit) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | backtrace, bug, singal 11 | ||
[21 Apr 2010 6:19]
Sveta Smirnova
Thank you for the report. Does it always crash executing same query? Please send us output of SHOW CREATE TABLE baafec8f1f61096356b44ca244978830 and SHOW TABLE STATUS LIKE 'baafec8f1f61096356b44ca244978830' and your configuration file.
[21 Apr 2010 19:36]
Marek Zakrzewski
[mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock user=mysql # Default to using old password format for compatibility with mysql 3.x # clients (those using the mysqlclient10 compatibility package). old_passwords=1 skip-innodb query_cache_size = 16M join_buffer_size = 512K thread_cache_size = 4 table_cache = 128 key_buffer_size = 3G # Disabling symbolic-links is recommended to prevent assorted security risks; # to do so, uncomment this line: # symbolic-links=0 [mysqld_safe] log-error=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid Table Create Table baafec8f1f61096356b44ca244978830 CREATE TABLE `baafec8f1f61096356b44ca244978830` ( ... baafec8f1f61096356b44ca244978830 MyISAM 10 Dynamic 1714 525 900220 281474976710655 55296 0 1715 2010-03-08 14:39:58 2010-04-21 02:00:41 2010-04-21 11:29:19 utf8_polish_ci NULL
[24 Apr 2010 9:34]
Sveta Smirnova
Thank you for the feedback. But there is no output of SHOW CREATE TABLE baafec8f1f61096356b44ca24497883. Please send it.
[24 May 2010 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".

Description: 100417 19:42:39 - 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=1468006400 read_buffer_size=131072 max_used_connections=48 max_threads=200 threads_connected=16 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1870832 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd: 0x7fdf5ad24ab0 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 = 0x40072f00 thread_stack 0x40000 /usr/libexec/mysqld(my_print_stacktrace+0x24) [0x872354] /usr/libexec/mysqld(handle_segfault+0x346) [0x5c81e6] /lib64/libpthread.so.0 [0x394960e930] /lib64/libc.so.6(memcpy+0x11) [0x3948a7bdc1] /usr/libexec/mysqld(_mi_insert+0x97b) [0x83e4db] /usr/libexec/mysqld [0x83e86b] /usr/libexec/mysqld [0x83e818] /usr/libexec/mysqld(_mi_ck_real_write_btree+0x60) [0x83ea90] /usr/libexec/mysqld(_mi_ck_write_btree+0x72) [0x83eb52] /usr/libexec/mysqld(mi_write+0x33a) [0x83d3da] /usr/libexec/mysqld(handler::ha_write_row(unsigned char*)+0x5f) [0x6b1eef] /usr/libexec/mysqld(write_record(THD*, st_table*, st_copy_info*)+0x74) [0x64db84] /usr/libexec/mysqld(mysql_insert(THD*, TABLE_LIST*, List<Item>&, List<List<Item> >&, List<Item>&, List<Item>&, enum_duplicates, bool)+0xbc5) [0x651185] /usr/libexec/mysqld(mysql_execute_command(THD*)+0x2ef6) [0x5d8556] /usr/libexec/mysqld(mysql_parse(THD*, char const*, unsigned int, char const**)+0x211) [0x5db311] /usr/libexec/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x107f) [0x5dc3af] /usr/libexec/mysqld(do_command(THD*)+0xe6) [0x5dc996] /usr/libexec/mysqld(handle_one_connection+0x73d) [0x5cf37d] /lib64/libpthread.so.0 [0x3949606617] /lib64/libc.so.6(clone+0x6d) [0x3948ad3c2d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort... thd->query at 0x87442e0 = INSERT INTO `baafec8f1f61096356b44ca244978830` (title,tresc,link,data,czas,zdjecia) VALUES ('Trumny przed gĹĂłwnym oĹtarzem; "Polska zdaĹa egzamin"','- Kondukt z PaĹacu Prezydenckiego to ostatnia warszawska droga prezydenckiej pary - mĂłwiĹ w archikatedrze Ĺ. Jana metropolita warszawski, arcybiskup Kazimierz Nycz.','http://wiadomosci.onet.pl/2156953,11,1,1,item.html','Sat, 17 Apr 2010 16:40:00 GMT','1271522400','a:3:{i:0;s:19:"1271526159_2712.jpg";i:1;s:25:"1271526159_2712_small.jpg";i:2;s:10:"kresy24.pl";}') thd->thread_id=13129 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. 100417 19:42:39 mysqld ended How to repeat: MySQL crashed by itself ! CPU: Core i7 920 2.66 GHz RAM: 8 GB DDR3