MySQL Bugs: #25261: binlog truncated at replication

Bug #25261	binlog truncated at replication
Submitted:	23 Dec 2006 19:49	Modified:	25 Jan 2007 13:59
Reporter:	Ali Hamed	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S2 (Serious)
Version:	4.1.20-log	OS:	Linux (Linux CentOS 4.4)
Assigned to:		CPU Architecture:	Any
Tags:	Error reading packet from server

Description:
Hello;
I'm running Replication between one master and three slaves. problem occured every tow - three days.
when problem occured slave's error log said
=========
061221  0:53:38 [Note] Slave I/O thread: connected to master 'repl@server3.6rbtop.com:3306',  replication started in log 'server3-bin.000041' at position 89385628
061223 12:20:51 [ERROR] Error reading packet from server: binlog truncated in the middle of event (server_errno=1236)
061223 12:20:51 [ERROR] Got fatal error 1236: 'binlog truncated in the middle of event' from master when reading data from binary log
061223 12:20:51 [ERROR] Slave I/O thread exiting, read up to log 'server3-bin.000042', position 400821103
==========
Problem solving after restart mysql service at slave server.

How to repeat:
Don't know

Thank you for a problem report. Please, try to use newer version, 4.1.22, and inform about the results.

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