binary logs on slave won't grow (1 reply)

Hello All,

Having an odd issue on 5.0.81, running on W2K8, setup as a slave to a single master. I want to hang a slave off this slave, so I added binlogs to the config to get started. The first log and index are created upon restart of the service. However, no events are logged to the file, except the log file header and the log start event. If I read the binary log while the service is up, it shows:

/*!40019 SET @@session.max_insert_delayed_threads=0*/;
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
DELIMITER /*!*/;
# at 4
#110629 13:39:32 server id 1005 end_log_pos 98 Start: binlog v 4, server v 5.0.81-community-nt-log created 110629 13
# Warning: this binlog was not closed properly. Most probably mysqld crashed writing it.
ROLLBACK/*!*/;
DELIMITER ;
# End of log file
ROLLBACK /* added by mysqlbinlog */;
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;



However, it will eventually remove the warning and write a log stop event like normal, and start a new file. But the only events are the start and stop events, leaving the file at 117 bytes. Over the past few days, I've gotten up to binlog 5 and each of the logfiles is like this, with just the start and stop events.

The excerpt above was obtained directly after starting the service after adding logging to the config file. The service did not crash or throw errors.

The .err file is not showing any errors.

Replication is doing fine, with the master bin read advancing and the relay exec advancing. I can see the results of the relay exec in my tables. In addition to the activity generated via the rep, I also have triggers writing to a separate db that are constantly writing to tables and that data is showing up fine. Everything is looking great on this server but the binlog creation.

log-slave-updates has been enabled in the config.

Any help would be much appreciated.

-Jason