I'll have to look into that. We have a single cronjob that just does a mysqldump daily
but not during the time of the log file generation, but that's all I can think of off the
top of my head.
From: tlyons@stripped [tlyons@stripped] On Behalf Of Todd Lyons
Sent: Thursday, July 16, 2009 2:41 PM
To: Gary Smith
Subject: Re: Slave log files going nuts...
On Thu, Jul 16, 2009 at 1:18 PM, Gary Smith<Gary@stripped> wrote:
> I have a new slave I setup against a new master server. The master server has 4 log
> files in it, the most current being updated on the 16th. The slave server on the other
> hand has several files, many which seem to be blank. This slave is set to slave the
> master and act as a master for downstream slaves. Note, there is no master/master on this
> configuration, even though the master itself could do it.
> Any ideas?
Something is doing several 'mysqladmin refresh' or a related command,
all sequentially in a row in short order. Look at your cron jobs that
start or end around the time that all those "empty" binlogs are being
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=1