本篇文章给大家分享的是有关PXC搭建问题有哪些,小编觉得挺实用的,因此分享给大家学习,希望大家阅读完这篇文章后可以有所收获,话不多说,跟着小编一起来看看吧。无法启动第一个节点2017-11-18T15:53
本篇文章给大家分享的是有关PXC搭建问题有哪些,小编觉得挺实用的,因此分享给大家学习,希望大家阅读完这篇文章后可以有所收获,话不多说,跟着小编一起来看看吧。
无法启动第一个节点
2017-11-18T15:53:00.732400Z 0 [Note] WSREP: GComm: connecting to group 'zrz', peer '192.168.1.101:'
2017-11-18T15:53:00.733049Z 0 [Note] WSREP: (8dec793b, 'tcp://0.0.0.0:4567') connection established to 8dec793b tcp://192.168.1.101:4567
2017-11-18T15:53:00.733073Z 0 [Warning] WSREP: (8dec793b, 'tcp://0.0.0.0:4567') address 'tcp://192.168.1.101:4567' points to own listening address, blacklisting
2017-11-18T15:53:03.733022Z 0 [Note] WSREP: (8dec793b, 'tcp://0.0.0.0:4567') connection to peer 8dec793b with addr tcp://192.168.1.101:4567 timed out, no messages seen in PT3S
2017-11-18T15:53:03.733131Z 0 [Warning] WSREP: no nodes coming from prim view, prim not possible
2017-11-18T15:53:03.733151Z 0 [Note] WSREP: Current view of cluster as seen by this node
view (view_id(NON_PRIM,8dec793b,1)
memb {
8dec793b,0
}
joined {
}
left {
}
partitioned {
}
)
2017-11-18T15:53:04.233267Z 0 [Warning] WSREP: last inactive check more than PT1.5S aGo (PT3.50093S), skipping check
2017-11-18T15:53:33.736202Z 0 [Note] WSREP: Current view of cluster as seen by this node
view ((empty))
2017-11-18T15:53:33.736368Z 0 [ERROR] WSREP: failed to open gcomm backend connection: 110: failed to reach primary view: 110 (Connection timed out)
at gcomm/src/pc.cpp:connect():158
2017-11-18T15:53:33.736383Z 0 [ERROR] WSREP: gcs/src/gcs_core.cpp:gcs_core_open():208: Failed to open backend connection: -110 (Connection timed out)
2017-11-18T15:53:33.736618Z 0 [ERROR] WSREP: gcs/src/gcs.cpp:gcs_open():1463: Failed to open channel 'zrz' at 'gcomm://192.168.1.101': -110 (Connection timed out)
2017-11-18T15:53:33.736631Z 0 [ERROR] WSREP: gcs connect failed: Connection timed out
2017-11-18T15:53:33.736636Z 0 [ERROR] WSREP: Provider/Node (gcomm://192.168.1.101) failed to establish connection with cluster (reason: 7)
2017-11-18T15:53:33.736641Z 0 [ERROR] Aborting
2017-11-18T15:53:33.736651Z 0 [Note] Giving 0 client threads a chance to die gracefully
2017-11-18T15:53:33.736656Z 0 [Note] WSREP: Waiting for active wsrep applier to exit
2017-11-18T15:53:33.736659Z 0 [Note] WSREP: Service disconnected.
2017-11-18T15:53:33.736664Z 0 [Note] WSREP: Waiting to close threads......
2017-11-18T15:53:38.736758Z 0 [Note] WSREP: Some threads may fail to exit.
2017-11-18T15:53:38.736807Z 0 [Note] Binlog end
2017-11-18T15:53:38.737048Z 0 [Note] /usr/local/Mysql/bin/mysqld: Shutdown complete
问题主要描述:错误日志提示无法成功加入节点
原因:第一个节点启动时需要指定自己为作为集群启动
解决办法:加--wsrep-new-cluster参数启动,官方指定的bootstrap-pxc参数并不生效
第二个节点无法加入
2017-11-19T15:55:29.227793Z 0 [ERROR] WSREP: Process completed with error: wsrep_sst_xtrabackup-v2 --role 'donor' --address '192.168.1.103:4444/xtrabackup_sst//1' --Socket '/data/mysql/3306/tmp/mysql3306.sock' --datadir '/data/mysql/3306/data/' --defaults-file '/data/mysql/3306/my.cnf' --defaults-group-suffix '' --binlog 'mysql-bin' --gtid 'df47a753-cd3D-11e7-85b5-66f48d655632:0': 32 (Broken pipe)
2017-11-19T15:55:29.227868Z 0 [ERROR] WSREP: Command did not run: wsrep_sst_xtrabackup-v2 --role 'donor' --address '192.168.1.103:4444/xtrabackup_sst//1' --socket '/data/mysql/3306/tmp/mysql3306.sock' --datadir '/data/mysql/3306/data/' --defaults-file '/data/mysql/3306/my.cnf' --defaults-group-suffix '' --binlog 'mysql-bin' --gtid 'df47a753-cd3d-11e7-85b5-66f48d655632:0'
问题描述:无法成功传输SST
在mysql/bin目录下执行wsrep_sst_xtrabackup-v2 --role 'donor' --address '192.168.1.103:4444/xtrabackup_sst//1' --socket '/data/mysql/3306/tmp/mysql3306.sock' --datadir '/data/mysql/3306/data/' --defaults-file '/data/mysql/3306/my.cnf' --defaults-group-suffix '' --binlog 'mysql-bin' --gtid 'df47a753-cd3d-11e7-85b5-66f48d655632:0'
提示:
which: no socat in (/usr/sbin:/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/usr/local/mysql/bin:/usr/local/pxc/bin:/root/bin)
原因:缺少依赖组件socat
解决办法:yum -y install socat
第二个几点无法加入
2017-11-19T15:15:11.735984Z 2 [Note] WSREP: New cluster view: global state: 50970ac2-cc82-11e7-8b90-c716227b4ac7:0, view# 8: Primary, number of nodes: 2, my index: 0, protocol version 3
2715-2017-11-19T15:15:11.735993Z 2 [Warning] WSREP: Gap in state sequence. Need state transfer.
2716-2017-11-19T15:15:11.736057Z 0 [Note] WSREP: Initiating SST/IST transfer on JOINER side (wsrep_sst_rsync --role 'joiner' --address '192.168.1.102' --datadir '/data/mysql/3306/data/' --defaults-file '/data/mysql/3306/my.cnf' --defaults-group-suffix '' --parent '3104' --binlog 'mysql-bin' )
2717:which: no lsof in (/usr/sbin:/sbin:/usr/local/Percona-XtraDB-Cluster-5.7.18-rel15-29.20.1.linux.x86_64.ssl101/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/usr/local/mysql/bin:/root/bin)
2718-2017-11-19T15:15:11.874860Z 0 [ERROR] WSREP: Failed to read 'ready <addr>' from: wsrep_sst_rsync --role 'joiner' --address '192.168.1.102' --datadir '/data/mysql/3306/data/' --defaults-file '/data/mysql/3306/my.cnf' --defaults-group-suffix '' --parent '3104' --binlog 'mysql-bin'
2719: Read: ''lsof' not found in PATH'
2720-2017-11-19T15:15:11.874912Z 0 [ERROR] WSREP: Process completed with error: wsrep_sst_rsync --role 'joiner' --address '192.168.1.102' --datadir '/data/mysql/3306/data/' --defaults-file '/data/mysql/3306/my.cnf' --defaults-group-suffix '' --parent '3104' --binlog 'mysql-bin' : 2 (No such file or directory)
2721-2017-11-19T15:15:11.874964Z 2 [ERROR] WSREP: Failed to prepare for 'rsync' SST. Unrecoverable.
2722-2017-11-19T15:15:11.874987Z 2 [ERROR] Aborting
2723-
2724-2017-11-19T15:15:11.874993Z 2 [Note] Giving 2 client threads a chance to die gracefully
问题描述:无法传输SST
原因:缺少依赖组件lsof
解决办法:yum -y install lsof
建议:1.先单机启动,更改完root账号,并创建好sst传输账号后,再启动第一个节点
2.若xtrabackup-v2传输方式总是报错,可以改用rsync,并注释掉auth行
3.第二第三个节点启动失败,可以暴力一点删掉data目录下面的文件后重新初始化
4.可以删除data目录下面g开头的两个集群信息文件重新启动进行尝试排错
5.telnet主节点的4567端口判断网络和主节点的mysqld服务是否正常。
6.libaio,openssl也可以考虑安装
以上就是PXC搭建问题有哪些,小编相信有部分知识点可能是我们日常工作会见到或用到的。希望你能通过这篇文章学到更多知识。更多详情敬请关注编程网数据库频道。
--结束END--
本文标题: PXC搭建问题有哪些
本文链接: https://lsjlt.com/news/61342.html(转载时请注明来源链接)
有问题或投稿请发送至: 邮箱/279061341@qq.com QQ/279061341
2024-10-23
2024-10-22
2024-10-22
2024-10-22
2024-10-22
2024-10-22
2024-10-22
2024-10-22
2024-10-22
2024-10-22
回答
回答
回答
回答
回答
回答
回答
回答
回答
回答
0