Re: Re[2]: Thread freezes on SLAVE START/STOP

[Guilhem Bichot]

This is the most worrying (the first line) (more than the hang), it looks like the
slave only has the first characters of a longer query (see how SET has become S).
Then it is normal that the slave stops (as it is a bad query).

030130  5:15:48  Slave: error 'unexpected success or fatal error' on query 'UPDATE
hits_albums S', error_code=0
030130  5:15:48  Error running query, slave SQL thread aborted. Fix the problem, and
restart the slave SQL thread with "SLAVE START". We stopped at log 'binlog.007' position
303184804

The fact that the slave now fails immediately at startup is normal ;
you don't start the slave with --skip-slave-start so the slave automatically
does START SLAVE, and always hits this bad query.
For the moment, save your maybe strange master's binlog somewhere, then restart
replication
from scratch : take a snapshot of your master, do RESET MASTER on the master,
start the slave with --skip-slave-start, do RESET SLAVE and START SLAVE on it, and see
if the problem still happens later.
(see manual for details before doing this !!!!).

Before this, to give me a bit of info, could you do
mysqlbinlog position -j303184804 binlog.007 | head 
on your MASTER
and send me the output please ?

-- 
MySQL 2003 Users Conference -> http://www.mysql.com/events/uc2003/
For technical support contracts, visit https://order.mysql.com/?ref=mgbi
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Mr. Guilhem Bichot <guilhem@stripped>
 / /|_/ / // /\ \/ /_/ / /__   MySQL AB, Full-Time Software Developer
/_/  /_/\_, /___/\___\_\___/   Bordeaux, France
       <___/   www.mysql.com