Plugin group_replication reported: 'Connecting socket to address 192.168.233.137 in port 33061 faile

MySQL Group Replication START GROUP_REPLICATION启动时报错

2018-11-02T14:50:23.337291+08:00 8 [Note] Slave SQL thread for channel 'group_replication_applier' initialized, starting replication in log 'FIRST' at position 0, relay log './node1-relay-bin-group_replication_applier.000015' position: 4
2018-11-02T14:50:23.337339+08:00 3 [Note] Plugin group_replication reported: 'Group Replication applier module successfully initialized!'
2018-11-02T14:50:23.337854+08:00 3 [Note] Plugin group_replication reported: 'auto_increment_increment is set to 7'
2018-11-02T14:50:23.337880+08:00 3 [Note] Plugin group_replication reported: 'auto_increment_offset is set to 137'
2018-11-02T14:50:23.339542+08:00 0 [Note] Plugin group_replication reported: 'state 0 action xa_init'
2018-11-02T14:50:23.639334+08:00 0 [Note] Plugin group_replication reported: 'Successfully bound to 0.0.0.0:33061 (socket=51).'
2018-11-02T14:50:23.639451+08:00 0 [Note] Plugin group_replication reported: 'Successfully set listen backlog to 32 (socket=51)!'
2018-11-02T14:50:23.639510+08:00 0 [Note] Plugin group_replication reported: 'Successfully unblocked socket (socket=51)!'
2018-11-02T14:50:23.639586+08:00 0 [Note] Plugin group_replication reported: 'Ready to accept incoming connections on 0.0.0.0:33061 (socket=51)!'
2018-11-02T14:50:23.639692+08:00 0 [Note] Plugin group_replication reported: 'connecting to 192.168.233.137 33061'
2018-11-02T14:50:23.640343+08:00 0 [Warning] Plugin group_replication reported: 'connect - Error connecting (socket=52, error=13, error message='Permission denied').'
2018-11-02T14:50:23.640380+08:00 0 [Note] Plugin group_replication reported: 'Connecting socket to address 192.168.233.137 in port 33061 failed with error 13 - Permission denied.'
2018-11-02T14:50:24.640661+08:00 0 [Note] Plugin group_replication reported: 'connecting to 192.168.233.137 33061'
2018-11-02T14:50:24.641111+08:00 0 [Warning] Plugin group_replication reported: 'connect - Error connecting (socket=52, error=13, error message='Permission denied').'
2018-11-02T14:50:24.641159+08:00 0 [Note] Plugin group_replication reported: 'Connecting socket to address 192.168.233.137 in port 33061 failed with error 13 - Permission denied.'
2018-11-02T14:50:25.641936+08:00 0 [Note] Plugin group_replication reported: 'connecting to 192.168.233.137 33061'
2018-11-02T14:50:25.642054+08:00 0 [Warning] Plugin group_replication reported: 'connect - Error connecting (socket=52, error=13, error message='Permission denied').'
2018-11-02T14:50:27.645129+08:00 0 [Note] Plugin group_replication reported: 'connecting to 192.168.233.137 33061'
2018-11-02T14:50:27.645236+08:00 0 [Warning] Plugin group_replication reported: 'connect - Error connecting (socket=52, error=13, error message='Permission denied').'
2018-11-02T14:50:27.645251+08:00 0 [Note] Plugin group_replication reported: 'Connecting socket to address 192.168.233.137 in port 33061 failed with error 13 - Permission denied.'
2018-11-02T14:50:28.645825+08:00 0 [Note] Plugin group_replication reported: 'connecting to 192.168.233.137 33061'
2018-11-02T14:50:28.645912+08:00 0 [Warning] Plugin group_replication reported: 'connect - Error connecting (socket=52, error=13, error message='Permission denied').'
2018-11-02T14:50:28.645919+08:00 0 [Note] Plugin group_replication reported: 'Connecting socket to address 192.168.233.137 in port 33061 failed with error 13 - Permission denied.'
2018-11-02T14:50:29.646876+08:00 0 [Note] Plugin group_replication reported: 'connecting to 192.168.233.137 33061'
2018-11-02T14:50:33.651051+08:00 0 [Note] Plugin group_replication reported: 'connecting to 192.168.233.137 33061'
2018-11-02T14:50:33.651347+08:00 0 [Warning] Plugin group_replication reported: 'connect - Error connecting (socket=52, error=13, error message='Permission denied').'
2018-11-02T14:50:33.651385+08:00 0 [Note] Plugin group_replication reported: 'Connecting socket to address 192.168.233.137 in port 33061 failed with error 13 - Permission denied.'
2018-11-02T14:50:33.651533+08:00 0 [ERROR] Plugin group_replication reported: '[GCS] Error connecting to the local group communication engine instance.'
2018-11-02T14:50:33.651582+08:00 0 [Note] Plugin group_replication reported: 'state 4337 action xa_exit'
2018-11-02T14:50:33.652643+08:00 0 [Note] Plugin group_replication reported: 'Exiting xcom thread'
2018-11-02T14:50:33.692120+08:00 0 [ERROR] Plugin group_replication reported: '[GCS] The member was unable to join the group. Local port: 33061'
2018-11-02T14:51:23.338509+08:00 3 [ERROR] Plugin group_replication reported: 'Timeout on wait for view after joining group'
2018-11-02T14:51:23.338626+08:00 3 [Note] Plugin group_replication reported: 'Requesting to leave the group despite of not being a member'
2018-11-02T14:51:23.338665+08:00 3 [ERROR] Plugin group_replication reported: '[GCS] The member is leaving a group without being on one.'
2018-11-02T14:51:23.339683+08:00 3 [Note] Plugin group_replication reported: 'auto_increment_increment is reset to 1'
2018-11-02T14:51:23.339885+08:00 3 [Note] Plugin group_replication reported: 'auto_increment_offset is reset to 1'
2018-11-02T14:51:23.341219+08:00 8 [Note] Error reading relay log event for channel 'group_replication_applier': slave SQL thread was killed
2018-11-02T14:51:23.369092+08:00 5 [Note] Plugin group_replication reported: 'The group replication applier thread was killed'

在centos-7 MySQL5.7中按照官方推荐的端口配置为33061,当时在运行的时候报权限错误。在START GROUP_REPLICATION之前我已经关闭了防火墙,命令如下:

# 关闭防火墙
systemctl stop firewalld.service
# 禁用防火墙
systemctl disable firewalld.service

经过一番资源搜索,还需要禁用selinux,配置文件路径/etc/selinux/config修改如下变量值

SELINUX=disabled 

然后重启centos即可。

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
根据引用中的内容,当无法连接到特定IP地址和端口时,可能是由于以下原因导致连接失败。首先,需要确认连接的主机上是否开启了SSH服务。如果没有开启SSH服务,那么连接将无法建立。其次,还需要确保网络配置正确,特别是在使用虚拟机时,需要确认主机和虚拟机之间的网络连接是正常的。 根据引用中的内容,某些情况下,出现"Could not connect to '192.168.171.128' (port 22): Connection failed"的错误可能与Qt平台插件有关。解决这个问题的方法可能是安装或重新配置相关的Qt平台插件。 最后,根据引用中的内容,为了确保虚拟机和宿主机之间的连接正常,可以尝试使用ping命令来验证网络连接是否正常。如果ping命令可以成功,那么表示网络连接是正常的。 综上所述,当出现"Could not connect to '192.168.171.128' (port 22): Connection failed"的错误时,需要检查目标主机上是否开启了SSH服务,并确保网络连接正常。如果问题仍然存在,可以考虑查看相关的日志文件或尝试其他网络调试方法来进一步排除问题。<span class="em">1</span><span class="em">2</span><span class="em">3</span> #### 引用[.reference_title] - *1* *3* [Could not connect to ‘192.168.203.128‘ (port 22): Connection failed.](https://blog.csdn.net/qq_41885673/article/details/118020012)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatgptT3_2"}}] [.reference_item style="max-width: 50%"] - *2* [Ubuntu18.04下解决Qt出现qt.qpa.plugin:Could not load the Qt platform plugin “xcb“问题](https://download.csdn.net/download/weixin_38695061/12841039)[target="_blank" data-report-click={"spm":"1018.2226.3001.9630","extra":{"utm_source":"vip_chatgpt_common_search_pc_result","utm_medium":"distribute.pc_search_result.none-task-cask-2~all~insert_cask~default-1-null.142^v93^chatgptT3_2"}}] [.reference_item style="max-width: 50%"] [ .reference_list ]

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值