[ERROR] Slave I/O: error connecting to master

本文涉及的产品
RDS MySQL Serverless 基础系列,0.5-2RCU 50GB
云数据库 RDS MySQL,集群系列 2核4GB
推荐场景:
搭建个人博客
云数据库 RDS MySQL,高可用系列 2核4GB
简介:
刚配置的MySQL主从,在从机上看到 
点击(此处)折叠或打开 
mysql> SHOW slave STATUS \\G 
*************************** 1. row *************************** 
               Slave_IO_State: Connecting to master 
                  Master_Host: 172.17.210.199 
                  Master_User: my 
                  Master_Port: 3306 
                Connect_Retry: 60 
              Master_Log_File: masters-bin.000003 
          Read_Master_Log_Pos: 1224 
               Relay_Log_File: testmysql-relay-bin.000001 
                Relay_Log_Pos: 4 
        Relay_Master_Log_File: masters-bin.000003 
             Slave_IO_Running: Connecting 
            Slave_SQL_Running: Yes 
              Replicate_Do_DB: 
          Replicate_Ignore_DB: 
看日志有很多: 
点击(此处)折叠或打开 
141010 0:02:48 [ERROR] Slave I/O: error connecting to master \'my@172.17.210.199:3306\' - retry-time: 60 retries: 1, Error_code: 2003 
141010 0:03:48 [ERROR] Slave I/O: error connecting to master \'my@172.17.210.199:3306\' - retry-time: 60 retries: 2, Error_code: 2003 
141010 0:04:48 [ERROR] Slave I/O: error connecting to master \'my@172.17.210.199:3306\' - retry-time: 60 retries: 3, Error_code: 2003 
141010 0:05:48 [ERROR] Slave I/O: error connecting to master \'my@172.17.210.199:3306\' - retry-time: 60 retries: 4, Error_code: 2003 
141010 0:06:48 [ERROR] Slave I/O: error connecting to master \'my@172.17.210.199:3306\' - retry-time: 60 retries: 5, Error_code: 2003 
141010 0:07:48 [ERROR] Slave I/O: error connecting to master \'my@172.17.210.199:3306\' - retry-time: 60 retries: 6, Error_code: 2003 
解决方法:  
  
导致lave_IO_Running 为connecting 的原因主要有以下 3 个方面:  
  
1、网络不通  
2、密码不对  
3、pos不对 
解决步骤: 
1、对于第一个问题,一般情况下都是可以排除的,也是最容易排除的。 
2、在主库上修改用来复制的用户的密码。 
3、 在做chang to 的时候注意log_pos 是否跟此时主机的一样。在主机上 show master status \G ;可以查看到 
mysql> show master status \G; 
*************************** 1. row *************************** 
             File: masters-bin.000003 
         Position: 2392 
     Binlog_Do_DB: 
Binlog_Ignore_DB: 
Executed_Gtid_Set: 
1 row in set (0.00 sec) 
ERROR: 
No query specified 
从机上面执行change to 的正确 
CHANGE MASTER TO 
MASTER_HOST='172.17.210.199', 
MASTER_USER='my', 
MASTER_PASSWORD='123456', 
MASTER_LOG_FILE='masters-bin.000003', 
MASTER_LOG_POS= 2392; 

我的问题,就是主机的防火墙没有关闭 


==================================================================== 
由于主服务器异外重启, 导致从报错, 错误如下: 
show slave status错误: 
mysql> show slave status\G 
Master_Log_File: mysql-bin.000288 
Read_Master_Log_Pos: 627806304 
Relay_Log_File: mysql-relay-bin.000990 
Relay_Log_Pos: 627806457 
Relay_Master_Log_File: mysql-bin.000288 
Slave_IO_Running: No 
Slave_SQL_Running: Yes 
Exec_Master_Log_Pos: 627806304 
Relay_Log_Space: 627806663 


...... 
Last_IO_Error: Got fatal error 1236 from master when  reading data from binary log: 
'Client requested master to start  replication from impossible position' 
mysql错误日志: 

tail /data/mysql/mysql-error.log 
111010 17:35:49 [ERROR] Error reading packet from server: Client requested master 
to start replication from impossible position ( server_errno=1236) 
111010 17:35:49 [ERROR] Slave I/O: Got fatal error 1236 from master when reading data 
from binary log: 'Client requested master to start replication from impossible 
position', Error_code: 1236 
111010 17:35:49 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000288', 
position 627806304 
按照习惯, 先尝试必改position位置. 

mysql> stop slave; 
mysql> change master to master_log_file='mysql-bin.000288',master_log_pos=627625751; 
mysql> start slave; 
错误依旧, 接下来登陆到主服务器查看binlog日志. 
先按照错误点的标记去主服务器日志中查找: 

[root@db1 ~]# mysqlbinlog --start-position=627655136 /data/mysql/binlog/mysql-bin.000288 
/*!40019 SET @@session.max_insert_delayed_threads=0*/; 
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/; 
DELIMITER /*!*/; 
# at 4 
#111010 13:31:19 server id 4 end_log_pos 106 Start: binlog v 4, server v 5.1.45-log 
created 111010 13:31:19 
# Warning: this binlog is either in use or was not closed properly. 
BINLOG ' 
F1aTTg8EAAAAZgAAAGoAAAABAAQANS4xLjQ1LWxvZwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA 
AAAAAAAAAAAAAAAAAAAAAAAAEzgNAAgAEgAEBAQEEgAAUwAEGggAAAAICAgC 
'/*!*/; 
DELIMITER ; 
# End of log file 
ROLLBACK /* added by mysqlbinlog */; 
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/; 
没有看到这个位置. 

[root@db1 ~]# mysqlbinlog /data/mysql/binlog/mysql-bin.000288 > test.txt 

less text.txt 
看最后一部分 
# at 627625495 
#111010 16:35:46 server id 1 end_log_pos 627625631 Query thread_id=45613333 
exec_time=32758 error_code=0 
SET TIMESTAMP=1318289746/*!*/; 
delete from freeshipping_bef_update where part='AR-4006WLM' and code='' 
/*!*/; 
# at 627625631 
#111010 16:35:46 server id 1 end_log_pos 627625751 Query thread_id=45613333 
exec_time=32758 error_code=0 
SET TIMESTAMP=1318289746/*!*/; 
delete from shippingFee_special where part='AR-4006WLM' 
/*!*/; 
DELIMITER ; 
# End of log file 
ROLLBACK /* added by mysqlbinlog */; 
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/; 
找到最接近错误标记627655136的一个position是627625631. 

再回到slave机器上change master, 将postion指向这个位置. 

mysql> stop slave; 
Query OK, 0 rows affected (0.00 sec) 

mysql> change master to master_log_file='mysql-bin.000288',master_log_pos=627625631; 
Query OK, 0 rows affected (0.06 sec) 

mysql> start slave; 
Query OK, 0 rows affected (0.00 sec) 
再次查看 

mysql> show slave status\G 
*************************** 1. row *************************** 
Slave_IO_State: Queueing master event to the relay log 
Master_Host: 192.168.21.105 
Master_User: rep 
Master_Port: 3306 
Connect_Retry: 10 
Master_Log_File: mysql-bin.000289 
Read_Master_Log_Pos: 25433767 
Relay_Log_File: mysql-relay-bin.000003 
Relay_Log_Pos: 630 
Relay_Master_Log_File: mysql-bin.000289 
Slave_IO_Running: Yes 
Slave_SQL_Running: Yes 
主从同步正常了, 同样的方法修复其它slave机器.
相关实践学习
如何快速连接云数据库RDS MySQL
本场景介绍如何通过阿里云数据管理服务DMS快速连接云数据库RDS MySQL,然后进行数据表的CRUD操作。
全面了解阿里云能为你做什么
阿里云在全球各地部署高效节能的绿色数据中心,利用清洁计算为万物互联的新世界提供源源不断的能源动力,目前开服的区域包括中国(华北、华东、华南、香港)、新加坡、美国(美东、美西)、欧洲、中东、澳大利亚、日本。目前阿里云的产品涵盖弹性计算、数据库、存储与CDN、分析与搜索、云通信、网络、管理与监控、应用服务、互联网中间件、移动服务、视频服务等。通过本课程,来了解阿里云能够为你的业务带来哪些帮助     相关的阿里云产品:云服务器ECS 云服务器 ECS(Elastic Compute Service)是一种弹性可伸缩的计算服务,助您降低 IT 成本,提升运维效率,使您更专注于核心业务创新。产品详情: https://www.aliyun.com/product/ecs
相关文章
|
8月前
|
负载均衡 Java 应用服务中间件
Client not connected, current status:STARTING
Client not connected, current status:STARTING
589 1
|
8月前
|
NoSQL Redis
解决(error) ERR Errors trying to SHUTDOWN. Check logs.问题~
解决(error) ERR Errors trying to SHUTDOWN. Check logs.问题~
229 0
ERR Errors trying to SHUTDOWN. Check logs.
ERR Errors trying to SHUTDOWN. Check logs.
133 0
|
NoSQL MongoDB
运行 mongo 出现 Error: couldn‘t connect to server 127.0.0.1:27017, connection attempt failed
运行 mongo 出现 Error: couldn‘t connect to server 127.0.0.1:27017, connection attempt failed
1099 0
运行 mongo 出现 Error: couldn‘t connect to server 127.0.0.1:27017, connection attempt failed
|
关系型数据库 MySQL Linux
Error connecting to master ‘slave@192.168.200.128:3307‘ - retry-time: 30 retries: 1
Error connecting to master ‘slave@192.168.200.128:3307‘ - retry-time: 30 retries: 1
Error connecting to master ‘slave@192.168.200.128:3307‘ - retry-time: 30 retries: 1
|
开发工具 git
关于 error: refname refs/heads/master not found 的问题
关于 error: refname refs/heads/master not found 的问题
783 0
|
应用服务中间件 nginx
[error] 17755#0: *58522 readv() failed (104: Connection reset by peer) while reading upstream
[error] 17755#0: *58522 readv() failed (104: Connection reset by peer) while reading upstream
5093 0

热门文章

最新文章

下一篇
开通oss服务