Bug #68090 mysqld got signal 11
Submitted: 15 Jan 2013 19:25 Modified: 15 Jan 2013 23:11
Reporter: Rhys Campbell Email Updates:
Status: Unsupported Impact on me:
Category:MySQL Server Severity:S2 (Serious)
Version:5.4.2-beta OS:Linux (openSUSE 11.2 (x86_64))
Assigned to: CPU Architecture:Any

[15 Jan 2013 19:25] Rhys Campbell

Can anyone shed any further light on this? This is running on a server with another instance of mysqld. I've previous run this same version, with the same number of instances, with no issues before. There's should be plenty of available memory for mysql so I'm unsure where to go from here...

130115 17:42:50 [ERROR] /usr/local/mysql/bin/mysqld: Out of memory (Needed 8160 bytes)
130115 17:42:50 [ERROR] Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space
130115 17:42:50 - 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.

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 10245089 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd: 0x1044a00
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 = 0x7f04d334a0d0 thread_stack 0x40000
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xe16e40 = CALL update_parameter(6854645,"Team",NULL,1346,"Attack",0.57706075386724875)
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.
130115 17:42:50 mysqld_safe Number of processes running now: 0
130115 17:42:50 mysqld_safe mysqld restarted
130115 17:42:51 [Note] Plugin 'FEDERATED' is disabled.
130115 17:42:51 [Note] Plugin 'InnoDB' is disabled.
130115 17:42:52 [Note] Event Scheduler: Loaded 0 events
130115 17:44:52 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.4.2-beta'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Server (GPL)

Output from resolve_stack_dump...

0x89f80e my_print_stacktrace + 46
0x5c4422 handle_segfault + 802
0x7f06f7d95c00 _end + -150289192
0x626964 _ZN13st_join_table7cleanupEv + 4
0x626b0f _ZN4JOIN7cleanupEb + 191
0x626f59 _ZN4JOIN7destroyEv + 169
0x704ef8 _ZN18st_select_lex_unit7cleanupEv + 168
0x704fb8 _ZN18st_select_lex_unit7cleanupEv + 360
0x71e010 _ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr + 240
0x71c49c _ZN7sp_head7executeEP3THD + 1404
0x71cb2b _ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE + 1227
0x5d7383 _Z21mysql_execute_commandP3THD + 11395
0x5da287 _Z11mysql_parseP3THDPKcjPS2_ + 855
0x5db123 _Z16dispatch_command19enum_server_commandP3THDPcj + 3731
0x5db9e6 _Z10do_commandP3THD + 230
0x5ce326 handle_one_connection + 582
0x7f06f7d8d65d _end + -150323403
0x7f06f725114d _end + -162104795



How to repeat:
Currently unsure. Seems to happen randomly.
[15 Jan 2013 23:11] Shane Bester
Please, use a modern version of mysql.  5.6.9, 5.5.29 are available from dev.mysql.com today :)