Bug #6655 simple query killed mysql - when rebooted, it executed fine though...
Submitted: 16 Nov 2004 5:02 Modified: 16 Dec 2004 15:00
Reporter: matt bodley Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:12.22 distrib 4.0.21 OS:Linux (linux, debian 3.0)
Assigned to: CPU Architecture:Any

[16 Nov 2004 5:02] matt bodley
Description:
Things were running smoothly on my website...

But randomly, the server killed itself on a simple query:

thd->query at 0x84f3ee8 = INSERT INTO finder_msg_type SET msg_id = '22580', type_id = '46'
thd->thread_id=473

Basically, I was writing a message (classified site) then clicked add, and it died trying to enter it into the table. All I did was a "refresh" and (mysqld_safe had restarted the server automatically) and it worked!!!

How to repeat:
Not sure...

I was running on another hosting provider and it kept going down consistently... I had to move to this new one which is dedicated and it looks like it is going to start up again!

I think it could be a serious issue depending on the problem, because I use pretty simple queries and don't use any special memory manipulation (I use PHP which handles everything)

Suggested fix:
I wish I knew, but heres the stack trace anyway... If anyone knows how to fix it or if they want to know more about the website etc then feel free to email me...

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=16777216
read_buffer_size=131072
max_used_connections=16
max_connections=100
threads_connected=16
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 233983 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

thd=0x84b4c60
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=0xbedfed98, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x810f1eb
0x40174825
0x81a3576
0x81a3b88
0x81a3ae8
0x81a3a5b
0x81a2a23
0x814ce48
0x811d78f
0x8121428
0x811b967
0x811b472
0x811ad38
0x4016ee51
0x4030865a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/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 0x84f3ee8 = INSERT INTO finder_msg_type SET msg_id = '22580', type_id = '46'
thd->thread_id=473
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.
[16 Nov 2004 12:51] Heikki Tuuri
Matt,

please resolve the stack dump as explained in the manual.

Please post

SHOW CREATE TABLE ...

for that table.

Regards,

Heikki
[14 Feb 2005 22:54] 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".