I had this same problem. This isn't fool proof or recomended but what
i ended up doing was calling mysqlbinlog over and over again
incrementing --position (or --offset i can't remember) until it picked
up a good record again and kept going. Chances are you will lose
queries but it does work.
-ERic
Hello everyone,
We're having a problem with replication. The servers are all running 4.0.18 under SuSE
Linux 9.1 Professional.
I noticed that the two slaves were both showing a status of I/O thread not running.
In the mysqld.log file for both slaves I found the following entry:
040628 12:59:0
