In Mysql replication Slave_IO_Running:No


Root cause: The error occur due to the master log file does not match in the slave when you query in mysql “show slave status\G” .

Solution:

a. Check the master log file in mysql master by

mysql> show master status;

+——————+———-+————–+——————+

| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |

+——————+———-+————–+——————+

| mysql-bin.000154 | 107 | | |

+——————+———-+————–+——————+

1 row in set (0.00 sec)

 

mysql>

b. Compare the log file in slave by running the command “show slave status\G” and try to set the same log file in slave mysql server.

c. Go to slave mysql server and run the below command.

mysql>STOP SLAVE;

mysql>CHANGE MASTER TO MASTER_LOG_POS = 0;

mysql>CHANGE MASTER TO MASTER_LOG_FILE = 'mysql-bin.000154';

mysql>START SLAVE;

 

This solves the problem…

 

Advertisements

One Response to In Mysql replication Slave_IO_Running:No

  1. Peter says:

    hello,
    i was looking for the solution about 3 hours (maybe more:)).
    i just want to tell you: thank you!

    ps. why we have to change MASTER_LOG_POS for “0”?
    all manuals are talking about set the save value like a master.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: