MySQL Bugs: #73731: Mysql bin log issue

Bug #73731	Mysql bin log issue
Submitted:	26 Aug 2014 20:29	Modified:	10 Mar 2015 11:35
Reporter:	Sarbamangal Choudhury	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.6.20	OS:	Linux
Assigned to:		CPU Architecture:	Any

Description:
We are getting this error once in every week.

Got fatal error 1236 from master when reading data from binary log: 'binlog truncated in the middle of event; consider out of disk space on master; the first event '' at 4, the last event read from '/data/log/mysql-bin-db03.000558' at 11939833, the last byte read from '/data/log/mysql-bin-db03.000558' at 11939852.'

Bin log is corrupted. Last time I restore the database from Master.

[root@db03 log]# mysqlbinlog mysql-bin-db03.000558>sarba_558.txt
ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 1229217363, event_type: 50
ERROR: Could not read entry at offset 11985390: Error in log format or read error.
[root@db03 log]# mysqlbinlog mysql-bin-db03.000559>sarba_558.txt
ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 840979534, event_type: 73
ERROR: Could not read entry at offset 31580042: Error in log format or read error.

How to repeat:
It is repeating every week. 

Suggested fix:
I like to know.

Please try version 5.6.23 (similar to bug http://bugs.mysql.com/bug.php?id=71400). Thanks.

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