Re: Database recommendations?

Paul Butcher
Thu, 22 Feb 2007 23:15:06 -0000

Tom Mornini wrote:
> Are we talking crash as in "boom" or crash as in halted
replication?
>
> If "boom", process boom or OS boom?

We''re talking crash as in "boom" followed by mysqld
attempting to
restart, followed by "boom" followed by... (ad infinitum, until the
log
files grow to be very large indeed!).

Here is an example from error.log of one of the crashes:

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=8388600
read_buffer_size=131072
max_used_connections=3
max_connections=100
threads_connected=1
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.

thd=0x73300490
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=0xbe5fecd8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80b18df
0x831073a
0x80e666f
0x80eb5de
0x816f87c
0x8170b9f
0x8170b0d
0x810af48
0x80cc59e
0x80c9d27
0x80cab2c
0x8115889
0x816bb3f
0x8169e47
0x830c0ff
0x833bb0a
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 0x7338b92b  is invalid pointer
thd->thread_id=2
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.

--
Posted via http://www.ruby-forum.com/.