Mailing List
Home
MySQL General - General MySQL discussion
MaxDB - Everything about MaxDB, formerly known as SAP DB
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
ODBC - ODBC with the MySQL Connector/ODBC driver
Perl - Perl support for MySQL with DBI and DBD::mysql
MySQL++ - Programming with the C++ API to MySQL
Subjects
• mysql openssl Question
• mysql:it 's a db not a dbms how it 's possible?!
• Does the binary log enabling affect the MySQL performances?
• Strange behavior, Table Level Permission
• FULLTEXT query format question
• Preventing Duplicate Entries
• Comparing and writing out BLOBS
• Executing MySQL Commands From Within C Program
• Can 't access mysql after kernel upgrade
• Mysql 4 0 Oracle Stored Procedure Trigger Conversion
• Downgrade Mysql from 4 to 3 23
• MySQL Cluster Software
• mysql test 4 1 fails with the gis test
• ERROR 2002: Can 't connect to local MySQL server through socket
• Getting Identity after INSERT
• Update one field with more fields from another table
• ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
• mysql have same function mthod as Oracle decode()
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Replication is currupted ...Please help me...

Replication is currupted ...Please help me...

2004-06-09       - By Mechain Marc

 Back
Reply:     1     2  

May be a full off the filesystem where the relay logbin file is ?

Marc.

-- --Message d 'origine-- --
De?: seho@(protected) [mailto:seho@(protected)]
Envoye?: mercredi 9 juin 2004 09:46
A?: mysql@(protected)
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
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- -----

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=mysql @(protected)