mysql> SHOW SLAVE STATUS\G *************************** 1. row *************************** Slave_IO_State: Queueing master event to the relay log Master_Host: 192.168.250.2 Master_User: root Master_Port: 3306 Connect_Retry: 60 Master_Log_File: www-bin.002242 Read_Master_Log_Pos: 4 Relay_Log_File: xp64-relay-bin.002683 Relay_Log_Pos: 18446744073656553925 Relay_Master_Log_File: www-bin.001342 Slave_IO_Running: Yes Slave_SQL_Running: No Replicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 1593 Last_Error: Relay log read failure: 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 binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Skip_Counter: 0 Exec_Master_Log_Pos: 4 Relay_Log_Space: 4828115 Until_Condition: None Until_Log_File: Until_Log_Pos: 0 Master_SSL_Allowed: No Master_SSL_CA_File: Master_SSL_CA_Path: Master_SSL_Cert: Master_SSL_Cipher: Master_SSL_Key: Seconds_Behind_Master: NULL Master_SSL_Verify_Server_Cert: No Last_IO_Errno: 0 Last_IO_Error: Last_SQL_Errno: 1593 Last_SQL_Error: Relay log read failure: 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 binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. 1 row in set (0.00 sec) E:\builds\5.1-win-src\sql\debug>mysqld --console --skip-name-resolve --skip-grant-tables --server-id=13 --port=3306 InnoDB: The first specified data file .\ibdata1 did not exist: InnoDB: a new database to be created! 071102 9:41:11 InnoDB: Setting file .\ibdata1 size to 10 MB InnoDB: Database physically writes the file full: wait... 071102 9:41:11 InnoDB: Log file .\ib_logfile0 did not exist: new to be created InnoDB: Setting log file .\ib_logfile0 size to 5 MB InnoDB: Database physically writes the file full: wait... 071102 9:41:11 InnoDB: Log file .\ib_logfile1 did not exist: new to be created InnoDB: Setting log file .\ib_logfile1 size to 5 MB InnoDB: Database physically writes the file full: wait... InnoDB: Doublewrite buffer not found: creating new InnoDB: Doublewrite buffer created InnoDB: Creating foreign key constraint system tables InnoDB: Foreign key constraint system tables created 071102 9:41:12 InnoDB: Started; log sequence number 0 0 071102 9:41:12 [Note] mysqld: ready for connections. Version: '5.1.23-beta-debug' socket: '' port: 3306 Source distribution 071102 9:41:28 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--relay-log=E:\builds\5.1-win-src\sql\data\xp64-relay-bin' to avoid this problem. 071102 9:41:28 [Note] Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log 'E:\builds\5.1-win-src\sql\data\xp64-relay-bin.000001' position: 4 071102 9:41:28 [Note] Slave I/O thread: connected to master 'root@192.168.250.2:3306',replication started in log 'FIRST' at position 4 071102 9:46:20 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error 071102 9:46:20 [ERROR] Slave SQL: Relay log read failure: 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 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: 1593 071102 9:46:20 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'www-bin.001342' position 4