Re: Persistent annoying slave binlog corruption...

2003-07-02 Thread Egor Egorov
Michael Loftis [EMAIL PROTECTED] wrote:
 Recently, and pretty consistently our slave's relay logs have been getting 
 garbage that is not in the master.  The symptom is usually a truncated 
 query with a few characters of garbage.  The solution for now is to change 
 master to  to the errored master bin log and position and have it start 
 replication from the spot where it is.  When this happens the IO and SQL 
 thread are found choked, with no error on show slave status, but the MySQL 
 .err log shows the error.

What version of master and slave do you use? Which OS? Did you install MySQL server 
from binary or from source?



-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.net http://www.ensita.net/
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /Egor Egorov
 / /|_/ / // /\ \/ /_/ / /__   [EMAIL PROTECTED]
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.net
   ___/   www.mysql.com




-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Persistent annoying slave binlog corruption...

2003-06-28 Thread Michael Loftis
Recently, and pretty consistently our slave's relay logs have been getting 
garbage that is not in the master.  The symptom is usually a truncated 
query with a few characters of garbage.  The solution for now is to change 
master to  to the errored master bin log and position and have it start 
replication from the spot where it is.  When this happens the IO and SQL 
thread are found choked, with no error on show slave status, but the MySQL 
.err log shows the error.

Any ideas?

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]