高可用pacemaker状态，db状态为stopped

admin

# pcs status
Cluster name: my_wsrep_cluster
Stack: corosync
Current DC: controller1 (version 1.1.16-12.el7_4.5-94ff4df) - partition with quorum
Last updated: Thu Dec 28 18:24:33 2017
% k" k# @6 d; WLast change: Thu Dec 28 18:05:11 2017 by root via cibadmin on controller1
# I" {* S, [& E! g" X7 H2 F3 nodes configured
( _! c+ s6 {- O1 resource configured
Online: [ controller1 controller2 controller3 ]
Full list of resources:
9 v/ U- S. L4 }8 s; J& `0 V db (ocf::heartbeat:galera): Stopped
Failed Actions:
* db_start_0 on controller1 'not configured' (6): call=22, status=complete, exitreason='Galera must be configured as a multistate Master/Slave resource.',
; \; A1 t7 a# Q: p  b1 U2 N    last-rc-change='Thu Dec 28 18:05:11 2017', queued=1ms, exec=56ms
0 }4 ]$ l6 \, G4 r, Q3 K8 t3 p
% J4 ^: {. q/ a; e, q9 IDaemon Status:
9 n2 u) e/ E4 o/ V, L& D  corosync: active/enabled
  pacemaker: active/enabled
4 r# k7 p5 m: k1 i5 _  k! G1 B% Z  pcsd: active/enabled

所有的状态都是active的，唯独只有db状态是stopped，为什么呢？
" a" a8 N5 \4 M7 R) t$ C2 k) ^3 {

admin

才疏学浅，未能解决问题，遗憾。不知哪儿出问题了，好尴尬。

admin

配置一个mariadb服务
在所有节点上执行
% P; J  s1 h$ L& m% x# yum install mariadb-* -y
$ a. R/ w9 X2 S% a# B: x/ E# systemctl disable mariadb
# systemctl status mariadb
6 _& ~- @6 p1 S4 g. i5 a# pcs create resource DB ocf:heartbear:mysql
配置一个互为备份的双机环境，一个节点作为web，一个节点作为db，各自有自己的浮动IP，出现故障的时候互相切换
# pcs resource create VIP1 ocf:heartbeat:IPaddr2 ip=192.168.122.171 cidr_netmask=24 nic=eth0
+ @  Y8 k7 y+ B8 y0 u, V# pcs resource group add MyGroup1 VIP1 DB(因为前面已经把DB添加到MyGroup组，所以需要先用pcs resource disable WEB; pcs resource diable DB;pcs resource group remove MyGroup DB; pcs resource enable WEB;才可以添加DB到MyGroup1 )
4 o( T! B5 _, _+ L3 i# pcs constraint location add server1 DB node1 1
/ E5 a: E5 C: A  R% |0 i2 d# pcs constraint location add server1 VIP1 node1 1
* |" }) _- h9 ]. p4 l( Q& I1 z# pcs constraint location add server2 FS node2 1
# pcs constraint location add server2 VIP node2 1
( `3 Q: [& f0 W$ X: o! J+ Z+ N# pcs constraint location add server2 WEB node2 1
执行上述命令后，DB和VIP1将启动在node1上而剩下的FS VIP WEB将启动在node2上

admin

突然想起来好像用的是pike版本的源，这个版本有可能有问题。还需要验证，想着回退到octa版本，试试。

admin

controller_start_0 on controller1 'unknown error'