Bug #22244 MySQL Server 5.0.24a crashes constantly on an INSERT DELAYED
Submitted: 11 Sep 2006 18:50 Modified: 12 Sep 2006 13:57
Reporter: David Fix Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Server Severity:S1 (Critical)
Version:5.0.24a OS:Linux (Suse 10.1)
Assigned to: CPU Architecture:Any
Tags: crash, delayed insert

[11 Sep 2006 18:50] David Fix
MySQL 5.024a running on Suse 10.1 crashes.  I am using the standard statically linked version, downloaded from the mysql site.  (RPMs)

I am running a PHP-Nuke site...  Not that it matters, but...  :)

The last query in the query logs is this:
INSERT DELAYED INTO nuke_blocked_pagetracker (last_page ,page_date ,id_tracker) VALUES ('/modules.php?name=Forums', '1157999113', '84413')

I made sure that the table was not corrupt, etc, before filing this report, of course.  :)

Here's the error log:

Version: '5.0.24a-standard-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MySQL Community Edition - Standard (GPL)
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_connections = 225791 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

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=0xb50b02a8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
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 0x8ad1588 = INSERT DELAYED INTO nuke_blocked_pagetracker (last_page ,page_date ,id_tracker) VALUES ('modules.php', '1158000116', '84413')
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.

And here is a stack trace:
0x817ec70 handle_segfault + 416
0xffffe420 _end + -140413904
0x81bb415 _Z36fill_record_n_invoke_before_triggersP3THDR4ListI4ItemES4_bP19Table_triggers_list14trg_event_type + 53
0x81bb415 _Z36fill_record_n_invoke_before_triggersP3THDR4ListI4ItemES4_bP19Table_triggers_list14trg_event_type + 53
0x81de9dc _Z12mysql_insertP3THDP13st_table_listR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb + 1196
0x819698e _Z21mysql_execute_commandP3THD + 8382
0x819c1d0 _Z11mysql_parseP3THDPcj + 304
0x819319b _Z16dispatch_command19enum_server_commandP3THDPcj + 1147
0x8192ccd _Z10do_commandP3THD + 141
0x819223f handle_one_connection + 655
0xb7eff34b _end + -1349418149
0xb7e2565e _end + -1350310290

Unfortunately, that doesn't tell me much.  :(

If there's anything that you need, please let me know!  :)

Thanks in advance, guys!

How to repeat:
Um...  :)  Run the query:

INSERT DELAYED INTO nuke_blocked_pagetracker (last_page ,page_date ,id_tracker) VALUES ('/modules.php?name=Forums', '1157999113', '84413')

And it dies.  :)

Suggested fix:
No idea!
[12 Sep 2006 8:49] Valeriy Kravchuk
Thank you for a problem report. Please, send the results of:

SHOW TABLE STATUS LIKE 'nuke_blocked_pagetracker'\G
[12 Sep 2006 13:16] David Fix
Here you are:

mysql> SHOW TABLE STATUS LIKE 'nuke_blocked_pagetracker'\G
*************************** 1. row ***************************
           Name: nuke_blocked_pagetracker
         Engine: MyISAM
        Version: 9
     Row_format: Dynamic
           Rows: 382283
 Avg_row_length: 62
    Data_length: 24045160
Max_data_length: 4294967295
   Index_length: 6634496
      Data_free: 0
 Auto_increment: 966702
    Create_time: 2005-03-15 15:24:07
    Update_time: 2006-09-12 09:15:12
     Check_time: 2006-09-11 15:15:40
      Collation: latin1_swedish_ci
       Checksum: NULL
1 row in set (0.00 sec)
[12 Sep 2006 13:37] Valeriy Kravchuk
Then is is a duplicate of bug #16218, already fixed in 5.0.25.
[12 Sep 2006 13:57] David Fix
Ok perfect.  :)  Sorry to waste people's time!  I had searched, but didn't see that bug.  Any idea when 5.0.25 will be released?  :)