Re: Replication crashes when max_bin_log_size is reached
We have still not solved this problem. I've thought I could get around it by doing "FLUSH LOGS" before the relay log reached the max_bin_log_size. But the same thing happened when I ran "FLUSH LOGS".
master.info was corrupted in the same way and the relay log did not rotate. So it seems that I have no other option than to install the latest 4.1 version and hope that it will work then. Unless someone know anything that could help me.
This time the error log looked like this:
050313 3:40:40 Slave I/O thread killed while reading event
050313 3:40:40 Slave I/O thread exiting, read up to log 'freebsds-bin.006', position 399146999
050313 3:40:40 Error reading relay log event: slave SQL thread was killed
050313 3:41:10 Could not use ensim-relay-bin for logging (error 13). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.
The rest is just like before.
Subject
Views
Written By
Posted
5987
February 19, 2005 08:33PM
Re: Replication crashes when max_bin_log_size is reached
3307
March 15, 2005 10:04AM
3673
April 20, 2005 06:29AM
3059
April 24, 2005 09:29PM
3116
April 30, 2005 02:52AM
3036
April 30, 2005 09:45AM
2951
May 01, 2005 02:29AM
2837
May 01, 2005 02:32AM
3020
May 06, 2005 01:59AM
2721
May 06, 2005 02:00AM
7810
May 11, 2005 08:12PM
3403
May 12, 2005 01:16PM
3149
May 16, 2005 04:32PM
2915
May 17, 2005 02:20AM
3096
May 17, 2005 06:53AM
2894
May 17, 2005 09:54AM
2988
May 17, 2005 06:23PM
3034
May 18, 2005 04:13AM
2982
May 18, 2005 08:02AM
5447
May 20, 2005 02:56PM
3834
May 23, 2005 03:30AM
2886
May 23, 2005 03:38AM
3001
May 31, 2005 08:52AM
3045
May 31, 2005 11:44AM
3119
May 02, 2005 07:31PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.