What setting(s) did you change to move to the separate partition?
SHOW VARIABLES LIKE '%bin%';
SHOW VARIABLES LIKE '%dir%';
(there may be other VARIABLES worth checking)
What steps did you take for the move? (Actually move bin.1? Start over? etc?)
Consider using expire_logs_days.
5.0 -- I don't think anything relevant has changed during 4.0 thru 5.6.
> -----Original Message-----
> From: Machiel Richards - Gmail [mailto:machiel.richards@stripped]
> Sent: Wednesday, July 03, 2013 3:20 AM
> To: mysql list
> Subject: Master not creating new binary log.
> Hi all
> I hope all are well.
> I would like some assistance with something really strange.
> We currently have a problem with a master slave setup running mysql
> This is one of our legacy servers which are in the planning to be
> upgraded, however in order for this to be done the replication needs to be
> up and running.
> The problem we have currently however is that the binary logs on
> the master was moved to a seperate partition due to disc space
> A new binlog file called mysql-bin.1 was created and everything
> seemed to work fine.
> However, the moment the file reached the file size of 100Mb, it
> does not go on to create a new binlog file called mysql-bin.2 and the
> replication fails stating that it is unable to read the binary log file.
> Thus far we have done a flush logs and reset master , but the
> same problem occurs, where it creates mysql-bin.1 and the moment it
> reaches it's max size and suppose to create a new file, it stops and does
> not create the new one.
> I really hope this makes sense, and that someone can perhaps
> point us in the correct direction.
> Any help would be appreciated.
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql