MySQL Bugs: #12152: Mysql Replication

Bug #12152	Mysql Replication
Submitted:	25 Jul 2005 14:05	Modified:	27 Jul 2005 8:04
Reporter:	[ name withheld ]	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	MySQL-4.0.20-0	OS:	Linux (Linux)
Assigned to:		CPU Architecture:	Any

Description:
I have configured replication between master & slave servers, which was working fine without any issues. Suddenly replication stopped and the log file thrown the following message in slave --

050715 14:37:52  Error reading packet from server: binlog truncated in the middle of event (server_errno=1236)
050715 14:37:52  Got fatal error 1236: 'binlog truncated in the middle of event' from master when reading data from binary log
050715 14:37:52  Slave I/O thread exiting, read up to log 'linux-bin.016', position 733802359

later I restarted slave service (mysql>slave start), but it couldn't update itself from where it has stopped replication  & I had to take a dump of master and restore in slave & configure replication again.

Could some one let me know what could be the problem?

How to repeat:
I couldn't repeat the issue

Hi!

Tried to reproduce but unsuccessfully. For now I set status "can't repeat". if you get any ideas how to reproduce it pls let us know (or just reopen this bug report)