[i=s] 本帖最后由 sjg9999 于 2009-8-26 17:59 编辑 [/i]
show slave status;所报的错.
Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.
日志报的错
Slave I/O thread killed while reading event
090810 14:18:27 Slave I/O thread exiting, read up to log 'master-bin.196', posi
tion 149391244
090810 14:18:51 Slave SQL thread initialized, starting replication in log 'mast
er-bin.190' at position 320925716, relay log './back-8hy-relay-bin.001' position
: 422932341
090810 14:18:51 Slave I/O thread: connected to master 'hyrepl@192.168.1.1:33
06', replication started in log 'master-bin.196' at position 149391244
ERROR: 1064 You have an error in your SQL syntax. Check the manual that corres
ponds to your MySQL server version for the right syntax to use near '?' at line
1
090810 22:27:59 Error in Log_event::read_log_event(): 'Event too big', data_len
: 1679847284, event_type: 114
090810 22:27:59 Error reading relay log event: slave SQL thread aborted because
of I/O error
哪位兄弟帮忙看看.
错误可能出在哪里...
找了一天没找出问题
sjg9999 于 2009-08-26 17:59:18发表:
问题解决了..
用mysqlbinlog -j log_pos log_file | less
找到log_pos下一个log_pos
然后用change master to从下一个log_pos开始复制就OK了
sjg9999 于 2009-08-26 16:59:43发表:
Log_Pos请问这个值是不是连续的?
我用mysqlbinlog看日志不是连续的
sjg9999 于 2009-08-26 16:47:32发表:
set global sql_slave_skip_counter = 1;
跳过这个错误也不行