I may found a solution to my problem >Today my slave aborted replication with error (this is the third time in 2 days)
Note that it worked for couple of months without a glitch >It has aborted since the sql query had an error ? >1. i think that if the query would have an error it should not go to the bin-log on the master and then executed by slaves right? >2. I belive that the query was OK and it was executed on master but somehow got corrupted and that`s why the slave failed. >What could contribute to this behavior ? I came up with this: Master stoped making bin-log since the disk went over the 95% [ it was 96% ] but continued to work ( since people were entering their stuff in ) slave got the "corrupt" log and exited. On the master the last query that was in the bin-log was the corrupted one. This happened to me a day before too but when i cleaned some space up (deleting old bin-logs), reseting slave,master it worked until this morning. I hope i`m right since i don`t see what else could cause this. My disk usage is now 48% on the partition where i keep mysql data so if it happens again soon i`m very wrong with this hypothesis --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
