May be a full off the filesystem where the relay logbin file is ?
Marc.
-----Message d'origine-----
De?: seho@stripped [mailto:seho@stripped]
Envoye?: mercredi 9 juin 2004 09:46
A?: mysql@stripped
Objet?: Replication is currupted ...Please help me...
Hi all.
My company has three Mysql DB servers.
one is master, the other are slaves.
master's version is 3.23.54-log.
two slaves's version is 4.0.17
and Os of all servers is linux 7.3
2 days ago, another slave's replication was currupted unexpactedly, but the other slave
was ok.
I don't know what this replaction was currepted.
Anybody know what I do?
Please let me know...
this is err_message at that time.
---------------------------------------------------------------------------------------------------------
040609 13:09:14 Error in Log_event::read_log_event(): 'Event too big', data_len:
1852795251, event_type: 110
040609 13:09:14 Error reading relay log event: slave SQL thread aborted because of I/O
error
040609 13:09:14 Slave: Could not parse relay log event entry. The possible reasons are:
the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the
binary log), the slave's relay log is corrupted (you can check this by running
'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's
MySQL code. If you want to check the master's or slave's MySQL code. If you want to check
the master's
binary log or slave's relay log, you will be able to know their names by issuing 'SHOW
SLAVE STATUS' on this slave. Error_code: 0
040609 13:32:16 Slave I/O thread exiting, read up to log 'www5-bin.001', position
84904657
------------------------------------------------------------------------------------------------------------
