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

本文主要是介绍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即可。

这篇关于Plugin group_replication reported: 'Connecting socket to address 192.168.233.137 in port 33061 faile的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/609587

相关文章

matlab读取NC文件(含group)

matlab读取NC文件(含group): NC文件数据结构: 代码: % 打开 NetCDF 文件filename = 'your_file.nc'; % 替换为你的文件名% 使用 netcdf.open 函数打开文件ncid = netcdf.open(filename, 'NC_NOWRITE');% 查看文件中的组% 假设我们想读取名为 "group1" 的组groupName

AI辅助编程里的 Atom Group 的概念和使用

背景 在我们实际的开发当中,一个需求往往会涉及到多个文件修改,而需求也往往有相似性。 举个例子,我经常需要在 auto-coder中需要添加命令行参数,通常是这样的: /coding 添加一个新的命令行参数 --chat_model 默认值为空 实际上这个需求涉及到以下文件列表: /Users/allwefantasy/projects/auto-coder/src/autocoder/auto

Jenkins 通过 Version Number Plugin 自动生成和管理构建的版本号

步骤 1:安装 Version Number Plugin 登录 Jenkins 的管理界面。进入 “Manage Jenkins” -> “Manage Plugins”。在 “Available” 选项卡中搜索 “Version Number Plugin”。选中并安装插件,完成后可能需要重启 Jenkins。 步骤 2:配置版本号生成 打开项目配置页面。在下方找到 “Build Env

Gerrit与Gitlab同步配置replication其他配置

一、Gerrit与Gitlab同步配置 当配置好gerrit环境后,还需要与现有gitlab库进行同步配置,否则会影响现有开发与打包流程。 1.安装gerrit replication插件 unzip gerrit.warcp WEB-INF/plugins/replication.jar ~/temp/ssh -p 29418 admin@172.19.16.64 gerrit plu

Java Socket服务器端与客户端的编程步骤总结

一,InetAddress类: InetAddress类没有构造方法,所以不能直接new出一个对象; 可以通过InetAddress类的静态方法获得InetAddress的对象; InetAddress.getLocalHost(); InetAddress.getByName(""); 类主要方法: String - address.getHostName(); String - addre

VC环境下window网络程序:UDP Socket程序

最近在学Windows网络编程,正好在做UDPsocket的程序,贴上来: 服务器框架函数:              socket();    bind();    recfrom();  sendto();  closesocket(); 客户机框架函数:            socket();      recfrom();  sendto();  closesocket();

C++常见异常汇总(三): fatal error: google/protobuf/port_def.inc

文章目录 1、fatal error : sw/redis++/redis.h2、fatal error: dwarf.h: No such file or directory3、fatal error: elfutils/libdw.h: No such file or directory4、fatal error: libunwind.h: No such file or directo

group by 新体会

group by 分组语句中的 select 后面查询的东西,只能是 group by 中的字段或聚合函数,如果含有group by 中的没有的字段,sql 会报错。 表users   例子:  1.select count(1),sex from users group by sex; sql执行正确   2.select count(id),sex from users gr

Autosar(Davinci) --- 创建一个S/R类型的port(下)

前言:         前面章节我们讲解了S/R类型的Port如何创建,这一章节,我们着重讲一下生成的代码,以及我们如何添加代码让这些门与灯之间的关系产生连接。 一、CtSaDoor.c 在【Rte.c】的【IO_TASK】中我们可以看到,反复的判断Rte_Ev_Cyclic_IO_Task_0_200ms这个条件是否成立,当200ms到达时,调用RCtSaDoorReadDoor函数,去读

Tomcat启动报错:transport error 202: bind failed: Address already in use

Tomcat启动报错:transport error 202: bind failed: Address already in use 了,上网查找了下面这篇文章。也是一种解决办法。 下文来自:http://blog.csdn.net/sam031503/article/details/7037033 tomcat 启动日志报出以下错误:  ERROR: transport err