MySQL Bugs: #239: bin-log not working

Bug #239	bin-log not working
Submitted:	6 Apr 2003 22:15	Modified:	19 May 2005 14:24
Reporter:	Ryan R	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S2 (Serious)
Version:	4.0.12	OS:	Linux (linux glibc6)
Assigned to:	Guilhem Bichot	CPU Architecture:	Any

Description:
With bin-log on in my.cnf, server is not logging changes to a database. no databases are listed in binlog-skip-db. mysql and foo_live are listed in binlog-do-db. foo_live is the database that I am trying to replicate. updates to the database do not cause the position to change, nor is the update in the dbserver-bin.00x file. The log on the slave server indicates connection, and the server and client processes appear to be ok (same as on the replication implementation manual page). I have innodb tables off.

How to repeat:
anytime I try to update the master, the update is not logged nor replicated to the slave. Binary logging works when no slave is connected to the master.

Suggested fix:
Appears that replication is working, just not binary logging when a slave is trying to replicate.

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Hi,
Please test this :
* shutdown the master server and slave server
* start the master server with --log-bin and your binlog-do-db
* start the slave server with your options and --skip-slave-start
* do RESET MASTER and SHOW MASTER STATUS on the master
* do an INSERT query in foo_live on the master and see if it goes into the master's binlog
* do SHOW MASTER STATUS on the master.
* do RESET SLAVE and START SLAVE on the slave.
* check the slave's .err file to see if there is some error.
* do SHOW SLAVE STATUS on the slave.
* do SHOW MASTER STATUS on the master
* do an INSERT query in foo_live on the master and see if it goes into the master's binlog
* do SHOW MASTER STATUS on the master.
* do SHOW SLAVE STATUS on the slave.
Then you will see if having a slave connected changes something, or if it's unrelated to the slave.
If you still think there is a problem, read your .err files (master and slave). If you still find no clue, modify this bug report to add a copy-paste of the output of the above commands, plus your my.cnf and .err (master and slave).
Thanks.

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.

That corrected the problem. thank you.