MySQL Bugs: #24032: master server down when running replication

Bug #24032	master server down when running replication
Submitted:	7 Nov 2006 7:43	Modified:	26 Jan 2007 13:51
Reporter:	ILHA CHO	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	5.0.27	OS:	Linux (linux(CentOS_x86_64))
Assigned to:		CPU Architecture:	Any

Description:
err-log
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=2
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=(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=0x2af90afb5ad0, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x496d0a
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
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.
061107 16:12:44 mysqld ended

--------------------------------------------------------------------------------------------

env : CentOS4.4_x86_64 on IntelXeon

command
echo "0xd07d90" > mysqld.stack
nm -n /usr/local/mysql/libexec/mysqld > /tmp/mysqld.sym
resolve_stack_dump -s /tmp/mysqld.sym -n mysqld.stack

result :
0xd07d90 _end + 547264

This is meaning?

How to repeat:
.

Thank you for a problem report. Your resolved stack trace is surely meaningless. Please, send your my.cnf content and describe your hardware (how much RAM do you have), for the beginning. Can you identify exact statement that caused this crash?

my.cnf
# The MySQL server
[mysqld]
port        = 3306
socket      = /tmp/mysql.sock
#datadir     = /DB/mysql

skip-locking
#### 추가 요청 ### 
interactive_timeout=3600
query_cache_type=1
join_buffer_size = 64M
##################
key_buffer = 2048M
max_allowed_packet = 64M
table_cache = 1024
sort_buffer_size = 64M
read_buffer_size = 64M
read_rnd_buffer_size = 64M
myisam_sort_buffer_size = 64M
thread_cache_size = 40
query_cache_size = 64M
# Try number of CPU's*2 for thread_concurrency
thread_concurrency = 32
myisam_sort_buffer_size=32M
max_connections=300
max_connect_errors=9000
max_user_connections=400
wait_timeout=3600
long_query_time=3
default-character-set=euckr
init_connect='set names euckr'
#language        = /usr/local/mysql/share/mysql/korean
#log = /home/mysql/select.log
log-slow-queries
#skip-name-resolve
skip-innodb
skip-bdb
safe-show-database
skip-concurrent-insert
skip-new
old_passwords=1
#"load data local infile"을 사용하기위한옵션 켤때는 1로변경
local-infile=0

## replication master configration
server-id       = 1
set-variable    = max_binlog_size=100M
log-bin         = /MYSQLLOG/server-bin
binlog-do-db    = irani
#binlog-do-db    = job_db
#binlog-do-db    = job_db

H/W : DELL-AS-PE6850/800T
CPU : IntelXeonDualCorePro-7140M * 4
RAM : 32GB

Sorry for a delay with this bug report. 

Can you identify exact statement that caused this crash? Do you have corresponding binary log? And, most importantly, how much RAM do you have on this sysytem? Send the results of 

free

Linux command in case of any doubts.

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".