Bug #34323 mysqld got signal 11 in delete query
Submitted: 5 Feb 2008 18:48 Modified: 20 Aug 2009 9:19
Reporter: Dmitry Labutin Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: General Severity:S1 (Critical)
Version:5.0.45, 5.0.51a OS:Linux (Fedora 8)
Assigned to: Assigned Account CPU Architecture:Any
Tags: delete, innodb, Signal 11, UPDATE

[5 Feb 2008 18:48] Dmitry Labutin
Description:
Sometimes mysql fail on update and delete queries.
For example:
080205  8:01:45 - 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=10485760
read_buffer_size=131072
max_used_connections=41
max_connections=40
threads_connected=1
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 97279 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0xc15fe30
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...
Cannot determine thread, fp=0x67d8bcb8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x8188be3
0x827dfea
0x827e09a
0x827e266
0x827e38d
0x8203ee7
0x81a069a
0x81a3fe0
0x81a45c3
0x81a5a17
0x81a65e7
0x5c850b
0x4b8b2e
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do 
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0xbfc0720 = DELETE FROM vsm_sklad WHERE f_provider_id='16'
thd->thread_id=33342
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.

Number of processes running now: 0
080205 08:01:45  mysqld restarted

How to repeat:
CREATE TABLE vsm_sklad (
  f_id int(10) unsigned NOT NULL auto_increment,
  f_maker varchar(30) NOT NULL default '',
  f_number varchar(30) NOT NULL default '',
  f_description varchar(255) default NULL,
  f_quantity varchar(30) NOT NULL default '',
  f_price_opt double NOT NULL default '0',
  f_price_opt2 double NOT NULL default '0',
  f_price_rozn double NOT NULL default '0',
  f_days varchar(10) default '',
  f_price_group_id int(10) unsigned NOT NULL default '0',
  f_provider_id int(11) NOT NULL default '0',
  f_store_id bigint(20) NOT NULL default '-1',
  PRIMARY KEY  (f_id),
  KEY f_number (f_number),
  KEY f_provider_id (f_provider_id),
  KEY f_store_id (f_store_id),
  KEY f_maker (f_maker)
) ENGINE=InnoDB AUTO_INCREMENT=153344391 DEFAULT CHARSET=cp1251;

This table contain 25 192 703 rows.
[5 Feb 2008 18:49] Dmitry Labutin
mysql config

Attachment: my.cnf (application/octet-stream, text), 642 bytes.

[5 Feb 2008 18:51] Dmitry Labutin
symbol file for the mysqld server

Attachment: mysqld_sym.rar (application/octet-stream, text), 105.61 KiB.

[5 Feb 2008 18:54] Dmitry Labutin
Mysql log

Attachment: mysqld.log (text/plain), 26.55 KiB.

[5 Feb 2008 21:19] Sveta Smirnova
Stack trace:

0x8188be3 handle_segfault + 835
0x827dfea _ZN11Query_cache16invalidate_tableEP17Query_cache_block + 42
0x827e09a _ZN11Query_cache16invalidate_tableEP8st_table + 42
0x827e266 _ZN11Query_cache16invalidate_tableEP13st_table_list + 54
0x827e38d _ZN11Query_cache10invalidateEP3THDP13st_table_listc + 157
0x8203ee7 _Z12mysql_deleteP3THDP13st_table_listP4ItemP11st_sql_listmyb + 3143
0x81a069a _Z21mysql_execute_commandP3THD + 14650
0x81a3fe0 _Z11mysql_parseP3THDPKcjPS2_ + 368
0x81a45c3 _Z16dispatch_command19enum_server_commandP3THDPcj + 1251
0x81a5a17 _Z10do_commandP3THD + 167
0x81a65e7 handle_one_connection + 2695
0x5c850b (?)
0x4b8b2e (?)
[5 Feb 2008 21:40] Sveta Smirnova
Thank you for the report.

There were several bug reports relating to query cache and crashes which were fixed after version 5.0.45 has released. So described problem can be fixed already. Please upgrade to current version, try with it and inform us if problem is still repeatable.
[8 Feb 2008 8:07] Dmitry Labutin
Now, I have this problem:
http://bugs.mysql.com/bug.php?id=34404
[8 Feb 2008 8:27] Sveta Smirnova
Bug #34404 was marked as duplicate of this one.
[8 Feb 2008 8:44] Sveta Smirnova
Bug #34404 contains additional information about the case.
[8 Feb 2008 9:41] Dmitry Labutin
New fail trace:
0x818c030 handle_segfault + 768
0x8291912 _ZN11Query_cache19free_query_internalEP17Query_cache_block + 82
0x82955be _ZN11Query_cache16invalidate_tableEP10TABLE_LIST + 142
0x829571d _ZN11Query_cache10invalidateEP3THDP10TABLE_LISTc + 157
0x82144e0 _Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP11st_sql_listmyb + 2976
0x81a679f _Z21mysql_execute_commandP3THD + 13167
0x81ac5fc _Z11mysql_parseP3THDPKcjPS2_ + 604
0x81acbeb _Z16dispatch_command19enum_server_commandP3THDPcj + 1243
0x81ae297 _Z10do_commandP3THD + 167
0x81aedda handle_one_connection + 2554
0x5c850b (?)
0x4b8b2e (?)
[8 Feb 2008 9:45] Dmitry Labutin
mysql report before fail:

MySQL 5.0.51a-log        uptime 0 1:33:28       Fri Feb  8 12:04:01 2008

__ Key _________________________________________________________________
Buffer used     7.00k of  10.00M  %Used:   0.07
  Current       1.14M            %Usage:  11.38
Write hit     100.00%
Read hit       96.36%

__ Questions ___________________________________________________________
Total           1.11M   198.1/s
  QC Hits       1.01M   179.4/s  %Total:  90.53
  DMS          87.27k    15.6/s            7.85
  Com_         21.33k     3.8/s            1.92
  -Unknown      7.55k     1.3/s            0.68
  COM_QUIT      4.14k     0.7/s            0.37
Slow (10)           2     0.0/s  %Total:   0.00  %DMS:   0.00  Log: OFF
DMS            87.27k    15.6/s            7.85
  INSERT       45.12k     8.0/s            4.06         51.70
  SELECT       38.61k     6.9/s            3.48         44.25
  DELETE        2.52k     0.4/s            0.23          2.89
  UPDATE        1.01k     0.2/s            0.09          1.16
  REPLACE           0       0/s            0.00          0.00
Com_           21.33k     3.8/s            1.92
  change_db    11.63k     2.1/s            1.05
  admin_comma   7.55k     1.3/s            0.68
  lock_tables     806     0.1/s            0.07

__ SELECT and Sort _____________________________________________________
Scan            8.20k     1.5/s %SELECT:  21.23
Range           8.70k     1.6/s           22.52
Full join         105     0.0/s            0.27
Range check         0       0/s            0.00
Full rng join       0       0/s            0.00
Sort scan       1.22k     0.2/s
Sort range      2.90k     0.5/s
Sort mrg pass       0       0/s

__ Query Cache _________________________________________________________
Memory usage   45.99M of 100.00M  %Used:  45.99
Block Fragmnt   0.00%
Hits            1.01M   179.4/s
Inserts        26.48k     4.7/s
Insrt:Prune  26.48k:1     4.7/s
Hit:Insert    37.99:1

__ Table Locks _________________________________________________________
Waited              0       0/s  %Total:   0.00
Immediate     299.23k    53.4/s

__ Tables ______________________________________________________________
Open              256 of  256    %Cache: 100.00
Opened         89.56k    16.0/s

__ Connections _________________________________________________________
Max used            7 of   40      %Max:  17.50
Total           4.27k     0.8/s

__ Created Temp ________________________________________________________
Disk table        108     0.0/s
Table           5.50k     1.0/s    Size: 103.00
File                5     0.0/s

__ Threads _____________________________________________________________
Running             1 of    1
Cached              4 of    5      %Hit:  99.72
Created            12     0.0/s
Slow                0       0/s

__ Aborted _____________________________________________________________
Clients           256     0.0/s
Connects            0       0/s

__ Bytes _______________________________________________________________
Sent          488.59M   87.1k/s
Received      108.39M   19.3k/s

__ InnoDB Buffer Pool __________________________________________________
Usage         746.88M of   1.00G  %Used:  72.94
Read ratio      0.004
Pages
  Free         17.74k            %Total:  27.06
  Data         46.27k                     70.60 %Drty:   0.00
  Misc           1533                      2.34
  Latched           0                      0.00
Reads          10.45M    1.9k/s
  From file    41.98k     7.5/s            0.40
  Ahead Rnd         5     0.0/s
  Ahead Sql       101     0.0/s
Writes        973.68k   173.6/s
Flushes        21.69k     3.9/s
Wait Free           0       0/s

__ InnoDB Lock _________________________________________________________
Waits               0       0/s
Current             0
Time acquiring
  Total             0 ms
  Average           0 ms
  Max               0 ms

__ InnoDB Data, Pages, Rows ____________________________________________
Data
  Reads        42.84k     7.6/s
  Writes       67.22k    12.0/s
  fsync        50.14k     8.9/s
  Pending
    Reads           0
    Writes          0
    fsync           0

Pages
  Created         432     0.1/s
  Read         45.84k     8.2/s
  Written      21.69k     3.9/s

Rows
  Deleted      36.32k     6.5/s
  Inserted     44.99k     8.0/s
  Read          3.76M   670.0/s
  Updated       4.62k     0.8/s
[8 Feb 2008 9:53] Dmitry Labutin
I think Severity of this issue is Critical
[20 Jul 2009 9:19] Susanne Ebrecht
This seems to be fixed in MySQL 5.1.

Please try version MySQL 5.1 and let us know if issue still exist.
[20 Aug 2009 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".