Description:
mysqld has crashed and the error log suggests that it might be a bug:
090714 22:32:00 - mysqld got exception 0xc0000005 ;
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.
This MySQL server is a slave. Nothing was running against this server at the time of the crash. All it did was replicating.
The exacts same binaries are deployed on several other servers with the exact same OS / hardware specs.
Here is the full error log leading to the crash:
090714 17:38:15 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)
090714 17:38:15 [Note] Slave I/O thread killed while reading event
090714 17:38:15 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000012', position 7053
090714 17:38:15 [Note] Error reading relay log event: slave SQL thread was killed
090714 17:38:15 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000012' at position 7053, relay log '.\SERVER8488-relay-bin.000429' position: 7198
090714 17:38:15 [Note] Slave I/O thread: connected to master 'rep@10.200.110.137:3310',replication started in log 'mysql-bin.000012' at position 7053
090714 22:32:00 - mysqld got exception 0xc0000005 ;
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=25165824
read_buffer_size=65536
max_used_connections=2
max_threads=700
threads_connected=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 221221 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd: 0x482a060
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...
0000000000000000
0000000140070E91 mysqld.exe!Arg_comparator::can_compare_as_dates()[item_cmpfunc.cc:760]
0000000140074E05 mysqld.exe!Arg_comparator::set_cmp_func()[item_cmpfunc.cc:853]
0000000140077CFA mysqld.exe!Item_bool_func2::set_cmp_func()[item_cmpfunc.h:337]
0000000140078121 mysqld.exe!Item_bool_func2::fix_length_and_dec()[item_cmpfunc.cc:525]
000000014009DC69 mysqld.exe!Item_func::fix_fields()[item_func.cc:199]
0000000140076532 mysqld.exe!Item_cond::fix_fields()[item_cmpfunc.cc:3903]
0000000140163CA5 mysqld.exe!setup_conds()[sql_base.cc:7923]
0000000140210A94 mysqld.exe!mysql_prepare_update()[sql_update.cc:893]
0000000140210FE6 mysqld.exe!mysql_update()[sql_update.cc:247]
000000014019EC16 mysqld.exe!mysql_execute_command()[sql_parse.cc:2959]
00000001401A2F06 mysqld.exe!mysql_parse()[sql_parse.cc:5791]
00000001400E9C4D mysqld.exe!Query_log_event::do_apply_event()[log_event.cc:3012]
000000014012D7CB mysqld.exe!apply_event_and_update_pos()[slave.cc:1941]
000000014012F900 mysqld.exe!exec_relay_log_event()[slave.cc:2065]
000000014013459B mysqld.exe!handle_slave_sql()[slave.cc:2717]
00000001402B82C5 mysqld.exe!pthread_start()[my_winthread.c:85]
00000001403CAC37 mysqld.exe!_callthreadstart()[thread.c:295]
00000001403CAD05 mysqld.exe!_threadstart()[thread.c:275]
000000007725466D kernel32.dll!BaseThreadInitThunk()
0000000077458791 ntdll.dll!RtlUserThreadStart()
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at **QUERY**
thd->thread_id=495
thd->killed=NOT_KILLED
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
How to repeat:
I'm not sure how to repeat. This just happened while replicating.
