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

admin

# pcs status
: G; |1 s3 W5 T0 T! xCluster 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
Last change: Thu Dec 28 18:05:11 2017 by root via cibadmin on controller1
" O; g6 E8 M$ S  j% o, p5 C3 nodes configured
1 resource configured
9 I. T. I- C) }2 y) \7 V, UOnline: [ controller1 controller2 controller3 ]
Full list of resources:
9 O- d/ V6 r0 j* s9 ]) i( M; U' Q db (ocf::heartbeat:galera): Stopped
& d6 u& V* [9 B% A& c% _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.',
8 ?3 `2 d7 J# v( s    last-rc-change='Thu Dec 28 18:05:11 2017', queued=1ms, exec=56ms
8 N8 M0 C9 Y7 B% |' }
  \: `4 _: R7 R( F% kDaemon Status:
  corosync: active/enabled
8 m4 h9 d- `+ {, E  pacemaker: active/enabled
( n& }3 q7 T0 R  pcsd: active/enabled
% ~, X5 ~" S" F0 o, F/ a# e
0 r, E$ p3 x5 o0 e所有的状态都是active的，唯独只有db状态是stopped，为什么呢？

admin

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

admin

配置一个mariadb服务
在所有节点上执行
# yum install mariadb-* -y
5 [) f: }3 x( q/ m7 y6 W2 I# systemctl disable mariadb
# systemctl status mariadb
# pcs create resource DB ocf:heartbear:mysql
配置一个互为备份的双机环境，一个节点作为web，一个节点作为db，各自有自己的浮动IP，出现故障的时候互相切换
  h! m) V, i4 ~7 [# pcs resource create VIP1 ocf:heartbeat:IPaddr2 ip=192.168.122.171 cidr_netmask=24 nic=eth0
4 a; S9 r% T4 M& J. Y# 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 )
# pcs constraint location add server1 DB node1 1
4 g. l: R% _7 h4 \# pcs constraint location add server1 VIP1 node1 1
" [$ e, s9 `2 B7 ?) @5 S7 \" ^- ?1 `# pcs constraint location add server2 FS node2 1
# pcs constraint location add server2 VIP node2 1
# pcs constraint location add server2 WEB node2 1
4 K6 ]6 W2 ^* C" Z+ Q执行上述命令后，DB和VIP1将启动在node1上而剩下的FS VIP WEB将启动在node2上

admin

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

admin

controller_start_0 on controller1 'unknown error'