Bug #6128 mysqld restarts every 1 minute
Submitted: 16 Oct 2004 13:43 Modified: 18 Oct 2004 11:56
Reporter: Vitaly Lopatin Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:4.0.20 OS:Linux (Linux)
Assigned to: CPU Architecture:Any

[16 Oct 2004 13:43] Vitaly Lopatin
Description:
I'd just start newlly installed Fedora Core 2 system.

------8< Cut here 8<----------
Number of processes running now: 0
041016 06:18:49  mysqld restarted
041016  6:18:49  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=67108864
read_buffer_size=1044480
max_used_connections=0
max_connections=2500
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 272604 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
&#9500;erribly 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.
-----------8< cut here 8<------------------

This add to error log every 1 minute.
I'd traced stack and I've got:

-----------8< cut here 8<------------------
root@d4 [/var/lib/mysql]# resolve_stack_dump -s mysqld.sym -n mysql.stack
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
-----------8< cut here 8<------------------

root@d4 [/var/lib/mysql]# cat /etc/my.cnf
[mysqld]
skip-external-locking
open-files-limit=8192
max_connections=2500
max_delayed_threads=100
key_buffer=64M
sort_buffer=4M
table_cache=256
record_buffer=1M
thread_stack=98304

This error repeats with kernels
2.6.8.1-smp
2.4.22nptl-smp
2.4.20-smp

How to repeat:
Just do it

Suggested fix:
On FC1 and RH7.3 all my MySQL 4.0.20 works fine.
Maybe bug in libpthread?
[16 Oct 2004 17:28] MySQL Verification Team
It is hard to tell based on the output what went wrong.

Please try two things:

* Try using our binary
* Try setting thread_stack at 128K
[17 Oct 2004 9:07] Vitaly Lopatin
> Try using our binary 
Thanx. That works fine. 
 
> Try setting thread_stack at 128K 
No effect.
[18 Oct 2004 11:56] MySQL Verification Team
So, what you have here is some grave problem in building a binary.

Use our, and you will have no problems.