Description:
master version is 4.1.12.
i don't use innodb tables (also innodb is active). only myisam.
i upgraded slave from 5.0.4-beta to 5.0.6-beta and when i start mysql replication seems to crash:
------------------------------------------------------------------------------------------
050601 09:44:05 mysqld started
050601 9:44:05 [Warning] Changed limits: max_open_files: 1024 max_connections: 100 table_cache: 457
050601 9:44:05 InnoDB: Started; log sequence number 0 43656
050601 9:44:05 InnoDB: Starting recovery for XA transactions...
050601 9:44:05 InnoDB: 0 transactions in prepared state after recovery
050601 9:44:07 [Note] /usr/local/mysql5-DE/libexec/mysqld: ready for connections.
Version: '5.0.6-beta-log' socket: '/tmp/mysql5-DE.sock' port: 3301 Source distribution
050601 9:44:07 [Note] Slave SQL thread initialized, starting replication in log 'lin0101004-bin.000200' at position 6338378, relay log './db-relay-bin.000126' position: 6356594
050601 9:44:07 [Note] Slave I/O thread: connected to master '..........:3306', replication started in log 'lin0101004-bin.000200' at position 6338378
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=268435456
read_buffer_size=1044480
max_used_connections=0
max_connections=100
threads_connected=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 466543 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
thd=0x89d7b38
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=0x59283594, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
0x816e526
0xffffe420
(nil)
0x81f7c6b
0x81f827a
0x827312e
0x40176aa7
0x4036dc2e
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
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x89da557 = INSERT INTO `liquid`.`debug_2005w22` (`date`, `type`, `ok`, `wmid`, `absid`, `uid`, `page`, `code`, `message`, `timer`) VALUES (20050601093032, 'tx2Chk', '
1', '0', '0', '37343817', '0', 'FRE:demo:37343817', 'un=demo pw=demo uip=81.219.130.1 lang=en ecode=304940577 f/e=0/0 wmid= agent=\"\" test=0 lgdPV2= vrs=2.011.000/2011000 agid=0 ga
me=Luder ctid=0 dm=1 dmGM=0 dlid= exc= atID=0 atA= hid= rtp= cid=0 fid= aO=|| ei=| org=| D|GAMA(1)mysqlC(1)plgGFV(1)plgGOV(1)gQ(rsaD(rsaGK(1)1)1)plgGEUs(1)DP(PCE(01)w0)r
saE(rsaGK(1)1)|', 30)
thd->thread_id=2
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 output:
0x816e526 handle_segfault + 566
0xffffe420 _end + -139528496
(nil)
0x81f7c6b _ZN15Query_log_event10exec_eventEP17st_relay_log_infoPKcj + 811
0x81f827a _ZN15Query_log_event10exec_eventEP17st_relay_log_info + 26
0x827312e handle_slave_sql + 1230
0x40176aa7 _end + 935755095
0x4036dc2e _end + 937815774
How to repeat:
i don't know. nothing special... compiled mysql 5.0.6-beta, start it, crash.
i tried mysql 5.0.4 again -> works perfect.
back to mysql 5.0.6 -> crash
