The binlogs are closed and reopened every time you do a FLUSH LOGS; command, or 
when the server restarts.  Is your server crashing continuously?  Take a look 
at your error log as well.

Regards,
Gavin Towey

-----Original Message-----
From: Gary Smith [mailto:g...@primeexalia.com]
Sent: Thursday, July 16, 2009 3:16 PM
To: Todd Lyons
Cc: mysql@lists.mysql.com
Subject: RE: Slave log files going nuts...

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.

Gary

________________________________________
From: tly...@sitehelp.org [tly...@sitehelp.org] On Behalf Of Todd Lyons 
[tly...@ivenue.com]
Sent: Thursday, July 16, 2009 2:41 PM
To: Gary Smith
Cc: mysql@lists.mysql.com
Subject: Re: Slave log files going nuts...

On Thu, Jul 16, 2009 at 1:18 PM, Gary Smith<g...@primeexalia.com> 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
created.

--
Regards...      Todd

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql?unsub=g...@primeexalia.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql?unsub=gto...@ffn.com


The information contained in this transmission may contain privileged and 
confidential information. It is intended only for the use of the person(s) 
named above. If you are not the intended recipient, you are hereby notified 
that any review, dissemination, distribution or duplication of this 
communication is strictly prohibited. If you are not the intended recipient, 
please contact the sender by reply email and destroy all copies of the original 
message.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/mysql?unsub=arch...@jab.org

Reply via email to