Bug #47670 MySQL Crash with signal 6

• Submitted: 28 Sep 2009 9:22
• Modified: 3 Mar 2010 8:41
• Reporter: kris dba
• Status: No Feedback
• Category: MySQL Server
• Severity: S1 (Critical)
• Version: 5.0.51a
• OS: Linux
• CPU Architecture: Any
• Tags: cluster sql node, MySql Crash

[28 Sep 2009 9:22] kris dba

Description:
MySQL Instance is getting crashed with signal 6 and the crash recovery report does not provide back trace information.

How to repeat:
NA...gets crashed for every 3-4 days..

[28 Sep 2009 9:39] Sveta Smirnova

Thank you for the report.

But version 5.0.51a is old and many bugs were fiexed since. Please try with current verison 5.0.86 and if problem still exists provide output of SHOW CREATE TABLE usr_time_info

[2 Oct 2009 6:09] Sveta Smirnova

Thank you for the feedback.

It is hard to say what exactly leads to crash having information provided. But yes, this can be MySQL bug. This is why I ask you to try with current version and help us to create repeatable test case.

[2 Oct 2009 6:11] Sveta Smirnova

> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 21193712 K

Also this can be just out of memory error. Please check if you have 20G RAM which mysqld can use.

[11 Oct 2009 9:40] Sveta Smirnova

Thank you for the report.

fomit-frame-pointer is compiling option, should be not related if you use packages which we provide.

So, please, upgrade, set buffers to values reasonable for server having 8G RAM and if problem still repeatable with current version 5.0.86 provide output of SHOW CREATE TABLE usr_time_info

[14 Oct 2009 2:09] MySQL Verification Team

was that table a cluster table?  The abort() was called from NdbReceiver::execTRANSID_AI function... after printing this message:

ndbout_c("%p: ok: %d tAttrId: %d currRecAttr: %p", 
	       this,ok, tAttrId, currRecAttr);

[12 Nov 2009 0: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".

[21 Dec 2009 6:42] Sveta Smirnova

Thank you for the feedback.

Please provide output of SHOW CREATE TABLE usr_time_info

[3 Feb 2010 8:41] Sveta Smirnova

Thank you for the feedback.

Please upgrade to current version 5.0.90, try with it and if problem still exists send us new error log: it should contain more information.

[4 Mar 2010 0: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".