I'm having a problem in that mySQL 4.0.20 keeps restarting every 17 seconds like clockwork. Within the 17 seconds I can run queries but if anything doesn't complete (such as a large file import), it errors out.
The problem is that I'm completely lost as to how to resolve this. I've included all of the inforamation I have even if I don't understand it. Obviously this is a general forum, if anyone has a better place for me to post my problem, please let me know.
The mysql error log shows the following for every time it restarts:
--------------------------------------------------------------------------------
Number of processes running now: 0
040816 00:35:25 mysqld restarted
040816 0:35:25 Warning: Asked for 196608 thread stack, but got 126976
040816 0:35:25 InnoDB: Started
/usr/sbin/mysqld: ready for connections.
Version: '4.0.20-standard' socket: '/var/lib/mysql/mysql.sock' port: 3306
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=0
max_connections=500
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 1096188 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=(nil)
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=0xbfeff6c8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x80720d4
0x8250d48
0x8272e9e
0x80f87c2
0x80f8ce0
0x824e4fc
0x828452a
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
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.
--------------------------------------------------------------------------------
As mentioned, I did a stack trace and got the following output:
--------------------------------------------------------------------------------
0x80720d4 handle_segfault + 420
0x8250d48 pthread_sighandler + 184
0x8272e9e ftell + 14
0x80f87c2 srv_printf_innodb_monitor + 818
0x80f8ce0 srv_lock_timeout_and_monitor_thread + 512
0x824e4fc pthread_start_thread + 220
0x828452a thread_start + 4