MySQL Bugs: #6300: Event not written to bin-log, but is found in log-file

Bug #6300	Event not written to bin-log, but is found in log-file
Submitted:	28 Oct 2004 10:24	Modified:	28 Nov 2004 13:07
Reporter:	René Thorsted	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	MySQL-Max 4.0.21	OS:	Linux (RedHar 9.0 kernel 2.4.20)
Assigned to:		CPU Architecture:	Any

Description:
A few events (2 to 5 actions per day), like UPDATE <some table> SET <something> WHERE <something>, is lost in the bin-log, but is still found in the text-log, this is a problem when the action isn't copied to the replication servers!

How to repeat:
I haven't found any spc. event to repeat this, but it happens on and off!!!

Hi,

What bin-log option do you use? Please, provide also full update statement.

There is no spc. update statement that doesn't work, 1 statement can go ok 10 times and get written in the bin-log (which ist startet with the --log-bin directly) the 11'th time it is executed and put into the text-log (started with --log) but is not found in the bin-log, the again it works nice for the next 10-20 times.
I don't think it has anything to do with the update statement, the bin-log is simply left out of the loop sometimes, it also happens with inserts, but I haven't testet how often!!!

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