Bug #25018 Master server mysqld crash
Submitted: 12 Dec 2006 19:33 Modified: 26 Jan 2007 23:31
Reporter: Bill Nesbitt Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S1 (Critical)
Version:5.0.27 OS:Linux (RH EL4 x86_64)
Assigned to: CPU Architecture:Any

[12 Dec 2006 19:33] Bill Nesbitt
Description:
After a recent upgrade from 5.0.24a to 5.0.27, after a few days of running.  This seems very similar to Bug #24032.

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=536870912
read_buffer_size=131072
max_used_connections=301
max_connections=1000
threads_connected=160
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 2700280 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
thd=0x2adb6fc010
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=0x46bf4ff8, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x65725f747361
Stack trace seems successful - bottom reached
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 0x2ac3ef8ad0  is invalid pointer
thd->thread_id=2263516
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.
 
Number of processes running now: 0

# resolve_stack_dump -n /tmp/mysqld.stack -s /tmp/mysql.sym
0x65725f747361 _end + 1589335513

/etc/my.cnf:

[mysqld]
port=3306
datadir=/var/lib/mysql
tmpdir=/var/tmp
socket=/var/lib/mysql/mysql.sock
server-id=2
log-bin
read-only
report-host=maurice-local
log_slow_queries=/var/log/slow-queries.log
long_query_time=4
low-priority-updates
skip-name-resolve
 
max_connect_errors = 100000
max_allowed_packet = 2M
max_connections=1000
#sort_buffer_size = 1M
#read_buffer_size = 1M
#
#read_rnd_buffer_size = 1M
myisam_sort_buffer_size = 64M
thread_concurrency = 16
concurrent_insert = 2
thread_cache = 32
table_cache = 2048
query_cache_size= 128M
key_cache_division_limit = 50
key_buffer = 512M
 
#[mysql.server]
#user=mysql
#basedir=/var/lib
 
[safe_mysqld]
err-log=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
open-files-limit=4096

Hardware:
AMD Opteron(tm) Processor 870 (dual-core) x 4
32GB RAM

How to repeat:
Unknown, this is the first time it has happened.
[26 Dec 2006 23:31] Sveta Smirnova
Thank you for the report.

But we can not repeat it using infrmation you provided.

Please try to find query which causes crash. You can find it in the binary or in the general query log.
[27 Jan 2007 0:00] 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".