Upgrade to 5.0.51b seems to have solved the problem. On wednesday, I saw
the problem about a dozen times during a peak time. Upgraded wednesday
night and have not seen the error since.
Thanks
Dominik
Juan Eduardo Moreno wrote:
Hi,
This error occur when slave servers could incorrectly interpret an
out-of-memory error from the master and reconnect using the wrong binary
log position.
This was fix in 5.0.48 version. Please, try to update your version (
from 5.0.45) of mysql and try again.
regards,
Juan
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
