mysql 从库日志_mysql从库停了，如何跳过从库日志？

本帖最后由 lixunpeng 于 2013-5-23 13:56 编辑

有人改了从库密码，后来又改了回去，结果从库就停了，感觉是中断了mysqld进程导致的。

主库的日志文件看起来都正常，而从库就不正常了，我觉得应该跳过从库日志，就像跳过主库的change masete一样，但如何跳过从库日志呢？

这是从库的日志：

-rw-rw---- 1 mysql mysql 1.1G May 22 16:08 mysql-bin.001848

-rw-rw---- 1 mysql mysql 1.1G May 22 21:15 mysql-bin.001849

-rw-rw---- 1 mysql mysql 1.1G May 23 03:37 mysql-bin.001850

-rw-rw---- 1 mysql mysql 1.1G May 23 07:01 mysql-bin.001851

-rw-rw---- 1 mysql mysql 1.1G May 23 09:28 mysql-bin.001852

-rw-rw---- 1 mysql mysql 964M May 23 11:34 mysql-bin.001853

-rw-rw---- 1 mysql mysql 2.0M May 23 11:53 mysql-bin.001854

-rw-rw---- 1 mysql mysql 8.5K May 23 11:53 mysql-bin.index

-rw-rw---- 1 mysql mysql  70K May 23 13:20 mysqld.err

-rw-rw---- 1 mysql mysql    5 May 23 11:53 mysqld.pid

-rw-rw---- 1 mysql mysql  200 May 23 10:15 mysqld-relay-bin.001423

-rw-rw---- 1 mysql mysql 621M May 23 11:34 mysqld-relay-bin.001424

-rw-rw---- 1 mysql mysql  157 May 23 11:53 mysqld-relay-bin.001425

-rw-rw---- 1 mysql mysql 404M May 23 12:23 mysqld-relay-bin.001426

-rw-rw---- 1 mysql mysql  200 May 23 12:23 mysqld-relay-bin.001427

-rw-rw---- 1 mysql mysql 415M May 23 13:20 mysqld-relay-bin.001428

-rw-rw---- 1 mysql mysql  27M May 23 13:24 mysqld-relay-bin.001429

-rw-rw---- 1 mysql mysql  182 May 23 13:20 mysqld-relay-bin.index

mysql> show slave status\G;

*************************** 1. row ***************************

Slave_IO_State: Waiting for master to send event

Master_Host: 10.11.45.3

Master_User: replication

Master_Port: 3310

Connect_Retry: 60

Master_Log_File: mysql-bin.001933

Read_Master_Log_Pos: 547832499

Relay_Log_File: mysqld-relay-bin.001424

Relay_Log_Pos: 650825663

Relay_Master_Log_File: mysql-bin.001932

Slave_IO_Running: Yes

Slave_SQL_Running: No

Replicate_Do_DB:

Replicate_Ignore_DB: mysql,test,mysql,test

Replicate_Do_Table:

Replicate_Ignore_Table:

Replicate_Wild_Do_Table:

Replicate_Wild_Ignore_Table:

Last_Errno: 1594

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: 1

Exec_Master_Log_Pos: 650825517

Relay_Log_Space: 1622271478

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: 1594

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.

Replicate_Ignore_Server_Ids:

Master_Server_Id: 45003

1 row in set (0.00 sec)

ERROR:

No query specified