Description:
Production MySQL server has unexpectedly shut down twice in the last month, stack trace from the error log is about the same but can't figure out what caused the crash :-/ We are working on upgrading to MySQL5 but due to our environment that is not a simple overnight task.
Like I said I have looked throguh the stack traces, I have also searched for known bugs, and talked with some other folks I know who use MySQL and have had no luck locating the problem / bug.
Here are the 2 relevent error log sections
----------------------
----------------------
key_buffer_size=104857600
read_buffer_size=10481664
max_used_connections=995
max_connections=1000
threads_connected=9
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 2818136 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0xa2547d0
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=0xbfb1eeb8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x808f307
0x82eb5f8
0x63a78f9c
0x807e4cd
0x807b4bd
0x806c8cf
0x80bcd26
0x80dbfdb
0x80a11cb
0x80a427f
0x80e5323
0x812cae9
0x812d86d
0x82e8dac
0x831273a
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 0x7691d19d is invalid pointer
thd->thread_id=55747834
----------------------
----------------------
key_buffer_size=104857600
read_buffer_size=10481664
max_used_connections=502
max_connections=1000
threads_connected=19
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2818136 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x9bc3bb8
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=0xbfe7eeb8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x808f307
0x82eb5f8
0x80f34e9
0x807e4cd
0x807b4bd
0x806c8cf
0x80bcd26
0x80dbfdb
0x80a11cb
0x80a427f
0x80e5323
0x812cae9
0x812d86d
0x82e8dac
0x831273a
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html an
How to repeat:
Not sure how to repeat
