• 故障分析

输入以下命令查看node1日志

docker logs node1

错误日志如下

2019-06-27T10:30:58.274305Z 0 [ERROR] WSREP: It may not be safe to bootstrap the cluster from this node. It was not the last one to leave the cluster and may not contain all the updates. To force cluster bootstrap with this node, edit the grastate.dat file manually and set safe_to_bootstrap to 1 .
2019-06-27T10:30:58.274308Z 0 [ERROR] WSREP: Provider/Node (gcomm://) failed to establish connection with cluster (reason: 7)
2019-06-27T10:30:58.274310Z 0 [ERROR] Aborting
2019-06-27T10:30:58.274315Z 0 [Note] Giving 0 client threads a chance to die gracefully
2019-06-27T10:30:58.274319Z 0 [Note] WSREP: Waiting for active wsrep applier to exit
2019-06-27T10:30:58.274323Z 0 [Note] WSREP: Service disconnected.
2019-06-27T10:30:58.274325Z 0 [Note] WSREP: Waiting to close threads......

从此节点引导群集可能不安全。它不是离开群集的最后一个，可能不包含所有更新。 要使用此节点强制群集引导，请手动编辑grastate.dat文件并将safe_to_bootstrap设置为1

• 故障解决

查看node1挂载点的文件地址

[root@localhost ~]# docker volume inspect v1
[
    {
        "Driver": "local",
        "Labels": {},
        "Mountpoint": "/var/lib/docker/volumes/v1/_data",
        "Name": "v1",
        "Options": {},
        "Scope": "local"
    }
]

进入/var/lib/docker/volumes/v1/_data目录下

[root@localhost ~]# cd /var/lib/docker/volumes/v1/_data

编辑文件grastate.dat

[root@localhost _data]# vi grastate.dat

修改safe_to_bootstrap的值置为1

# GALERA saved state
version: 2.1
uuid:    1fdc4f95-9625-11e9-9a33-a20935d979f9
seqno:   -1
safe_to_bootstrap: 1

最后

以上就是高贵黑米为你收集整理的解决虚拟机重启后Percona XtraDB Cluster(PXC)容器无法正常启动故障分析故障解决的全部内容，希望文章能够帮你解决解决虚拟机重启后Percona XtraDB Cluster(PXC)容器无法正常启动故障分析故障解决所遇到的程序开发问题。

如果觉得靠谱客网站的内容还不错，欢迎将靠谱客网站推荐给程序员好友。